β03-09-2012 11:04 PM
Hi
I am using BE2010 R2 as my backup software. I am currently configured to take system state backup for my Application Server. The job fails with error. Please find below the error :
Solved! Go to Solution.
β03-14-2012 03:27 AM
THis can be the cause of the issue, and you have 1 of 2 options:
1. Restart the server which will fix the VSS wirters.
2. Check the TN below and then reregister the VSS *.DLLs. This is nonintrusive and doesn't require a restart:
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Thanks!
β03-09-2012 11:43 PM
Try the solutions in these documents
http://www.symantec.com/docs/TECH45309
http://www.symantec.com/docs/TECH143963
Also, you should turn on AOFO and select VSS is the technology to be used.
β03-10-2012 12:42 AM
Hi
I am already taking the backup with AOFO on and VSS selected as Microsoft Volume Shadow Copy Service. I am not using BE over apache and it is configured to run on IIS. I am not facing any problem with other servers running on Windows Server 2008. But this server is having problem.
β03-10-2012 01:39 AM
Hi,
You can sometimes get this error if an AV is either actively scanning the BE services, or the AV blocks BE from accessing the System State.
Check and make sure that this isnt the case, and if need be, put in an exclusion in the AV for the BE services.
Thanks!
β03-14-2012 02:07 AM
Can anyone help me out???
β03-14-2012 02:35 AM
...if you don't respond to what's advised/suggested/pointed out to you, then nobody knows if what was suggested has worked or not. Therefore people are waiting for feedback.
β03-14-2012 02:36 AM
Have you tried maybe changing the AOFO option on the Microsoft Volume Shadow Copy service to "System" instead of "Automatic"
James
β03-14-2012 03:20 AM
Hi
I have changed the option to System. Please find attached the screen shot. Still I am facing the same error. Just for a quick information I checked with my Application and found some of the VSS writers in Timed Out State.
Can you just put light that if this can be problem factor.
β03-14-2012 03:27 AM
THis can be the cause of the issue, and you have 1 of 2 options:
1. Restart the server which will fix the VSS wirters.
2. Check the TN below and then reregister the VSS *.DLLs. This is nonintrusive and doesn't require a restart:
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Thanks!