NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 4, NetBackup Status Codes and Messages 159
Status Codes
◆ Inventory the robotic library. This puts any media that were in the offsite vault
volume group back into the robotic volume group. Then, rerun the vault sessions that
failed.
NetBackup Status Code: 291
Message: number of media has exceeded capacity of MAP; must perform manual eject
using vltopmenu or vlteject
Explanation: This error occurs when a vault job is run for a profile that has selected
automatic eject mode and the number of media to be ejected exceeds the capacity of the
MAP.
Recommended Action: Use vltopmenu to manually eject the media for the selected
profile and session id. The vltopmenu option will let you eject the selected media, a
MAP-full (or less) at a time.
NetBackup Status Code: 292
Message: eject process failed to start
Explanation: This error occurs when the eject processing cannot be started by the vault
job or vlteject command or via vltopmenu.
Recommended Action: For detailed information about the problem, 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)
Use the robtest utility to ensure that you can communicate with the vault robotic
library. Once the problem is resolved, rerun the vault session, vlteject command,
or vltopmenu command.
NetBackup Status Code: 293
Message: eject process has been aborted
Explanation: This error occurs when the eject processing has been aborted. This error
could be encountered during a vault job or when using vlteject or the vltopmenu
eject command.
This error can occur because of one of the following conditions:
NetBackup 4.5 Troubleshooting Guide for Windows