10-04-2012 12:25 AM
Hi
We have Backup Exec 2010 running on a Windows Server 2008 64-bit.
System State backups are failing with the following info:-
Backup- WELLDONPF - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
The writers can be fixed by re-registering their DLLs, and then restarting the COM+ and VSS services (or by restarting the server). However, when the System State backup runs again, they fail again.
Any suggestions?
Thanks
Solved! Go to Solution.
10-05-2012 08:30 AM
Hi there
I have been working through the article you linked to.
However, the majority of the articles seem to describe problems which are different to the one I am having.
VSS Writer Errors:
1st link- the Microsoft article 826936 talks about timeout errors, this is not what I'm seeing.
2nd link - This link does not seem to work - it just says The URL you've tried isn't returning content.
MS VSS Fixes and Updates:-
Windows Server 2008 & SP2
975928 - parallel backups - I only 1 backup running so this probably doesn't apply.
975688 - snapshot corrupted - the snapshot doesn't even get created.
983425 - many volumes - Only 3 volumes on this server.
953531 - stop error 0x0000007E - no stop errors.
However, by chance I happened to enable the Shadow Copy feature for the C drive. I believe this is disabled by default when Windows is installed. None of the other servers I support have this option enabled on the C drive.
The test backup I was running just doing System State now runs ok. I am trying a full backup to see if that completes as well.
I will update this call when I know the answer.
10-04-2012 12:26 AM
I tried using SGMON.EXE to debug what is going on. However, there is so much information that I'm not sure what to look for.
This bit seemed relevant:-
10-04-2012 12:33 AM
You can try explicitly selecting the VSS as the provider.
Since you are using Server 2008, you should not re-register the VSS dll's. See this document
http://www.symantec.com/docs/TECH173983
10-04-2012 12:56 AM
Hi pkh
Thanks for your suggestion. I note your comments about re-registering the DLLs.
The backup did not have the Use Advanced Open File Option ticked. I have ticked it as suggested, and chosen the MS Software Shadow Copy Provider.
However, it failed again with the same error. Do you have any other suggestions?
Thanks
10-04-2012 01:16 AM
Have you tried the trouble-shooting steps in the document that I have referenced earlier?
10-05-2012 08:30 AM
Hi there
I have been working through the article you linked to.
However, the majority of the articles seem to describe problems which are different to the one I am having.
VSS Writer Errors:
1st link- the Microsoft article 826936 talks about timeout errors, this is not what I'm seeing.
2nd link - This link does not seem to work - it just says The URL you've tried isn't returning content.
MS VSS Fixes and Updates:-
Windows Server 2008 & SP2
975928 - parallel backups - I only 1 backup running so this probably doesn't apply.
975688 - snapshot corrupted - the snapshot doesn't even get created.
983425 - many volumes - Only 3 volumes on this server.
953531 - stop error 0x0000007E - no stop errors.
However, by chance I happened to enable the Shadow Copy feature for the C drive. I believe this is disabled by default when Windows is installed. None of the other servers I support have this option enabled on the C drive.
The test backup I was running just doing System State now runs ok. I am trying a full backup to see if that completes as well.
I will update this call when I know the answer.
10-06-2012 05:46 AM
Backup works fine with Shadow Copy enabled for C drive, including System State.
Will leave it like this.
08-02-2017 08:13 AM
Hi,
We have restarted the vss related services and tried to take backup but again the backup got failed
after that i have checked the vss writers again it is got failed
Frequently some of the writers got failed with no reason
what can i do for it without rebooting the server..?