08-01-2013 05:37 AM
Hello Team,
All of sudden backup of system state & shadows Copy is started failing. Which was running fine previous. (All Drive Backups are running fine)
Backup Server : Windows Server 2003/2008
Backup Exec Version : 2010
Error is pasted below. Kindly check and help in fixing this.
AOFO: Initialization failure on: "\\Server_Name\Shadow?Copy?Components". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.
V-79-57344-65302 - The Shadow Copy resource is not responding. Backup set canceled.
V-79-57344-65302 - The Shadow Copy resource is not responding. Backup set canceled.
- AOFO: Initialization failure on: "\\Server_NameSystem?State". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.
V-79-57344-65301 - The System State resource is not responding. Backup set canceled.
V-79-57344-65301 - The System State resource is not responding. Backup set canceled.
08-01-2013 09:57 AM
Hello Vamsi,
Based on the error reported, you might want to refer to the following link:
http://www.symantec.com/business/support/index?page=content&id=TECH165493
08-01-2013 10:16 AM
If the previous link didnt resolve the issue,
08-01-2013 01:32 PM
Looks like a VSS component issue
Try a system state backup via ntbackup if windows 2003 from the local server
or if 2008 install the backup role and wbadmin command and try a local backup on the server which was failing.
08-01-2013 08:07 PM
08-02-2013 12:31 AM
Hello Vamsi,
To backup Shadow Copy Component or System State it always uses VSS. So can you confirm if VSS service on that remote server set to manual type? Also try to start the service and see if there is any issues with it.
Regards,
-Sush...
08-02-2013 09:50 PM
Thank you all for your vaulable inputs. I will check and get back to you....
08-06-2013 08:07 PM
The VSS writers are owned by Microsoft and are merely called on to perform a function by Backup Exec. On the severs with the issue, open a command prompt with admin privileges and run "vssadmin list writers." This will show the status of the VSS writers on the system. If any show as other than "stable" then there may be an issue with the writers. Usually a reboot of the system resolves the issue. If the writers do not show at all or they are still not "stable" after a reboot, then you may need to contact Microsoft to resolve the issue.
As Sush says above, the VSS services should be in Manual start and should not be started unless they are being used. There are 2 VSS services: Microsoft Software Shadow Copy Provider and Volume Shadow Copy. If the server is a Hyper-V host, there will be other VSS services specific to Hyper-V