Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Status Codes Reference Guide
  3. Media Manager status codes
  4. Media Manager status codes
  5. Media Manager status code 167
NetBackup™ Status Codes Reference Guide

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 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.

Feedback

Was this page helpful?
Previous

Media Manager status code 166

Next

Media Manager status code 168

Feedback

Was this page helpful?