The problem seems to be random and on different servers. It is hard to see what is the root cause unless a trace is done during different points in the backup process under different types of loads.
Are any errors being produced? These could also be related to possible MS VSS patches.
As I mentioned earlier that we have tries all possible MS VSS patches, remedies available in internet but no success. One of such error is as mentioned below:
"Failure status of writer Registry Writer - VSS_WS_FAILED_AT_PREPARE_SNAPSHOT VSS SYSTEM BOOT: ERROR: VSS failed to process snapshot, error=0x800423f4: The VSS writer operation failed because of an error that might recur if another shadow copy is created."
We also observed that if we try to use the windows backup utility to take the backup of system state, it also fails. So we are compemplating to avoid VSS to take take and restore system state backup of Windows server. Any solution will be much appreciated.
Looks like a VSS issue. I would check if there are stale VSS snapshots on the machine using: vssadmin list shadows, if so, remove them.
Then decrease multiplexing of the client to 1. VSS had issues with parallel operations that were resolved in MS patch KB975928. Setting the multiplex value to 1 will allow you to troubleshoot the issue much easier.
I'm also moving this over to the support forum to get additional ideas for you.
In October 2009, Microsoft released new guidance on Windows Server 2008 system recoveries via KB article kb249694. This KB article states Microsoft will support System State Recovery to the same instance of Windows Server 2008 but does not support System State Recovery after Full Server restore (without BMR) to the same or different hardware or System State Recovery after a new installation of Windows Server 2008 on new hardware or same hardware.
As a result of Microsoft’s guidance for Windows Server 2008 System State Recoveries, the EMC NetWorker team released the following EMC Technical Advisories and Technical Notes in early November 2009:
EMC Technical Advisory esg109074 “NetWorker: Support for Disaster Recovery of Windows 2008”
The NetWorker 7.6SP2 release in April will introduce a new integrated solution for Windows Disaster Recovery to backup critical Windows Server 2008 R2, Windows Server 2008 and Windows 7 volumes directly to NetWorker savesets. If there is server failure that requires a reinstall of the Windows OS or replacement with similar hardware, an NetWorker Windows Disaster Recovery Wizard guides a user thorough the operations to initialize disks, install the base Windows OS then recover system state information from the NetWorker backup.
I agree with Allan that this looks like a random issue, however because of the differences between Windows 2003 R2 and Windows 2008 R2, regarding VSS itself I would kindly ask you to provide us with some more details about the failure, some extract of the logs so we can provide you with a better advice.
Currently I am handling one Windows Server 2003 server where VSS System Boot backup has failed with the follwoing error:
Failure status of writer Registry Writer - VSS_WS_FAILED_AT_PREPARE_SNAPSHOT VSS SYSTEM BOOT: ERROR: VSS failed to process snapshot, error=0x800423f4: The VSS writer operation failed because of an error that might recur if another shadow copy is created.
One of the common thing I have noticed in these systems is that if I run vssadmin list writers command it shows System Writer's state as Waiting for Completion.
Please let me know which log files you want. I can see some log files under dedup/logs, applogs and logs folder in C:\Program Files\Legato\nsr.
I have checked with vssadmin list shadows in one of the afffected server but there is no stale snapshots. I will try to apply the KB975928 on one of the affected server and how to set the multiplex value to 1.
I have already cheked that the state of the system writer state remains in waiting for completion even if no backup is running. I also know that if I reboot the problem will solve for time being. But after some time it will surface again and it is very difficult ot get the downtime to reboot the server.
AllanW1
334 Posts
0
March 10th, 2011 08:00
The problem seems to be random and on different servers. It is hard to see what is the root cause unless a trace is done during different points in the backup process under different types of loads.
Are any errors being produced? These could also be related to possible MS VSS patches.
Allan
Pilu78
10 Posts
1
March 14th, 2011 00:00
Hi AllanW,
Thanks for your reply.
As I mentioned earlier that we have tries all possible MS VSS patches, remedies available in internet but no success. One of such error is as mentioned below:
"Failure status of writer Registry Writer - VSS_WS_FAILED_AT_PREPARE_SNAPSHOT VSS SYSTEM BOOT: ERROR: VSS failed to process snapshot, error=0x800423f4: The VSS writer operation failed because of an error that might recur if another shadow copy is created."
We also observed that if we try to use the windows backup utility to take the backup of system state, it also fails. So we are compemplating to avoid VSS to take take and restore system state backup of Windows server. Any solution will be much appreciated.
AllanW1
334 Posts
0
March 14th, 2011 11:00
Looks like a VSS issue. I would check if there are stale VSS snapshots on the machine using: vssadmin list shadows, if so, remove them.
Then decrease multiplexing of the client to 1. VSS had issues with parallel operations that were resolved in MS patch KB975928. Setting the multiplex value to 1 will allow you to troubleshoot the issue much easier.
I'm also moving this over to the support forum to get additional ideas for you.
Allan
AllanW1
334 Posts
0
March 14th, 2011 12:00
should have sent this first:
In October 2009, Microsoft released new guidance on Windows Server 2008 system recoveries via KB article kb249694. This KB article states Microsoft will support System State Recovery to the same instance of Windows Server 2008 but does not support System State Recovery after Full Server restore (without BMR) to the same or different hardware or System State Recovery after a new installation of Windows Server 2008 on new hardware or same hardware.
As a result of Microsoft’s guidance for Windows Server 2008 System State Recoveries, the EMC NetWorker team released the following EMC Technical Advisories and Technical Notes in early November 2009:
The NetWorker 7.6SP2 release in April will introduce a new integrated solution for Windows Disaster Recovery to backup critical Windows Server 2008 R2, Windows Server 2008 and Windows 7 volumes directly to NetWorker savesets. If there is server failure that requires a reinstall of the Windows OS or replacement with similar hardware, an NetWorker Windows Disaster Recovery Wizard guides a user thorough the operations to initialize disks, install the base Windows OS then recover system state information from the NetWorker backup.
36115_carloscor
217 Posts
0
March 15th, 2011 00:00
Hello Pilu,
I agree with Allan that this looks like a random issue, however because of the differences between Windows 2003 R2 and Windows 2008 R2, regarding VSS itself I would kindly ask you to provide us with some more details about the failure, some extract of the logs so we can provide you with a better advice.
Thank you.
Carlos.
Pilu78
10 Posts
0
March 16th, 2011 05:00
Hi Carlos,
Currently I am handling one Windows Server 2003 server where VSS System Boot backup has failed with the follwoing error:
Failure status of writer Registry Writer - VSS_WS_FAILED_AT_PREPARE_SNAPSHOT VSS SYSTEM BOOT: ERROR: VSS failed to process snapshot, error=0x800423f4: The VSS writer operation failed because of an error that might recur if another shadow copy is created.
One of the common thing I have noticed in these systems is that if I run vssadmin list writers command it shows System Writer's state as Waiting for Completion.
Please let me know which log files you want. I can see some log files under dedup/logs, applogs and logs folder in C:\Program Files\Legato\nsr.
36115_carloscor
217 Posts
0
March 16th, 2011 05:00
Hi again Pilu,
no need for logs so far. This is what I would do:
1.- Check if there is any backup running (with Networker or any other backup software)
2.- If no backups currently running run:
vssadmin list writers
If System writer is in status [5] Waiting for completion you need to address that first in order to be able to run any File System backup.
Best way is to reboot the box.
3.- If backup is running you will need to wait for the backup to complete and check the status of the writers afterwards.
All writers should be left in status [1] stable.
Please let us know if you need any further information.
Thank you.
Carlos.
ble1
4 Operator
•
14.4K Posts
0
March 16th, 2011 05:00
Have you applied recommended VSS patches (mentioned in some thread not long time ago)?
Pilu78
10 Posts
0
March 16th, 2011 08:00
Hi AllanW,
Thanks for moving this over to support forum.
I have checked with vssadmin list shadows in one of the afffected server but there is no stale snapshots. I will try to apply the KB975928 on one of the affected server and how to set the multiplex value to 1.
Pilu78
10 Posts
0
March 16th, 2011 08:00
Hi Carlo,
I have already cheked that the state of the system writer state remains in waiting for completion even if no backup is running. I also know that if I reboot the problem will solve for time being. But after some time it will surface again and it is very difficult ot get the downtime to reboot the server.