Symantec NetBackup Robotic status code 256 to status code 260

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

Robotic status code 256
Message: Robot busy, multiple eject operation in progress
Explanation: The robot is unavailable because a multiple eject is in progress,
using resources that are needed for the requested operation.
RecommendedAction: Wait until the robot is done performing the multiple eject
operation before starting new requests. Check the vendor or operating system
administrative interfaces and logs to see if robotic resources are busy.

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

Robotic status code 258
Message: Cleaning/unknown media in drive
Explanation: A request to mount a tape failed because cleaning media was found
in the drive.
¦ 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.
¦ Retry the operation once the drive cleaning has completed.

Robotic status code 259
Message: Not authorized by VxSS
Explanation: A request was made to the robot daemons by an unauthorized user.
¦ Verify that the user has the necessary permissions to perform this operation.
¦ Verify that the authentication and authorization security settings are correct,
under HostProperties in the NetBackupAdministrationConsole. Information
is available on using the Symantec Product Authentication and Authorization
Service.
See the NetBackup Security and Encryption Guide.

Robotic status code 260
Message: Robot busy, robot diagnostics in progress
Explanation: The requested robot is running a robot diagnostic.
¦ 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.
¦ Retry the operation when the robot diagnostic cycle is complete.

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.

 

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.

 

Symantec NetBackup Robotic status code 221 to status code 225

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

Robotic status code 221
Message: Media access port already contains media
Explanation: A robotic eject media operation returned a status indicating that
the media access port contains one or more cartridges. The operator or
administrator may not have removed media from the media access port as part
of the latest (or a previous) eject operation.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Media Manager status codes” on page 337.
¦ Coordinate inject/eject operations between all operators and administrators.
Ensure that the media access port is empty of media before an eject operation.

Robotic status code 222
Message: Robotic arm has no addressable holder
Explanation: A holder is gone from an element of the robot and cannot be used.
¦ 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.
¦ Investigate the state of the physical hardware and correct the holder status
for storage, drive, and transport elements as needed. Then, resubmit the
request.

Robotic status code 223
Message: Robot busy, cannot perform operation
Explanation: The robot is busy performing another operation, using resources
that are needed for the requested operation.
Recommended Action: Wait until the robot is done performing current
external-based requests (including robot inventory and inject/eject media) before
starting new requests. Check vendor or operating system administrative interfaces
and logs to see if robotic resources are busy.

Robotic status code 224
Message: Control daemon connect or protocol error
Explanation: A protocol error occurred between robotic and other components.
¦ 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.
¦ Investigate the system log messages that are related to the specific error
leading to the media mount failure. Verify that all Media Manager binaries are
at a compatible version level.
¦ Verify that robotic interfaces to vendor and operating system software have
compatible versions.

Robotic status code 225
Message: Robot hardware or communication error
Explanation: Ahardware or communications error occurred between robotic and
other components.
¦ 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.
¦ Investigate the system log messages that are related to the error leading to
the media mount failure.
¦ Verify that all Media Manager binaries are at a compatible version level. Verify
that robotic interfaces to vendor and operating system hardware and software
have compatible versions.

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.