Symantec NetBackup Device configuration status code 86 to status code 90

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

Device configuration status code 86
Message: Invalid Drive Name Rule
Explanation: A drive name rule was not specified, or contained an invalid
character.
¦ 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.
¦ Observe the rules for drive names:
¦ Cannot begin with a dash.
¦ Cannot exceed 48 characters.
¦ A literal field can only contain alphanumeric characters and plus (+), dash
(-), period (.), or underscore (_).
¦ An invalid field name was specified; check command usage.

Device configuration status code 87
Message: System Error
Explanation: An operating system error occurred.
¦ 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 adequate memory is available.
¦ Verify that Windows networking is properly installed.

Device configuration status code 88
Message: Invalid host
Explanation: Anattempt was made to add a device to a host that theEMMdatabase
does not recognize.
¦ 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 nbemmcmd -addhost to add the host to the EMM database.

Device configuration status code 89
Message: Drive name rule has exceeded its maximum length of 48 characters
Explanation: The specified drive name rule is too long.
¦ 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.
¦ Choose a shorter rule.

Device configuration status code 90
Message: Another device configuration is already in progress
Explanation: An instance of the Device Configuration Wizard or tpautoconf is
already running.
¦ 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.
¦ Retry the operation after the current instance is done.
¦ A lock on the device configuration cache may have been orphaned. Use the
nbemmcmd command to clear the lock, then retry the operation.

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 *