cancel
Showing results for 
Search instead for 
Did you mean: 

VSS Writer Error

VMRaven78
Level 2

Recently contacted Symantec, was on the phone for about 1 1/2 hours trying to resolve the issue with VSS Writer Error, after all was said and done was told to contact Microsoft, after contacting Microsoft the only solution was to reboot the server. But eventually the writers will fail again and the reboot would have to be performed again, is there a permanent fix for this issue????

5 REPLIES 5

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Well, what version of Windows are you using? There is a VSS Rollup Patch you can install if you are using Windows Server 2003...but generally a reboot does reset the VSS writers and then backups will work for a bit.

Are you running BE 2010 R3 with SP3? If not, consider upgrading to this as it fixes a lot of issues with previous versions.

Thanks!

VMRaven78
Level 2

Thanks, we will update this clients servers and see if this helps, but we also run into this problem on BE 2012. 

sriharishkandul
Level 4
Certified

As per recommendation from Microsoft there are patches available to fix the VSS writers unstability. Just try contacting your OS Team so that this can be resolved.

 

Even we had the same issue with the couple of clients earlier and after applying some hotfix the issue got resolved.

allenjamieson
Level 3
Afternoon ive had loads of issues with VSS writers Exchange 2010 - doing a "vssadmin list writers" Showed the Exchange replica writer in a failed state and required reboots to fix, several service packs from MS plus BE fixed this Server 2008 Boxes - VSS failed due to another VSS snapshot provider being installed on the system for this one, you may need to grab a pen.... Firstly i checked registry for vss snapshot providers (i found buffalo writers plus Novastore ones) this may have been confusing the hell out of BE HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers Do a backup of these keys as if we mess up here, they can be restored Now the crazy part, delete the keys EXCEPT the microsoft provider, Now open services.msc Check that these 2 services arnt running and set to manual (or reboot the server) (Cant remember the exact names) 1. Microsoft volume snapshot provider 2. Volume shadow copy Retry the backup and see how this goes doing the above so far we have had several weeks of good backups from 58 file servers without a VSS failure (now ive said it, i'll get to the office and everything will have died)

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...very old post that has gone dead...

Thanks!