NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
3. Check to see whether the robotic device is still functioning. Use a robot test utility to
send commands to the device to see whether it is responsive. Verify that there are no
unexpected Media Manager processes running by executing vmps. Some processes
are expected to remain running, but some processes that do not go away could
indicate a more serious problem, such as a hung system call.
Robotic Status Code: 204
Message: Unable to initialize robot
Explanation: The robot could not be initialized. This is a generic status used for many
conditions.
Recommended Action:
1. 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.
2. Resolve the situation by referring to troubleshooting methods or investigating the
system log messages related to the specific error leading to the robot initialization
failure.
Robotic Status Code: 205
Message: Robotic mount failure
Explanation: The robot could not mount media.
Recommended Action:
1. 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.
340 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows