Symantec NetBackup Device configuration status code 27 to status code 30

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. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 27 to status code 30 which may be received while using the Symantec NetBackup tool.

Device configuration status code 27
Message: Invalid drive type for the robot
Explanation: On a request to configure a drive to be in a robot, the drive type was
not valid for the selected robot type.
RecommendedAction: Check the Robot Attributes tables in the following manual
to determine valid media types for a given robot type:
See the NetBackup Device Configuration Guide.
Drive types directly correspond to the listed media types. Configure supported
devices so that invalid combinations of drive types and robot types are not
required.

Device configuration status code 28
Message: Invalid robot drive number for the robot type
Explanation: On a request to configure a drive to be in a robot, the robot drive
number was not valid for the selected robot type.
Recommended Action: The robot drive number (for ACS robots, the set of ACS
drive identifiers) is limited to the ranges that are based on the robot type. These
limits are based on a supported device list. An invalid robot drive number means
that the drive number was not within the acceptable range. Make sure that the
robot hardware is supported and that the required patches are installed to support
the robotic library. If the robot type is TLH or TLM, do not specify a robot drive
number because the drives are addressed with a vendor drive name.

Device configuration status code 29
Message: Drive index is in use by another drive
Explanation: On a request to add a drive to the device configuration, the requested
drive index was in use on the targeted device host.
¦ To avoid configuring a drive index that is already in use, use the Device
Configuration Wizard (on supported device discovery platforms). The wizard
automatically configures the drive index.
¦ If you use a device configuration interface that allows the drive index to be
specified, use tpconfig -d to determine the drive indexes already in use on
the targeted device host. Then specify a drive index that is not in use.

Device configuration status code 30
Message: Robot number is in use by another robot
Explanation: On a request to add or update a robotic drive in the device
configuration, the following occurred: the robot number and robot type specified
were associated with an existing robot of a different robot type.
Recommended Action: Check the device configuration on the targeted device
host and identify the configured robots.Onthe drive configuration request, specify
both the robot number and robot type that relate to the robot that contains the
drive.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration 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 *