BA962: Selected VSS component skipped¶
| Error code | Product | Applies to |
|---|---|---|
| BA962 | BackupAssist | For BackupAssist 9.1 or later. |
Description¶
One or more application components failed to back up due to skipped files.
This condition only applies to Cloud Backup jobs.
When a Cloud Backup runs, every file that fails to be uploaded to the cloud destination is re-tried, but after a certain number of re-tries the file is skipped. This error means the skipped file belongs to a VSS application, and that the VSS application is incomplete and can not be reliably restored using this backup.
The backup report will show what VSS application failed, what VSS component failed (e.g the name of the Hyper-V guest or SQL database) and the files or folders that were not backed up.
This error will not cause the backup job to terminate, because even though the VSS application cannot be restored, other data can be.
Resolution¶
To resolve this problem you need to find out what files were skipped and why.
There are many possible causes for the skipped files including:
- Network or internet performance problems
- Network or internet connection problems
- Another process in the machine interfering with the backup job
Checking the backup report for the application, component and files will also help determine where the problem is occurring and how to resolve it.
How to identify a Hyper-V guest¶
When troubleshooting problems with Hyper-V backups, it is important to first determine which guest/s is causing the error. You can do this by checking the Hyper-V VMSS logs, as shown below. You may also be able to identify the guest from the information in the backup report. If you are not able to identify the guest, try backing up the guests one at a time until the errant guest is found.
The guest causing the error can be confirmed by running the backup again without that guest and checking that the backup runs without errors. You can also try a VSS backup on the guest itself using a trial version of BackupAssist. The success or failure of this backup will help to further narrow down what could be causing the error.
If the problem is with backing up data within a guest, you will need to open the Event Viewer inside that guest and review the VSS log entries. These may identify the exact cause of the VSS error.
To view the Hyper-V VMMS logs:
- Click the Start button.
- Click Control Panel.
- Click System and Maintenance.
- Click Administrative Tools.
- Double-click Event Viewer.
- In the left hand navigation window, browse to Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS.
| Last updated | Created | Further assistance |
|---|---|---|
| 8th January 2018 | 5th September 2017 | BackupAssist Support page |