H
Hilton TYoung
Guest
Looking for help with the VSS service on Windows Server 2008 R2 Datacenter. My backup software (EMC Networker) fails to capture the DISASTER RECOVERY data it needs for a bare metal recovery. When it fails the backup software gives me an error message as follows
181407:save: Step (1 of 5) for PID-9712: Save has been started on the client 'abdas-server'.
174412:save: Step (2 of 5) for PID-9712: Running the backup on the client 'abdas-server' for the save set 'pseudo_saveset'.
174424:save: Step (3 of 5) for PID-9712: Creating the snapshot for the selected save sets.
VSS OTHER: ERROR: VSS failed to process snapshot:
176575:save: Unable to save the SYSTEM STATE save sets and create the snapshot.
176571:save: Step (4 of 5) for PID-9712: Unable to complete the backup of the disaster recovery save sets. See the savegrp log to track the closure steps of the backup.
176572:save: Error occurred during the backup of the disaster recovery save sets.
--- Job Indications ---
abdas-server
seudo_saveset: retried 1 times.
If I check Windows Event Viewer I find the following error.
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{f68daa31-c393-11e2-a67c-806e6f6e6963} - 00000000000001EC,0x0053c008,00000000008BE500,0,00000000008BF510,4096,[0]). hr = 0x80070057, The parameter is incorrect.
.
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
I've done a plethora of troubleshooting at the behest of the backup vendor and a microsoft chat support person which has resolved the issue on 2 other systems. On this system I have done the following
Rebooted and run chkdsk
Restarted the VSS writer services
Re-registered the VSS writer services
Set the shadow copy space to unlimited and deleted the prior shadows and created a new one. (The system has 300 GB free out of 528 on the OS drive)
Upgraded the backup client
On the other systems I also did a clean boot with all services disabled but that didn't make a different. This one being a server I was unable to do that since it is a production system that can't go down without prior planning and advance notice.
Has anyone else seen this and resolved it?
Continue reading...
181407:save: Step (1 of 5) for PID-9712: Save has been started on the client 'abdas-server'.
174412:save: Step (2 of 5) for PID-9712: Running the backup on the client 'abdas-server' for the save set 'pseudo_saveset'.
174424:save: Step (3 of 5) for PID-9712: Creating the snapshot for the selected save sets.
VSS OTHER: ERROR: VSS failed to process snapshot:
176575:save: Unable to save the SYSTEM STATE save sets and create the snapshot.
176571:save: Step (4 of 5) for PID-9712: Unable to complete the backup of the disaster recovery save sets. See the savegrp log to track the closure steps of the backup.
176572:save: Error occurred during the backup of the disaster recovery save sets.
--- Job Indications ---
abdas-server
seudo_saveset: retried 1 times.If I check Windows Event Viewer I find the following error.
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{f68daa31-c393-11e2-a67c-806e6f6e6963} - 00000000000001EC,0x0053c008,00000000008BE500,0,00000000008BF510,4096,[0]). hr = 0x80070057, The parameter is incorrect.
.
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
I've done a plethora of troubleshooting at the behest of the backup vendor and a microsoft chat support person which has resolved the issue on 2 other systems. On this system I have done the following
Rebooted and run chkdsk
Restarted the VSS writer services
Re-registered the VSS writer services
Set the shadow copy space to unlimited and deleted the prior shadows and created a new one. (The system has 300 GB free out of 528 on the OS drive)
Upgraded the backup client
On the other systems I also did a clean boot with all services disabled but that didn't make a different. This one being a server I was unable to do that since it is a production system that can't go down without prior planning and advance notice.
Has anyone else seen this and resolved it?
Continue reading...