A0801
Message: The onQ backup of Protected Node PNName has repeatedly failed. The last backup attempt returned code: ReturnCodeListedBelow. Please verify that there is sufficient free disk space on the Protected Node. Backups will continue on the configured schedule or when triggered from the onQ web portal.
Cause: The specific cause depends on the return code that appears in the alert message.
Solution: Regardless of your return code, perform the following solutions in the following table and in the order listed:
Possible Cause | Solution |
High CPU Usage | Go to the Task Manager and determine if you have high CPU usage (> 30%). If yes, reduce the load on the system. In addition, go to PROTECTION CONFIG tab, select the PN, MODIFY > ADVANCED, then do the following: 1. Reduce scan threads to 1. 2. Reduce transfer threads to 1. 3. Reduce CPU resource limit by 50% of current limit. The system default is 30%. Set it to 15%.  |
Conflicting VSS‑based Backup Solutions | There are conflicting VSS‑based backup solutions running. Disable all conflicting VSS‑based backup solutions. |
Insufficient Disk Space | Backups can fail if the PN is running out of disk space. Free up some space on the PN by deleting temp files or, if the PN is a virtual machine, expand the disk. |
Other Solutions | |
If these solutions don’t work, perform the solution(s) outlined in the applicable return status listed under the drop‑down hotspots below and in alphabetical order.
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\ (The system cannot find the path specified.
There are conflicting VSS‑based backup solutions running: see
Conflicting VSS‑based Backup Solutions.
Block sums file c:\Program Files\Quorum\usr/blocksums/99restart-blocksums.bin corrupted: expected file object
Delete all files under blocksums folder.
DoSnapshotSet
Do the following:
1. From the PN, run the following command: .
2. If writers are at a failed state, reboot the PN.
If that solution doesn’t work, contact Quorum Support.
Error writing raw data to c:\Program Files\Quorum\usr/blocksums/sorted-blocksums.bin (Broken pipe)
PN is running out of disk space: see
Insufficient Disk Space. Also, delete all files under blocksums folder.
Error writing c:\Program Files\Quorum\usr/scan/0.txt (No space left on device)
The PN ran out of space during a backup. Free up some space: see
Insufficient Disk Space.
Error: E_INVALIDARG
Reboot the PN. If that solution doesn’t work, reinstall the node software as outlined in
(Alternative) To manually install or reinstall agent‑based Windows PN software:Error: VSS_E_VOLUME_NOT_SUPPORTED (..\volumes_win32.cpp @ 297)
We do not support non‑NTFS volumes as outlined in
Limitations.
Fail to rotate log, QFilter
Do the following:
1. From a cmd prompt, run the following commands:
> sc stop quorum > sc stop qfilter |
2. From C:\Program Files\Quorum\usr, delete all files with filenames that begin with qfilter.log.
3. Run the following command:
> net start qfilter > net start quorum |
Invalid Drive
The drive needed to perform the backup is no longer available. Log on to the PN and verify (Windows Explorer > My Computer) that all the drives are available. If the drives are present, reboot the PN. If the drives are missing, add the drives.
NotStarted
There are conflicting VSS‑based backup solutions running: see
Conflicting VSS‑based Backup Solutions. If that solution doesn’t work, reboot the PN.
Oracle VSS Writer failed during snapshot, aborting
Restore the Oracle database using one of the following procedures:
A Windows PN backup fails if onQ detects a VSS_WS_FAILED_AT_
ErrorState for any of the following VSS Writer error states, and records the error state in the PN’s
Event Log.
VSS_WS_FAILED_AT_IDENTIFY
VSS_WS_FAILED_AT_PREPARE_BACKUP
VSS_WS_FAILED_AT_PREPARE_SNAPSHOT
VSS_WS_FAILED_AT_FREEZE
VSS_WS_FAILED_AT_THAW
VSS_WS_FAILED_AT_POST_SNAPSHOT
VSS_WS_FAILED_AT_BACKUP_COMPLETE
VSS_WS_FAILED_AT_PRE_RESTORE
VSS_WS_FAILED_AT_POST_RESTORE
VSS_WS_FAILED_AT_BACKUPSHUTDOWN
To troubleshoot these error states, look at the PN's Windows log via Event Viewer:
Start button >
Control Panel >
System and Security >
Administrative Tools >
Event Viewer.
For an explanation of the error states, go to
Microsoft’s Volume Shadow Copy API Reference documentation. For overview information, go to
Microsoft’s Event and Error Handling Under VSS. Contact your Oracle database administrator to resolve the error.
scan failed, aborting
The PN might not have enough disk space: see
Insufficient Disk Space.
If that solution doesn’t work, do the following:
1. From the PN, run the following command: .
2. If writers are at a failed state, reboot the PN.
If that solution doesn’t work, there might be conflicting VSS‑based backup solutions running: see
Conflicting VSS‑based Backup Solutions.
If that solution doesn’t work, reboot the PN.
SS_E_PROVIDER_VETO
There might be too much CPU load: see
High CPU Usage. If that solution doesn’t work, there might be conflicting VSS‑based backup solutions running, resulting in VSS writer failures: see
Conflicting VSS‑based Backup Solutions. If that solution doesn’t work, reboot the PN.
Transfer incomplete
If your PN is a Windows Server 2003, you might need to change the values for the
PoolUsageMaximum and
PagedPoolSize registry settings as outlined in
Microsoft KB 304101.
Unable to resolve target hostname
Do the following:
• Verify that the hostname hasn’t changed. If it has, update the IP address in the onQ’s hosts file as outlined in
Manage hosts.
• Verify that the DNS entry is correct. If it isn’t, update the entry in the onQ’s hosts file as outlined in
Manage hosts.
vss unexpected provider
Oracle VSS Writer failed during a snapshot. There are conflicting vss backup solutions running. Uninstall any conflicting VSS‑based backup solutions. If this doesn’t work, reboot the PN.
VSS_E_SNAPSHOT_SET_IN_PROGRESS
There might be conflicting VSS‑based backup solutions running: see
Conflicting VSS‑based Backup Solutions. If that solution doesn’t work, then reboot the PN.