Symantec NetBackup Device configuration status code 11 to status code 15

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

Device configuration status code 11
Message: Invalid Usage
Explanation: One of the Media Manager device configurationcommands(tpconfig
or tpautoconf) was executed with improper options. Or an incompatibility exists
between components or versions of the product.
¦ 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.
¦ Check the tpconfig or the tpautoconf usage statement for expected usage
and compare with the parameters being sent to start the new process.
¦ Verify that all Media Manager binaries are at a compatible version level.

Device configuration status code 13
Message: Failed reading drive or robot config file
Explanation: A request was made to list the device configuration, but an error
was encountered while reading from the EMM database.
¦ Examine the daemon debug log 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 nbemm is running. Display the device configuration to determine
whether or not the database is corrupt. Restore a saved copy of the databases
from catalog backups, or delete them and recreate the device configuration as
needed.

Device configuration status code 14
Message: Invalid drive index
Explanation: A request was made to add, update, or list a drive configuration
entry, and the specified drive index was not associated with a configured drive.
¦ Display the device configuration to obtain the list of valid drives. Avoid making
device configuration changes from multiple sources simultaneously.
¦ If more information is needed, examine the daemon debug log and command
or interface output for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Device configuration status code 15
Message: Invalid robot number
Explanation: On a request to modify the device configuration, the specified robot
number was not within the allowable range, the robot number did not correspond
to a currently configured robot, or the robotic database is corrupted.
¦ Specify a robot number in the range of 0 to 32767.
¦ Ensure that all device configuration changes or deletions are performed on
the devices that are currently part of the device configuration.
¦ Verify that nbemm is running. Restore a saved copy of the robotic database from
catalog backups, or delete it and recreate any needed robotic configuration
information.

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 *