01-20-2012 09:13 AM
01-20-2012 09:33 AM
You are already using the MS recommended solution for a retryable VSS writer state....In certain cases, restart of the Exchange IS services might work, but its usually the reboot which works...
Have you logged a support case with MS regarding this ?
06-27-2012 09:37 AM
We get the same error, and suggesting we log a support case with MS regarding this is not a solution. The Exchange server works perfectly, it's when Backup Exec tries to access the server that the VSS writer fails. We should get a better solution to this common problem.
07-03-2012 02:32 AM
Has Symantec come up with any solution???
Facing the same problem here...
07-10-2012 04:54 AM
Having the same issues with the SAME environment and Symantec Support had no other ideas in resolving any issues, however the "engineer" (and I use that word VERY loosely) wasn't willing to admit that he didn't, in fact, have all of the answers and escalate to an actual Symantec Engineer so I closed the case as recommendations of continually rebooting servers is NOT a solution...
Server: w2k8R2_ENT
Backup Exec: 2010 R3 SP2
Exchange: 2010
Backup of Virtual Cluster Name for Exchange results in: Microsoft Exchange Writer Error: [8] Failed.
Also having issues with a few other servers; Separated the C:\ backup and System State/Shadow copy and noticed that the Shadow Copy/System State is what is causing the following VSS errors, which clear when the server is rebooted but that is not a solution (although that is all that Symantec tech support was able to suggest):
VSSADMIN LIST WRITERS
‘System Writer’
‘IIS Config Writer’
‘WMI Writer’
‘NPS VSS Writer’
‘IIS Metabase Writer’
‘Cluster Database’
ALL OF THE ABOVE:::
State: [7] Failed
Last Error: Timed Out
I will be trying the MS patch per http://support.microsoft.com/kb/976099 and have reviewed the following article from Symantec: TECH141421
07-10-2012 05:25 AM
...not sure why the TN below from Symantec wasn't ever mentioned...please check it out and it doesn't need a reboot!
http://www.symantec.com/business/support/index?page=content&id=TECH70486
@sunshine: You have maintenance...it's your right to insist on the call being escalated, and if they don't want too, ask for a duty manager!