-
Title
Exchange Backup hanging during Snapshot consistency check -
Description
The job then hangs for more than just a few hours without failing on the message
Job Message 2012/09/24 16:54:38 125 Data Plugin EXCHANGE Snapshot consistency check successful for Logs of database 'Mailbox_Database_1'
the following messages are seen in the log prior to this however, suggesting that the VSS snapshot creation was successful:
The following messages are seen in the log, suggesting VSS has been successully able to create the Snapshot:
Information 2012/09/24 16:31:52 0 Data Plugin EXCHANGE Candidate snapshot mount point is 'D:\NetvaultShadowCopy'Warning 2012/09/24 16:31:52 0 Data Plugin EXCHANGE Cannot delete existing mount point 'D:\NetvaultShadowCopy'
Information 2012/09/24 16:31:52 0 Data Plugin EXCHANGE Removed existing mount point directory 'D:\NetvaultShadowCopy'
Job Message 2012/09/24 16:31:59 125 Data Plugin EXCHANGE VSS Snapshot created successfully on server 'EXCHANGE'
The job then hangs for more than just a few hours without failing on the message
Jo
-
Cause
VSS cannot verify the successful creation of the snapshot
-
Resolution
check that the 'Microsoft Exchange Writer' VSS Writer is active with the following:
From the Windows Command Prompt, run:
C:\> vssadmin list writers
Ensure that "Microsoft Exchange Writer" is running. If it is not running, then the most likely cause is a registry setting configured to disable the writer
The registry key is a dword variable "Disable Exchange Writer" in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\.
If this is exists, and is set to 1, then the writer is disabled. To enable, set this variable to 1 and restart the Exchange Information Store Service.
Note that restarting this service will disconnect users from Exchange.
Verify that there is sufficient free space for the D:\NetvaultShadowCopy directory at whichever location this is located on your system.
Try deleting the contents of this directory (previous snapshots) and try re-running the job.
Also check if the Exchange database is on the local machine and not accessed via a SAN or iSCSI Lun as creating snapshots remotely could cause this kind of issue.
It has also been noted that rebooting the database server (thereby probably clearing out the NetvaultShadowCopy directory) has resolved this issue.