Symantec NetBackup Robotic status code 246 to status code 255

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

Robotic status code 246
Message: Failed to find an available slot to inject to
Explanation: An attempt to inject a volume into a full library failed. This error
should only occur when the library is full. Full means that all storage elements
either contain media or have been assigned media that are currently mounted in
a drive. Note that some libraries that support multiple media types restrict which
type of media can be assigned to each storage element. In this case, this error
might occur even if some of the storage elements in a library were not full. Since
the empty storage elements may not match the media type for the media to inject,
the library is full for this media type.
Recommended Action: Clear the media access port, then re-inventory the robot
by doing a volume configuration update.

Robotic status code 249
Message: Volume is in home slot
Explanation: Volume is currently in its home slot and ready for eject.
Recommended Action: None.

Robotic status code 250
Message: Media access port is available
Explanation: Media access port is available for inject or eject.
Recommended Action: Begin inject or eject operation.

Robotic status code 251
Message: Media access port is unavailable
Explanation: Media access port is not ready for inject or eject.
Recommended Action: Manually remove any media remaining in the robot’s
media access port. If this status persists, check robotic console for errors.

Robotic status code 252
Message: Media access port is in inject mode
Explanation: Media access port is ready to inject and is not available for eject.
Recommended Action: Complete inject operation.

Robotic status code 253
Message: Media access port is in eject mode
Explanation: Media access port is ready to eject and is not available for inject.
Recommended Action: Complete eject operation.

Robotic status code 254
Message: Robot busy, inventory operation in progress
Explanation: The robot is not available because it is performing an inventory,
using resources that are needed for the requested operation.
Recommended Action: Wait until the robot is done performing the inventory
before starting new requests. Check the vendor or operating system administrative
interfaces and logs to see if robotic resources are busy.

Robotic status code 255
Message: Robot busy, inject operation in progress
Explanation: The robot is not available because it is involved in an inject operation,
using resources that are needed for the requested operation.
Recommended Action: Wait until the robot is done performing the inject
operation before starting new requests. check the vendor or operating system
administrative interfaces and logs to see if robotic resources are busy.

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 *