Symantec NetBackup Robotic status code 200 to status code 202

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.

Below are some of the NetBackup Robotic status code 200 to status code 202 which may be received while using the Symantec NetBackup tool.

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
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 and Linux 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.
¦ Stop any robot test utilities that may be running, since they have the lock on
the robotic device when they are active.
¦ Check the configuration of the robot against the recommended configuration
as indicated in the documentation for robot configuration.
¦ Check the health of the robotic device by using a robot test utility, then close
the test utility when finished.
¦ 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 and Linux) 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 and Linux
or the NetBackup Device Manager service on Windows).

Robotic status code 202
Message: Unable to sense robotic device
An element of the robotic library device could not be sensed. The cause could be
any of the following:
¦ The SCSI commands mode sense, mode select, or read element status (of slot,
drive, transport, i/e element) may have failed.
¦ A network API-controlled library inventory request may have failed.
¦ The robotic daemon/process could not initialize a robotic database file.
¦ Check the configuration of the robot against the recommended configuration
as indicated in the documentation for robot configuration.
¦ Check the health of the robotic device by using a robot test utility, then close
the test utility when finished.
¦ Check for the existence and permissions of the temporary robotic database
and the temporary database directory/folder, which is
/usr/openv/volmgr/misc/robotic_db (UNIX and Linux) or
install_path\Volmgr\misc\robotic_db (Windows). Create the
directory/folder and adjust the permissions as needed so that the robotic
daemon/process can create it or use it. Stop and restart ltid (the device daemon
on UNIX and Linux or the NetBackup Device Manager service on Windows).

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *