Symantec NetBackup Device configuration status code 16 to status code 19
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 16 to status code 19 which may be received while using the Symantec NetBackup tool.
Device configuration status code 16
Message: A SCSI inquiry sent to the device has failed
Explanation: On a request to add or update a SCSI robotic library or drive, Media
Manager cannot obtain the device’s serial number and inquiry string. Media
Manager is obtains this information by sending a SCSI Inquiry command to the
device. Failure indicates that NetBackup was not able to communicate with the
device by means of SCSI.
¦ Ensure that the device is physically connected.
¦ Ensure that the operating system is configured to recognize the device and
that the operating system can see the device.
¦ Ensure that no other process uses the device and that the device is not offline.
Device configuration status code 17
Message: This robot type does not support multiple media types
Explanation: An attempt to add or update a robotic drive failed because the drives
in this robotic library are configured with a different drive type. (Some NetBackup
robotic library types do not support multiple media types.)
Refer to the NetBackup Release Notes or to the NetBackup Administrator’s Guide,
Volume II, for more information on which NetBackup robotic library types support
¦ Configure all drives for this robotic library with the same drive type.
¦ If you use NetBackup Server and want a robotic library with multiple media
types, contact Symantec to purchase NetBackup Enterprise Server.
Device configuration status code 18
Message: Invalid robot type
Explanation: On a request to modify the device configuration, the specified robot
type was invalid. Or it did not match the robot type for the robot that is associated
with the specified robot number.
¦ Check the device configuration for configured robots, and specify the correct
robot type applicable for the device configuration information being updated.
¦ 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 are at a compatible version level.
Device configuration status code 19
Message: Invalid device path name
Explanation: On a request to change the device configuration, the specified device
path or device name was not valid.
¦ To avoid configuring invalid device paths and device names, use the Device
Configuration Wizard (on supported device discovery platforms). The wizard
automatically configures device paths and device names.
¦ On Windows hosts, check the operating system configuration or registry for
device names and refer to the tpconfig command in NetBackup online Help.
Information for UNIX and Linux hosts is available
See the NetBackup Device Configuration Guide.
Always use no-rewind device files for drives that are attached to UNIX and
Linux hosts. Check to ensure that the specified device paths exist as
character-special files. Check for detailed errors from the command or the
user interface output.
Hope this was helpful.
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.