Symantec NetBackup Robotic status code 211 to status code 215

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 211 to status code 215 which may be received while using the Symantec NetBackup tool.

Robotic status code 211
Message: Process killed by signal
Explanation: An unexpected signal or event canceled the robotic operation.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ 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 of one of the following:
it did not return a status before a designated time period elapsed, or
communications or hardware errors led to the need to reinitialize the device.
¦ Stop any robot test utilities, since they have the lock on the robotic device
when they are active, and can block other requests.
¦ Check to see whether the robotic device still functions.
¦ Check whether excessive hardware or communication problems have delayed
the completion of a robotic command.
¦ Use a robot test utility to send commands to the device to see whether it is
responsive. Execute vmps to verify that no unexpected Media Manager processes
are running. Some processes should remain running, but some processes that
do not go away can indicate a 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.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Obtain the list of drives using a method that involves a robotic library query,
such as a query available from the robot test utility. Compare the list of drives
against the device configuration. Ensure that ltid was stopped and restarted
after changes were last made to the device configuration. ltid is the Media
Manager device daemon on UNIX and Linux or the NetBackup Device Manager
service on Windows.

Robotic status code 214
Message: Robot number does not exist
Explanation: A targeted robotic library was not found in the active device
configuration.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Ensure that ltid was stopped and restarted after changes were last made to
the device configuration. (ltid is the Media Manager device daemon on UNIX
and Linux or the NetBackup Device Manager service on Windows.) On
commands to robotic libraries, specify only robotic libraries that are actively
part of the device configuration.

Robotic status code 215
Message: Requested tape in other or non-configured drive
Explanation: The targeted media was found in a drive differing from the targeted
drive.
Requested media can be temporarily unavailable, which is normal. Also, media
can remain unavailable until administrator or operator action is taken.
¦ If the media is needed immediately, examine command output (if available),
debug logs, and system logs for messages relating to the targeted media.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Check for conflicts between multiple applications using media in the robotic
library. Check integrity of the drive and drive paths, so that media is not
routinely left in other drives.

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 *