Symantec NetBackup Media Manager status code 36 to status code 40

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 36 to status code 40 which may be received while using the Symantec NetBackup tool.

Media Manager status code 36
Message: barcode not unique in database
Explanation: A specified bar code in an added or a changed volume entry in the
EMM database duplicated a volume bar code already in the database. All volumes
in the EMM database must have a unique bar code.
¦ Examine command output (if available) and the daemon and reqlib debug logs
for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Query or sort volume records by bar code to identify the volume entry with
the duplicate bar code.

Media Manager status code 37
Message: robotic volume position is already in use
Explanation: A robotic coordinate in an added or a changed volume entry in the
EMMdatabase duplicated a volume robotic coordinate in the database. (The robotic
coordinate includes the slot number or the slot number and platter side.) All
volumes in the EMM database must have unique robotic coordinates.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Query or sort volume records by slot number to identify the volume entry with
the duplicate robotic coordinate.
¦ Change (update or move volume) or delete the existing volume entry if it does
not reflect the following: the correct robotic coordinate corresponding to the
volume’s storage position in the robotic library. If a volume is currently in a
drive, the EMM database should still reflect the volume’s home slot.

Media Manager status code 39
Message: network protocol error
Explanation: An attempt to read data from a socket failed.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message on the protocol error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Verify that the server being connected to is operational.

Media Manager status code 40
Message: unexpected data received
Explanation: Message communications (handshaking) was not correct.
¦ Verify that the correct version of software is running on all servers.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message on the protocol error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Retry the operation and examine the logs.
¦ Ensure that no embedded whitespaces exist in the fields that do not allow
embedded whitespace.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Media Manager 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 *