NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
Robotic Status Codes
These status codes are logged by robotic daemons/processes. They are also issued by
programs that call the robotic operations, such as the vmchange command and the media
and device management user interfaces.
Robotic Status Code: 200
Message: STATUS_SUCCESS
Explanation: A robotic operation was successfully completed.
Recommended Action: None.
Robotic Status Code: 201
Message: Unable to open robotic path
Explanation: The robotic library device could not be opened. The specific case could be
one of the following.
◆ The robot device, path, or library name in the device configuration may not be valid.
◆ The configured robotic device may not exist.
◆ The robotic device may be incorrect, such as a UNIX device file that is not of a
character special file format.
◆ The robotic daemon/process lock file could not be opened or a lock obtained.
◆ The open operation on the device or through the API interface (such as NDMP) failed.
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.
2. Check the configuration of the robot against the recommended configuration as
indicated in the documentation for robot configuration.
3. Check the health of the robotic device by using a robot test utility, then close the test
utility when finished.
4. Check for the existence and permissions of the lock file itself and the lock file
directory, which is /usr/openv/volmgr/misc/vmd.lock (UNIX) or
install_path\Volmgr\misc\vmd.lock (Windows). Create the directory/folder and
adjust the permissions as needed so that the robotic daemon/process can use the lock
file. Stop and restart ltid (the device daemon on UNIX or the NetBackup Device
Manager service on Windows).
338 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows