Santiago videla
asked on
Backup fail due to VSS errors.
Hi !
I have a production wintel server 2008 r2 with a tsm client 6.4 where the backup is failing with the following message:
11/11/2016 23:35:54 ANS0361I DIAG: VssRequestor::checkWriterS tatus: VssRequestor::checkWriterS tatus failed with hr=VSS_E_WRITERERROR_TIMEO UT
11/11/2016 23:35:54 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/11/2016 23:36:24 ANS0361I DIAG: VssRequestor::checkWriterS tatus: VssRequestor::checkWriterS tatus failed with hr=VSS_E_WRITERERROR_TIMEO UT
11/11/2016 23:36:24 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/11/2016 23:36:54 ANS0361I DIAG: VssRequestor::checkWriterS tatus: VssRequestor::checkWriterS tatus failed with hr=VSS_E_WRITERERROR_TIMEO UT
11/11/2016 23:36:54 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/11/2016 23:37:24 ANS0361I DIAG: VssRequestor::checkWriterS tatus: VssRequestor::checkWriterS tatus failed with hr=VSS_E_WRITERERROR_TIMEO UT
11/11/2016 23:37:24 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/11/2016 23:37:25 ANS5273E A Microsoft Volume Shadow Copy Services writer is in an invalid state after taking a snapshot.
11/11/2016 23:37:25 ANS5258E Microsoft volume shadow copy snapshot initialization failed.
11/11/2016 23:37:25 ANS1327W The snapshot operation for 'VWSAPASAPPITS01\SystemSta te\NULL\Sy stem State\SystemState' failed with error code: 4353.
11/11/2016 23:37:25 ANS1377W The client was unable to obtain a snapshot of '\\vwsapasappits01\c$'. The operation will continue without snapshot support.
11/11/2016 23:37:25 ANS1228E Sending of object 'VWSAPASAPPITS01\SystemSta te\NULL\Sy stem State\SystemState' failed
11/11/2016 23:37:25 ANS5258E Microsoft volume shadow copy snapshot initialization failed.
The server has been rebooted but the backup still fail with the same error. When i check the writters, i have 3 of them with time out:
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1 050253ae22 0}
Writer Instance Id: {8c32708a-cf54-4e8e-92be-4 47a1ecf472 8}
State: [9] Failed
Last error: Timed out
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1 f8c654603f 6}
Writer Instance Id: {cfcd162a-622d-45cf-9306-9 52eb2f5b1d e}
State: [9] Failed
Last error: Timed out
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-4 9d8f43532f 0}
Writer Instance Id: {c26e9422-db50-455d-b02b-8 8aa2c78f96 f}
State: [9] Failed
Last error: Timed out
my question is: Is there any other solution beside server reboot? because the server was rebooted last saturday and the vss are still failing.
Thanks in advance.
I have a production wintel server 2008 r2 with a tsm client 6.4 where the backup is failing with the following message:
11/11/2016 23:35:54 ANS0361I DIAG: VssRequestor::checkWriterS
11/11/2016 23:35:54 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/11/2016 23:36:24 ANS0361I DIAG: VssRequestor::checkWriterS
11/11/2016 23:36:24 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/11/2016 23:36:54 ANS0361I DIAG: VssRequestor::checkWriterS
11/11/2016 23:36:54 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/11/2016 23:37:24 ANS0361I DIAG: VssRequestor::checkWriterS
11/11/2016 23:37:24 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/11/2016 23:37:25 ANS5273E A Microsoft Volume Shadow Copy Services writer is in an invalid state after taking a snapshot.
11/11/2016 23:37:25 ANS5258E Microsoft volume shadow copy snapshot initialization failed.
11/11/2016 23:37:25 ANS1327W The snapshot operation for 'VWSAPASAPPITS01\SystemSta
11/11/2016 23:37:25 ANS1377W The client was unable to obtain a snapshot of '\\vwsapasappits01\c$'. The operation will continue without snapshot support.
11/11/2016 23:37:25 ANS1228E Sending of object 'VWSAPASAPPITS01\SystemSta
11/11/2016 23:37:25 ANS5258E Microsoft volume shadow copy snapshot initialization failed.
The server has been rebooted but the backup still fail with the same error. When i check the writters, i have 3 of them with time out:
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1
Writer Instance Id: {8c32708a-cf54-4e8e-92be-4
State: [9] Failed
Last error: Timed out
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1
Writer Instance Id: {cfcd162a-622d-45cf-9306-9
State: [9] Failed
Last error: Timed out
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-4
Writer Instance Id: {c26e9422-db50-455d-b02b-8
State: [9] Failed
Last error: Timed out
my question is: Is there any other solution beside server reboot? because the server was rebooted last saturday and the vss are still failing.
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Try running following command vssadmin list providers in elevated (Run as administrator) command line shell on the affected server. If there are more than one VSS provider listed in the system, try to temporary stop/disable all of them except the default Microsoft Software Shadow Copy in services.msc and see if it fixes the issue.
Go to EventViewer and delete the Events from VSS and Windows Server Backup. After that try to take backup again.
ASKER
Thanks,. i´ll try this hotfix.