Please enter search query.
Search <book_title>...
Veritas NetBackup™ Status Codes Reference Guide
Last Published:
2018-09-19
Product(s):
NetBackup (8.1.2)
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
Media Manager status code 167
Explanation: A volume entry that was added to or changed in the EMM database had a specified ADAMM GUID. It was a duplicate of the ADAMM GUID for another volume already in the EMM database. All of the volumes in the EMM database must have an ADAMM GUID that is either unique or null. (ADAMM is Advanced Device and Media Management, and GUID is a Global Unique Identifier.)
Recommended Action:
Examine the command output (if available) and the daemon and reqlib debug logs for a more detailed message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup Logging Reference 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.