NTBackup Volume Shadow Copy Errors

If you are getting back up errors after trying to run a NTBackup, or if you are just getting ntbackup errors in the event viewer, try some of these tips to help fix your backups.

When an NTBackup fails to run, it logs the error code in the NTBackup logs. Also, you can check the event viewer to see what error code caused the NTBackup failure. Most errors will be because of the shadow copy service or one of the shadow copy writers.

Here are some helpful tips on getting the Volume Shadow Copy service and its dependencies working with NTBackup.

Making sure the Volume Shadow Copy service is on
1. Type the following to pull up the Services mmc.
a. Start -> Run -> Services.msc

2. Scroll down to Volume Shadow Copy.
a. Right click on the service and look under the General Tab.
b. Make sure that the "Startup type:" is set to manual.
c. If there is an error starting the service, make sure "Remote Procedure Call" service is started.

(Perform these steps if the Volume Shadow Copy fails to start)
a. Within the Services mmc, find the "Remote Procedure Call" service.
b. Right click on the service and look under the General Tab.
c. Make sure that the "Startup type:" is set to Automatic.
d. Once the service is started, proceed back to Step 2.

3. Run these following commands in the Command Prompt to check the integrity of the VSS writers.
a. Start -> Run -> CMD
b. Type "vssadmin list providers" (without the quotes).
c. Type "vssadmin list writers". If you see no errors, then the service is running properly.
d. If there were errors, find the specific writer that is causing the error and type it into any search engine for more information on it.

Re-registering the VSS binaries
1. Pull up a command prompt.
a. Start -> Run -> cmd

2. Change directory to \windows\system32
a. cd %systemroot%\system32

3. Stop the Volume Shadow Copy service.
a. net stop vss

4. Register the following .dlls and services.
a. Type the following in the command prompt:
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
rRegsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

5. Run a test full backup.

Repairing Damaged WMI (requires reboot)
1. Pull up a command prompt.
a. Start -> Run -> cmd

2. Stop the WMI service.
a. net stop winmgmt

3. Open Explorer and go to the following folder:
a. %systemroot%\system32\wbem\repository
b. Delete the folder and everything in it.

4. Reboot the system normally.

5. After the reboot, pull up a command prompt and type the following in this order:
winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

6. Run a test full backup.

Running a Test Full Backup
1. Pull up NTBackup (Start -> All Programs -> Accessories -> System Tools -> Backup).

2. Steps to create NTBackup.
a. From the Wizard, click on “Advanced Mode”.
b. Once the new window comes up, click on the “Schedule Jobs” tab.
c. Double click on a highlighted date that is on the calendar.
d. Click next on the first screen, make sure the “Back up everything on this computer” is checked and click next.
e. Choose a place to save the backup (i.e. your desktop) and name the backup “Testbackup.bkf”. Click next.
f. Make sure the type of backup is set at “Normal” and click next.
g. Check the “Verify…” and click next.
h. Make sure the “Replace…” option is selected and click next.
I. From the “When to Back Up screen”, click on the “Now” option and click next. Then, click finish.
j. The NTBackup will now proceed with the backup. If the backup times out and fails, proceed to Backup Errors.

Add Feedback