Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 292
Explanation: This error occurs when the following cannot start the eject process: the Vault job, the vlteject command, or the use of the vltopmenu.
Recommended Action: For detailed information about the problem, review the Vault debug log in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the summary.log
in each of the sidxxx
directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows:install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
Use the robtest utility to ensure that you can communicate with the Vault robotic library. After the problem is resolved, rerun the Vault session, vlteject command, or vltopmenu command.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.