Check the log for avamar initiated ntbackup system state backup in C:\Documents and Settings\Default User\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\Data and troublshoot ntbackup issues.
You can also add --systemstate-timeout=7200 in avtar.cmd in var directory of target machine to allow 2 hours for ntbackup to finish.
You can apply MS KB hotfix 940349 for windows 2003 SP2 and consult with Microsoft for VSS Failures on Windows 2008. Generally reboot clears up all VSS issues.
Sameer_Khan
121 Posts
1
October 30th, 2011 10:00
Check the log for avamar initiated ntbackup system state backup in C:\Documents and Settings\Default User\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\Data and troublshoot ntbackup issues.
You can also add --systemstate-timeout=7200 in avtar.cmd in var directory of target machine to allow 2 hours for ntbackup to finish.
Aaron852
1 Rookie
•
6 Posts
0
November 3rd, 2011 03:00
Thanks for the post above
Sameer the systemstate timeout certainly sounds like a handy tip.
I have recently noticed that the error occurs a lot when there is an issue with the writers (vssamin list writers)
Does anyone know why the writers fail and is there anything i can do to proactively stop this happening?
Sameer_Khan
121 Posts
0
November 16th, 2011 10:00
Aaron,
You can apply MS KB hotfix 940349 for windows 2003 SP2 and consult with Microsoft for VSS Failures on Windows 2008. Generally reboot clears up all VSS issues.
Thanks
Sameer K