Unable to create Volume Shadow Copy

Error code

Product

Applies to

BA1403

BackupAssist

BackupAssist Version 3 later

Description

This error is caused by a problem with the Microsoft Volume Shadow copy service in Windows. The Microsoft Volume Shadow copy service is used to backup files that are in use at the time of the backup operation (open files).

Resolution

Resolution 1. Install the latest service pack
Microsoft has released a number of hotfixes targeting Volume Shadow Copy. Nearly of these hotfixes have been included in the latest service packs.

Resolution 2. Reregister the Volume Shadow Copy dlls

From the command prompt type the following:

CD C:\Windows\System32 (depending on where your copy of Windows is installed)
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

Reboot your server.
After reboot, open a command prompt and run:
vssadmin list writers
Ensure that all your writers are displayed without errors

Resolution 3. Ensure an NTFS volume is available
Volume Shadow Copy can fail if there are no NTFS volumes visible to the backup machine at the time of the backup.

Resolution 4. Include Active Directory log files

If your Active Directory log files are stored on a drive other than the system drive, you may get this error when backing up the system state. To resolve this make sure you have specifically selected the log files for backup, or make sure you have selected at least one file on that drive for backup (NTBackup will create a snapshot of a drive only if at least one file is selected on it).

Shadow Copy can fail if an SQL database in non-simple recovery mode is running at the time of backup, even if it is not selected for backup. This issue has been rectified in the latest service pack but be aware that the copy of your SQL database in your backup will be corrupt and cannot be restored (databases selected in the SQL database section of BackupAssist will still be available).

Changing your SQL database to simple recovery mode, or moving it to a volume that isn't included in the backup will also fix this problem.

Last updated

Created

Further assistance

26th Oct 2007

16th Mar 2007

BackupAssist Support page