NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 347
Status Codes
1. Check to see whether the robotic library has a media access port. Use the robot test
utility to validate this. Investigate whether the administrator or operator has canceled
the inject operation. Ensure that inject for LMF robot types is done only on the LMF
server.
2. Examine command output (if available), debug logs, and system logs for messages
related to the error.
a. Enable debug logging by creating the necessary directories/folders. Increase the
level of verbosity by adding the VERBOSE option in the vm.conf file and
restarting ltid (the device daemon on UNIX or NetBackup Device Manager
service on Windows).
b. Retry the operation and examine the logs.
Robotic Status Code: 219
Message: Cannot move from slot to media access port
Explanation: A robotic eject media operation returned a status indicating that an eject
failure occurred.
Recommended Action:
1. Check to see whether the robotic library has a media access port. Use the robot test
utility to validate this. Investigate whether the administrator or operator has canceled
the eject operation. Ensure that eject for LMF robot types is done only on the LMF
server. When ejecting RSM media, ensure that the device is available, and that media
is available in the NetBackup media pool.
2. Examine command output (if available), debug logs, and system logs for messages
related to the error.
a. Enable debug logging by creating the necessary directories/folders. Increase the
level of verbosity by adding the VERBOSE option in the vm.conf file and
restarting ltid (the device daemon on UNIX or NetBackup Device Manager
service on Windows).
b. Retry the operation and examine the logs.
Robotic Status Code: 220
Message: Media access port does not contain media
NetBackup 4.5 Troubleshooting Guide for Windows