Exchange VSS Writer has unsuccessfully completed the backup of storage group. No log files have been truncated for this storage group.
Hi,
New Exchange 2007 SP2 CCR build. Windows Server 2008 SP2, Dell EqualLogics iSCSI SAN.
I have configured Windows Server Backup and run a couple of jobs as a test, however the log files are not truncating and Event 9782 is being logged, followed by ESE Event 2007:
Log Name: Application
Source: MSExchangeIS
Date: 5/11/2009 1:04:06 PM
Event ID: 9782
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Computer: O2TDC-EXC02.oxygenforbusiness.com
Description:
Exchange VSS Writer (instance 363b8861-fe7d-4ecb-af90-79fbb03d9986:1) has unsuccessfully completed the backup of storage group 'Oxygen'. No log files have been truncated for this storage group.
Log Name: Application
Source: ESE
Date: 5/11/2009 1:04:06 PM
Event ID: 2007
Task Category: ShadowCopy
Level: Error
Keywords: Classic
User: N/A
Computer: O2TDC-EXC02.oxygenforbusiness.com
Description:
Information Store (1924) Shadow copy instance 1 aborted.
There are 2 VSS providers installed:
[PS] C:\Windows\System32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
Provider name: 'DELL EqualLogic VSS HW Provider'
Provider type: Hardware
Provider Id: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
Version: 3.3.0.4883
The Exchange writer is showing as stable and has no errors
[PS] C:\Windows\System32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {afe117b1-d0d1-4690-93cf-905f5a1796df}
State: [1] Stable
Last error: No error
There are no other errors in the event log however the previous event is from the EqualLogics VSS writer which suggests this may be interfering:
Log Name: Application
Source: EqualLogic
Date: 5/11/2009 1:03:36 PM
Event ID: 1000
Task Category: VSS
Level: Information
Keywords: Classic
User: N/A
Computer: O2TDC-EXC02.oxygenforbusiness.com
Description:
The service EqlVss has been successfully started
What is my next step to troubleshoot this issue? I have also raised this with Dell.
I am currently backing up using the EqualLogic Auto-Snapshot Manager (Host Integration Toolkit 3.3) which is application aware, however does not do a full backup or truncate logs when it snapshots the information store.
I need to get the logs truncating before I can start moving mailboxes onto this server.
- Edited byJames Bellaart Thursday, November 05, 2009 3:04 AMcorrected OS Version
Answers
- no opportunity to take this any further yet. Running WSB on the other node while its active, and will be installing commvault as a proper backup solution in the next month or so.
I have my exchange binaries on the same SAN volume as the exchange database which wasn't the smartest thing to do during the build, so Im not keen to repair / build that volume.- Marked As Answer byJames-LuoMSFT, ModeratorWednesday, November 11, 2009 1:25 AM
All Replies
Please see if my post in this thread helps
- Thanks, I had read your post already and used one of the sites you linked to get the output I provided above.
After posting I rolled the cluster to the other node and tried the same backup process there and it backed up successfully and truncated logs, so now I need to look into what is different on each node.
The logs show the same events down to the successful node logging an event for wsbexchange, while the other node logs an error at this point. It suggests to me that wsbexchange has not installed correctly on the 1st node. I have already tried removing and re-adding the windows server backup feature. 1. Have you followed all requirements in this article for exchange backup?
Yes
2. Does the issue happen to all SG/Database?
Only 1 SG/Database on the server
3. Is there any 3rd party software on the nodes?
Dell EqualLogic Host Integration Toolkit 3.3
4. Please check all files on the volume, verify if there’s any other special files other than exchange log and database files
no
5. Please get VSSAdmin reports with the commands below, which can provide useful info and even error messages if they exist:
Ø List Providers
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
Provider name: 'DELL EqualLogic VSS HW Provider'
Provider type: Hardware
Provider Id: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
Version: 3.3.0.4883
Ø List ShadowStorage
Shadow Copy Storage association
For volume: (C:)\\?\Volume{9226a785-c35e-11de-b136-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{9226a785-c35e-11de-b136-806e6f6e69
63}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 5 GB
Shadow Copy Storage association
For volume: (I:)\\?\Volume{67b58f6f-c36b-11de-9457-00155d646911}\
Shadow Copy Storage volume: (I:)\\?\Volume{67b58f6f-c36b-11de-9457-00155d6469
11}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 102.401 GB
Shadow Copy Storage association
For volume: (L:)\\?\Volume{67b58f76-c36b-11de-9457-00155d646911}\
Shadow Copy Storage volume: (L:)\\?\Volume{67b58f76-c36b-11de-9457-00155d6469
11}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 20.001 GB
Shadow Copy Storage association
For volume: (B:)\\?\Volume{d464e952-c972-11de-bd93-00155d64691f}\
Shadow Copy Storage volume: (B:)\\?\Volume{d464e952-c972-11de-bd93-00155d6469
1f}\
Used Shadow Copy Storage space: 4.094 MB
Allocated Shadow Copy Storage space: 2.93 GB
Maximum Shadow Copy Storage space: UNBOUNDED
Ø List Volumes
Volume path: C:\
Volume name: \\?\Volume{9226a785-c35e-11de-b136-806e6f6e6963}\
Volume path: I:\
Volume name: \\?\Volume{67b58f6f-c36b-11de-9457-00155d646911}\
Volume path: L:\
Volume name: \\?\Volume{67b58f76-c36b-11de-9457-00155d646911}\
Volume path: B:\
Volume name: \\?\Volume{d464e952-c972-11de-bd93-00155d64691f}\
Ø List Writers
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {afe117b1-d0d1-4690-93cf-905f5a1796df}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {cfcd944a-2d12-4ba7-a36a-3c845017bb25}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {e412699e-9579-49d8-8431-25ffc8420e37}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {610e2477-2a27-478c-96c7-5a74969eb512}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {86d2ad57-37ad-4f8e-b15f-cc59ef396000}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {0dadae73-786b-493c-98a1-6ee6aba9081e}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {bc4728d4-9c7b-49c9-b56d-7469ecc097ac}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {41130c8c-3734-49a1-90d2-2dde4a7e0ba7}
State: [1] Stable
Last error: No error
Writer name: 'Cluster Database'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {aa2675bf-6720-43b0-97c0-8959f5fe8932}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {bf3de13d-9ae9-4423-afed-282f3bcf25c4}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {bb033270-4d29-46fb-adf9-1f3206ddfa2f}
State: [1] Stable
Last error: No error
6. Please use the methods in Troubleshooting Exchange 2007 VSS Backups to troubleshoot the issue
Hoping to avoid installing BETest.
Rolled my cluster over again and still getting the same error on the 1st node.
Compared the logs of the 2 and both nodes log the same events up till
Log Name: Application
Source: MSExchangeIS
Date: 6/11/2009 7:23:51 AM
Event ID: 9622
Task Category: Exchange VSS Writer
Level: Information
Keywords: Classic
User: N/A
Computer: O2TDC-EXC02.oxygenforbusiness.com
Description:
Exchange VSS Writer (instance eb771693-f334-4a77-823d-3e0da64b5eb7:1) has processed the post-snapshot event successfully.And then the successful node logs
Log Name: Application
Source: wsbexchange
Date: 5/11/2009 3:16:03 PM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: O2TDC-EXC01.oxygenforbusiness.com
Description:
The description for Event ID 0 from source wsbexchange cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
And the unsuccessful node logs event 9782 as per the original post.
The EqualLogic error was only logged on one occasion and as this is installed on both nodes I no longer think that this is causing the issue.
- Edited byJames Bellaart Thursday, November 05, 2009 8:38 PMmissing content
Incorrectly formatted drive would be the possible cause. Please move/copy exchange data/log into another drive, and then perform the backup, see if the issue still persists. If not, please format the problematic drive
Please disable the anti-virus software on the problematic node, and see if the issue still persists
"Betest" can help you to narrow down the cause. If log files can be deleted after using Betest, this indicates the cause to windows server backup rather than exchange
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com- How's the issue going?
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com - no opportunity to take this any further yet. Running WSB on the other node while its active, and will be installing commvault as a proper backup solution in the next month or so.
I have my exchange binaries on the same SAN volume as the exchange database which wasn't the smartest thing to do during the build, so Im not keen to repair / build that volume.- Marked As Answer byJames-LuoMSFT, ModeratorWednesday, November 11, 2009 1:25 AM
- I am having the same issue on my Exchange 2007 SP1. I will try your suggestion tomorrow. This is very frustrating - no clear answer on how to resolve this. Thank you for following the thread James.. ill post my results. It seems that this is a growing issue for a lot of people
