NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
2. Check vendor or operating system administrative interfaces and logs to see if robotic
commands are being canceled.
Robotic Status Code: 212
Message: Process killed by parent
Explanation: A robotic operation was canceled because it either did not return with a
status before a designated time period had elapsed, or communications/hardware errors
led to the need to reinitialize the device.
Recommended Action:
1. Stop any robot test utilities that may be running, since they have the lock on the
robotic device when they are active, and can block other requests.
2. Check to see whether the robotic device is still functioning.
3. Check whether excessive hardware or communication problems have delayed the
completion of a robotic command.
4. 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: 213
Message: Drive does not exist in robot
Explanation: A targeted drive was not found in the robotic library. The drive
configuration may be incorrect.
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.
344 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows