Document ID: 301361
http://support.veritas.com/docs/301361 E-Mail Colleague IconE-Mail this document to a colleague

How to troubleshoot Exchange 2007 backups that may be failing due to VSS (Volume Shadow Copy Service) Issues
Details:

Resolution:

1. Open the Windows Event Viewer and check system events for any VSS specific errors during the time of the backup.

2. Verify the VSS Writers are stable
Run the command right after the backup fails if at all possible.:
VSSADMIN LIST WRITERS
*If failure on any of the writers, step 3 should be considered. If Step 3 does not resolve or does not apply, Microsoft should be contacted to resolve VSS issues

3. Update the current VSS installation (IF POSSIBLE)
As of December 19, 2007 - A Microsoft VSS Hot fix (MKB 940349) is available.
Update VSS with the following patch or later if it is not already installed:

Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues
 http://support.microsoft.com/kb/940349

4. Verify the latest version of the Microsoft Exchange Server MAPI Client and Collaboration Data Objects (MAPI/CDO) is installed on the Exchange Server. (Version 6.05.7888 or later)  http://support.veritas.com/docs/287937

How to verify what the version of MAPI/CDO (6.05.7888) or greater, is installed on the Exchange Server.
Step 1. Search the Server for the CDOsys.dll file
Step 2. Check the version number of the file

If the file version is older than 6.05.7888, the latest version of the MAPI/CDO client as of 3/6/2008 can be downloaded here:

Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1
 http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E&isplaylang=en&displaylang=en

(Note - The previous version of MAPI/CDO needs to be uninstalled before the new version is installed. A reboot of the Exchange Server is also required)

5. Verify the latest version of Management Tools is installed on the Backup Server.
(Note - If the Exchange Server is upgraded to Exchange SP1 and the Backup Server's Management Tools is not upgraded with it, this can cause issues on Exchange 2007 backups)

How to verify the what version of Management Tools is installed on the Backup Server:
Step 1. Click Start>Programs>Exchange>Exchange Management Shell
Step 2. Type the following command: Get -ExchangeServer
Step 3. Click Enter (This will show the number of Exchange Server's in the Environment)
Step 4. Under "AdminDisplayVersion" you will find the version for Management Tools.
- If version 8.0 (SP1 for Management Tools is NOT installed)
- If version 8.1 (SP1 for Management Tools is installed)

Below is an example:
 

4. In some extreme cases it may be necessary to debug Exchange VSS Writers at a higher level when VSS Writer failures cannot be determined or proven from the VSSADMIN LIST WRITERS command.

How to set the Exchange Server to 'Expert' level debugging to report in Windows Event Viewer.
Step 1. Before running the backup ensure the event logs for System and Application are saved and cleared.
Step 2. Click Start>Programs>Exchange>Exchange Management Shell
Step 3. Type the following command: cd \ and click Enter
Step 4. Type the following command:
Set-EventLogLevel "MSExchange Repl\Exchange VSS Writer" -level expert
Step 5. To verify run the command was successful type the following command:
Get-EventLogLevel "MSExchange Repl\Exchange VSS Writer"
                (This will indicate the entry was successful if the 'expert' EventLevel is referenced)

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Step 6. Open the Registry on the Exchange Server and goto the following location:
HKLM>SYSTEM>CurrentControlSet>Services>MSExchangeIS>Diagnostics\9002 System
(Any time a registry change is expected, please backup the registry before moving forward)
Step 7. Set the following Registry Keys from default 0 to 7
- Exchange Writer
- Backup Restore
Step 8. Close the Regisrty and re-run the Exchange backup as before.
(Note - You can change the level of Event logging by setting the registry keys back to 0)
(Note - To change the Debugging level back to normal away from expert then run the command from the shell:)
Set-EventLogLevel "MSExchange Repl\Exchange VSS Writer" -level normal

*The above information should be able to determine or resolve VSS issues causing Exchange 2007 backups to fail. Should VSS errors report after performing the above mentioned items then Microsoft Support should be contacted.



Supplemental Material:

System: Ref.#Description
UMI: V-79-57344-34110 A failure occurred querying the Writer status

Acknowledgements
Microsoft
Products Applied:
 Backup Exec for Windows Servers 11d (11.0) 7170, 12.0, 12.5
 Backup Exec for Windows Servers Agent for Microsoft Exchange Server 11d(11.0) 7170 SP2
Last Updated: March 04 2009 06:30 PM GMT
Expires on: 03-04-2010
Subscribe Via E-Mail IconSubscribe to receive critical updates about this document

Subjects:
 Backup Exec for Windows Servers
   Agent For Exchange: Backup-Restore, Troubleshoot
Backup Exec for Windows Servers Agent for Microsoft Exchange Server
   Application Basics: Backup-Restore, Troubleshoot
   Publishing Status: Kcs

Languages:
 English (US)

Operating Systems:
Windows Server 2003

Enterprise (x64)