NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
(where xxx is the session id)
Correct the problem and rerun the vault job.
Chapter 4, NetBackup Status Codes and Messages 161
Status Codes
NetBackup Status Code: 295
Message: eject process could not obtain information about the robot
Explanation: This error occurs when the eject process cannot collect information about the
robotic library and its associated MAPs and volumes.
Recommended Action: For detailed information about why the process failed, review the
vault debug log in the following directory:
UNIX: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
Also review the detail.log in each of the sidxxx directories that had problems:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session id)
Correct the error and rerun the vault session, vlteject command, or vltopmenu
eject command.
NetBackup Status Code: 297
Message: all volumes are not available to eject
Explanation: This error occurs when an attempt is made to eject a non-existent or bad
media id during the eject phase of a vault session, vlteject command, or vltopmenu
command.
Possible reasons for this occurring are:
◆ The bad media id was added by means of the vlt_ejectlist_notify script.
◆ The bad media id is already in the MAP or not in the robotic library.
◆ The bad media id is in a robotic drive.
◆ The bad media id is in transit in the robotic library.
Recommended Action: Remove or correct the bad media id from the
vlt_ejectlist_notify script and rerun the vault session. If the bad media id is in the
MAP or a drive or in transit, something is misconfigured.
NetBackup Status Code: 298
Message: the library is not ready to eject volumes
NetBackup 4.5 Troubleshooting Guide for Windows