Hello,
I am having a problem backing up �Shadow Copy� component on a new Windows 2003 R2 x64 server. I have the x64 client installed and test backups during the day always run fine. If I backup the server during our nightly backups, it fails every time. The event logs on the remote server show the �Volume Shadow Copy� service starting and entering the running state:
Event Type:Information
Event Source:Service Control Manager
Event Category:None
Event ID:7035
Date:4/29/2006
Time:2:33:23 AM
User:NT AUTHORITY\SYSTEM
Computer:Servername
Description:
The Volume Shadow Copy service was successfully sent a start control.
Event Type:Information
Event Source:Service Control Manager
Event Category:None
Event ID:7036
Date:4/29/2006
Time:2:33:23 AM
User:N/A
Computer:Servername
Description:
The Volume Shadow Copy service entered the running state.
10 seconds later, the remote agent crashes.
Event Type:Error
Event Source:Service Control Manager
Event Category:None
Event ID:7034
Date:4/29/2006
Time:2:34:33 AM
User:N/A
Computer:Servername
Description:
The Backup Exec Remote Agent for Windows Servers service terminated unexpectedly. It has done this 1 time(s).
The backup server has the following in the job log:
Job ended: Saturday, April 29, 2006 at 2:37:04 AM
Completed status: Failed
Final error: 0xe000fe30 - A communications failure has occurred.
Final error category: Server Errors
For additional information regarding this error refer to link V-79-57344-65072
Backup- \\Servername\Shadow?Copy?Components \\Servername\Shadow?Copy?Components
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
Backup- \\Servername\Shadow?Copy?Components \\Servername\Shadow?Copy?Components
An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.
If I run the command �vssadmin list writers�, I get the following�
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {d22f7b07-1041-484c-8404-3f55decf5041}
State: Waiting for completion
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {7f0ab312-8bf8-4ec7-9645-3db4525faf5f}
State: Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {fb41e86d-dbb2-4b87-bf77-0958fc1d207f}
State: Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {9e1ae15a-8098-4fcf-bb10-12331879d6cc}
State: Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {f5b0b36c-4e4c-4b75-951f-d11d52d3bd8f}
State: Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {07873d90-11be-444c-b9a8-b12a2d7b8693}
State: Waiting for completion
Last error: No error
I am not sure if the writers are �waiting for completion� because the agent crashed or the agent crashed due to a problem with writers. I had the same exact problem on a different x64 server as well. We decided to rebuild that as a 32 bit server for technical reasons, but I think that shows this is not a one time issue.
Does anyone have any suggestions on how to troubleshoot this problem??
Thanks in advance,
Joe
