cancel
Showing results for 
Search instead for 
Did you mean: 

Protection

Many of us are facing issue with Windows Server 2008 Volume Shadow Copy Service (VSS) failure while backing up. The batch file will re-register the VSS DLLs, you need to reboot the server after running the script. (Applicable ONLY for Windows Server 2008 and 2008R2)

THIS INFORMATION IS EXTRACTED FROM SYMANTEC SUPPORT TECHNOTE 70486.
Please check the Technote for updates.

http://www.symantec.com/business/support/index?page=content&id=TECH70486

 

PLEASE CHANGE THE FILE TO .BAT AFTER DOWNLOADING....

Comments

Hi Dev,

Just wondering if your solution is for both 32 and 64 bit Operating Systems

I am running to VSS writer issues as well but I'm running SBS 2008 x64.. Does this script apply to SBS as well? Your link posted did not work...

Cheers...

Hi Sirfatal,

I was running SBS 2011 which is 64bit and it still didn't work. To be honest I still don't know how I fixed the problem. It was just a combination of Rebooting windows, installing updates for windows + Backup exec.

One thing you may want to try which is independent of Backup Exec is to run a simple System State Backup from the command line. System state requires VSS to work so is a good test

wbadmin start systemstatebackup -backupTarget:F: -quiet

http://technet.microsoft.com/en-us/library/cc753201.aspx

 

It just helps you isolate it further. If that works then try again in backup exec. If it then fails you know it is something wrong with Backup Exec.

Please be careful when doing any VSS registration steps with Windows 2008 or newer.

 

Microsoft have released information stating it can break your server, and because of this we have pulled TECH70486

 

As per Microsoft KB http://support.microsoft.com/kb/940184
Important This article is not for use with Windows Vista, with Windows Server 2008, or with later Windows operating systems. Starting with Windows Vista and with Windows Server 2008, Windows component installation is manifest-based. Trying to manually register specific components, as described in the following steps, can have unexpected results that may require you to reinstall Windows to resolve.

New Symantec document here http://www.symantec.com/docs/TECH173983