Common issues with backups

Backups may fail for the following reasons:

• Sometimes the system can get into a state where the ole32.dll becomes unregistered. If ole32.dll is unregistered, backups do not work. To resolve this issue, re-register ole32.dll with the following command:

  regsvr32 ole32.dll

• Backups can fail if either of the following services is disabled:

  • Microsoft Software Shadow Copy Provider

  • Volume Shadow Copy

  • COM+Event System

• Typically, the Volume Shadow Copy service should not be running. It is started on demand whenever it is needed. If the service is running, it may be stuck in a bad state. To stop the service, enter the following command:

  net stop "Volume Shadow Copy"

  If this command does not work, use Windows Task Manager to end the VSSVC.exe process.

• Backups of Data Archive have been known to fail when the OfmProvider from St. Bernard software is installed on the Data Archive computer. To determine if this software is installed, run the vssadmin list providers command and look for OfmProvider in the output.

• All archives to be backed up must be on the Data Archive computer. If the archive to be backed up is on a remote drive, such as a UNC path, the backup will fail unless the file is marked read only, and the pibackup service is configured to run as an account that has appropriate permissions.

• Backups require at least one NTFS partition on the machine where Data Archive is installed.