Symantec NetBackup Device configuration status code 48 to status code 55

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

Device configuration status code 48
Message: RSM is not supported.
Explanation: On a request to make a device configuration change, the RSM
(Microsoft Removable Storage Manager) robot type was specified, but it is no
longer supported.
Recommended Action: Use a supported Media Manager robot type.

Device configuration status code 49
Message: global device database host name is invalid.
Explanation: On a device configuration request, the EMM server name cannot
be obtained.
TheEMMserver name is obtained through an internal request to read the bp.conf
file (or Windows registry). This request is likely to fail if the EMMSERVER entry
is not set.
RecommendedAction: Use tpautoconf -get_gdbhost on a device host to obtain
itsEMMserver name. Use tpautoconf -set_gdbhost to set theEMMserver name,
as needed.

Device configuration status code 51
Message: No compatible device is registered at these SCSI coordinates.
Explanation: On a request to add or change robot or drive information in the
device configuration, the following occurred: the specified SCSI coordinates did
not correspond to a device in the system registry. This status code applies to
Windows systems only.
RecommendedAction: To avoid manually specifying SCSI coordinates (port, bus,
target, and LUN), use the Device Configuration Wizard. The wizard fully automates
(on supported device discovery platforms) device configuration requests. Or use
the Media and Device Management interface to browse for devices in the system
registry. Check the operating system registry to ensure that devices are present
at the specified coordinates when SCSI coordinates are manually configured.

Device configuration status code 52
Message: The device name is not valid, no device responded.
Explanation: On a request to add or change robot or drive information in the
device configuration, the following occurred: no device was found in the system
registry with the specified device name. This error code applies to Windows
systems only.
Recommended Action: To avoid manually specifying the device name, use the
Device Configuration Wizard. The wizard fully automates (on supported device
discovery platforms) device configuration requests. Or use the Media And Device
Management interface to browse for devices in the system registry. Check the
operating system registry to ensure that devices are present at the specified
coordinates when devices are manually configured.

Device configuration status code 53
Message: Shared Storage Option (SSO) is not licensed
Explanation: An attempt to add a path to a drive failed. It failed because the SSO
license was not installed.
¦ 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 an active SSO license is installed on all servers that have a path
configured to this drive and the server where this operation is performed.

Device configuration status code 55
Message: Invalid NDMP hostname
Explanation: An invalid hostname or no hostname was specified.
¦ 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.
¦ Use tpconfig -dnh to verify that the host has been configured.
¦ Check the usage of the tpautoconf -list_snapvault_volumes command.

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 *