Symantec NetBackup Media Manager status code 166 to status code 169

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

Media Manager status code 166
Message: media access port not available
Explanation: A request was made to physically move a volume into or out of a
robotic library, but the media access port was unavailable.
¦ 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.
¦ Ensure that the move request was not sent to a robotic control daemon or
process on a system that runs an older, incompatible software version.
¦ Ensure that the targeted robotic control daemon or process operates normally.

Media Manager status code 167
Message: ADAMM GUID is not unique in the database
Explanation: A volume entry that was added to or changed in the EMM database
had a specifiedADAMMGUID. It was a duplicate of theADAMMGUID for another
volume already in theEMMdatabase. All volumes in theEMMdatabase must have
an ADAMM GUID that is either unique or null. (ADAMM is Advanced Device and
Media Management, and a GUID is a Global Unique Identifier.)
¦ 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.
¦ From the daemon debug log file, determine the volume that has an ADAMM
GUID conflict with the volume entry that is added or changed.

Media Manager status code 168
Message: ADAMM GUID does not exist in database
Explanation: The EMM database was queried for a specified ADAMM (Advanced
Device and Media Management) GUID, and no volumes were found matching the
specified criteria. (The GUID is a Global Unique Identifier.)
Recommended Action:
Run vmphyinv for the media whose ADAMM GUID does not exist in the database.

Media Manager status code 169
Message: internal database access failure
Explanation: During an update of a drive status from a pre-6.0 NetBackup server
in EMM, a problem 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.
¦ Run the tpconfig -d or vmquery -a command to verify that the EMM server
is actively running and that it accepts new connections.

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 *