Symantec NetBackup Robotic status code 226 to status code 230

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

Robotic status code 226
Message: Requested slot contains the wrong tape
Explanation: The media in the requested slot is different from the media that is
expected in that slot. The volume configuration is not consistent with the physical
contents of the robotic library that is associated with the slot associated with the
requested volume.
Recommended Action: The volume configuration or media placement in the
robotic library needs to be adjusted using one of the media management interfaces.
Determine whether the barcode changed or the media changed since the last time
the EMM database was reconciled for the affected slot. If only the barcode has
changed but not the media, issue an update barcode request for each affected
volume. If the media has been changed, use a media management interface to run
robot inventory update, which updates theEMMdatabase with the media location.

Robotic status code 228
Message: Requested slot does not exist in robot
Explanation: The slot that is associated with a request is not valid for the robot.
¦ 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.
¦ Issue a robot inventory Contents report to determine the valid slot range for
the robot. Check the volume configuration to ensure that only valid slots are
referenced in volume records, paying particular attention to the starting and
ending slot numbers. Update the volume configuration as needed, or request
only valid slot ranges for robotic operations.

Robotic status code 229
Message: Requested operation is not supported by the robot
Explanation: A robotic operation was sent to a robotic component that did not
support that operation. Or the options that were requested for the operation were
not supported. There may be an incompatibility between components or versions
of the product.
¦ 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.
¦ Verify that all Media Manager binaries and user interfaces are at a compatible
version level.

Robotic status code 230
Message: System error occurred during robot operation
Explanation: A robotic operation encountered a system error. This status code
is used for generic system call failures within robotic daemons/processes.
¦ Check for other error messages in the command or interface output to indicate
which system call failed. 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 the system application log for error and warning messages.
¦ Verify that the system is not running out of virtual memory. If virtual memory
is the problem, shut down unused applications or increase the amount of
virtual memory. To increase virtual memory on Windows: display the Control
Panel, double-click System, and on the Performance tab, set Virtual Memory
to a higher value.
¦ Verify that all product binaries are properly installed.
¦ Verify that no unexpected Media Manager processes are running by executing
vmps. Some processes should remain running, but some processes that do not
go away could indicate a problem, such as a hung system call.

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 *