Symantec NetBackup Device configuration status code 31 to status code 35

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

Device configuration status code 31
Message: Robot number does not exist
Explanation: On a request to add or update a drive or robot in the device
configuration, the following occurred: the robot number and robot type specified
were not associated with any configured robots on the targeted device host.
Recommended Action: Check the device configuration on the targeted device
host and identify the configured robots. Every drive that is configured as a robotic
drive must already have its robot configured on that device host. Shared robotic
libraries having robotic control on a remote host must have a logical robotic entry
that refers to the remote host having robotic control. Add the robot to the device
configuration first. Then add the drive. Define it to be in the robot. If the robot
was already configured, specify the correct robot number and robot type on the
drive or the robot configuration request.

Device configuration status code 33
Message: Robot type must be controlled locally
Explanation: On a request to add or update a robot in the device configuration,
a remote control host was specified for a library type which does not support it.
¦ Check that you configured the correct robot type.
¦ Configure the device with local control by using its local device path.

Device configuration status code 34
Message: Drive name is already in use by another drive
Explanation: On a request to add or update a drive in the device configuration,
the requested drive path was in use on the targeted device host.
¦ To avoid configuring any paths that are already in use, use the Device
Configuration Wizard (on supported device discovery platforms). The wizard
automatically configures the drive paths.
¦ Before you make configuration changes, check the existing drive configuration
through a device configuration interface. Or run tpconfig -d to determine
the drive paths that are already in use on the targeted device host. Then specify
a drive path that is not already in use.

Device configuration status code 35
Message: Drive name does not exist
Explanation: On a request to update or delete a drive in the device configuration,
the following occurred: no drives having the specified drive name were found on
the targeted device host.
Recommended Action: Check the device configuration on the targeted device
host and identify the configured drives. When you make drive configuration
changes or deletions, specify the drive name as it is configured. Take care to use
the proper case.

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 *