|
Error code |
Product |
Applies to |
|---|---|---|
|
BA917 |
BackupAssist |
Operating Systems running VSS. |
Description
This error occurs when the Volume Shadow Copy Service (VSS) is unable to run due to another instance of VSS already running.
Resolution
The error's known causes and resolutions are described below.
Known Cause 1 - Multiple backup solutions installed
Many backup solutions have their own proprietary snapshot manager which can cause conflicts with other backup solutions installed on the system.
If you have (or had) more than one backup program installed on your system, disable/uninstall all of the programs except for BackupAssist, and run the backup job again.
It is best practice to only have one backup solution installed at any one time.
You should also run a registry cleaner after the other backup solutions have been uninstalled: https://www.backupassist.com/blog/support/how-to-resolve-a-ba910-volume-shadow-copy-error-0x80004230/.
Known Cause 2 - Scheduling Conflict
This section explains VSS and device conflicts. Refer to the section applicable to your issue.
VSS conflicts: Having two backup jobs running at the same time within BackupAssist can cause errors if both backup jobs are trying to run VSS. Ensure that only one backup job is running at any one time.
Hardware conflicts: Conflicts with backup devices can occur when another process is trying to use the backup destination at the same time as BackupAssist. Make sure that there are no scheduled tasks, particularly backup tasks, that run at the same time as your scheduled backups.
To confirm that this is a scheduling issue try running a backup during the day, or try changing the scheduled time of your backup by a few hours. If these backups work, the problem is likely to be a scheduling conflict.
Known Cause 3 - Previous VSS snapshot is still running
Microsoft's native snapshot manager is only able to perform one snap shot at a time. If a snapshot process is already running when the backup job starts, the backup job could fail.
Stopping and restarting the Volume Shadow Copy service can resolve this problem.
To do this, open an elevated command prompt window and run the following commands:
net stop vss
net start vss
A reboot of the server has been known to clean up the snapshot manager correctly should a service restart not resolve the issue.
|
Last updated |
Created |
Further assistance |
|---|---|---|
|
14th Aug 2015 |
20th Aug 2007 |
BackupAssist Support page |