troubleshooting Question

TSM backup errors in dsmerror.log: ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT

Avatar of itnifl
itniflFlag for Norway asked on
StorageStorage SoftwareMicrosoft Server OS
6 Comments2 Solutions11762 ViewsLast Modified:
We are using TSM for backups. I am getting this error in the dsmerror.log of a 2008 R2 server:


12/05/2013 05:28:49 ANS1512E Scheduled event 'DAILY_SCHEDULE' failed.  Return code = 12.
12/05/2013 23:00:50 ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT
12/05/2013 23:00:50 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
12/05/2013 23:01:20 ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT
12/05/2013 23:01:20 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
12/05/2013 23:01:50 ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT
12/05/2013 23:01:50 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
12/05/2013 23:02:20 ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT
12/05/2013 23:02:20 ANS5268W The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
12/05/2013 23:02:20 ANS5273E A Microsoft Volume Shadow Copy Services writer is in an invalid state after taking a snapshot.
12/05/2013 23:02:20 ANS5258E Microsoft volume shadow copy snapshot initialization failed.
12/05/2013 23:02:20 ANS1327W The snapshot operation for 'SERVERNAME\SystemState\NULL\System State\SystemState' failed with error code: 4353.
12/05/2013 23:02:21 ANS1228E Sending of object 'SERVERNAME\SystemState\NULL\System State\SystemState' failed
12/05/2013 23:02:21 ANS5258E Microsoft volume shadow copy snapshot initialization failed.

I tried going through the solution steps in this article: https://www-304.ibm.com/support/docview.wss?uid=swg21295294

1. I don't know of any patches that remedy this for Windows 2008 R2.
2. All checked OK.
3. vssadmin list writers shows that several writers have status error. I restart theyr corresponding services this way:

 
@echo off
sc stop "Altiris Deployment Agent"
sc stop VSS
sc stop BITS
sc stop AppHostSvc
sc stop CryptSvc
sc stop tmlisten
sc stop iphlpsvc
cd /d %windir%\system32  
net stop swprv 
ping -n 16 -w 1000 127.0.0.1
regsvr32 /s ole32.dll 
regsvr32 /s oleaut32.dll 
regsvr32 /s vss_ps.dll 
vssvc /register 
regsvr32 /s /i swprv.dll 
regsvr32 /s /i eventcls.dll 
regsvr32 /s es.dll 
regsvr32 /s stdprov.dll 
regsvr32 /s vssui.dll 
regsvr32 /s msxml.dll 
regsvr32 /s msxml3.dll 
regsvr32 /s msxml4.dll
ping -n 16 -w 1000 127.0.0.1
sc stop Winmgmt
ping -n 32 -w 1000 127.0.0.1
net start swprv
sc start VSS
sc start BITS
sc start AppHostSvc
sc start CryptSvc
sc start Winmgmt
ping -n 16 -w 1000 127.0.0.1
sc start "Altiris Deployment Agent"
sc start tmlisten
sc start iphlpsvc

This script is actually run as a PRENSCHEDULECMD option in dsm.opt before the backups are run every day. The errors are then cleared and the writers should be ready to be used. They did not state anything else then "error" anyway.

4. I downloaded MS Windows Software Development Kit (SDK) and tested the following commands:

vshadow  -nw  C:   >vss_nw.out
    vshadow  -p   C:   >vss_p.out
    vshadow  -wm2      >vshadow_wm2.out
    vshadow  -ws       >vshadow_ws.out

None of them yielded any errors in the output files. I tested System state backups with Windows System Backup and wbadmin command line tool. This all worked fine. I also tested a system state backup with the TSM Storage Manager Backup Client. This also worked fine.

For a period I made the TSM backup run fine by first running a scheduled system state backup with Windows System Backup every day(resets the whole VSS thing I am guessing), but that has no effect anymore.

So, I have no idea where to go from here. All works when testing, but when the schedule runs the errors appear in the error log and the backup appears more or less failed.
ASKER CERTIFIED SOLUTION
Venugopal N

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 2 Answers and 6 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 6 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros