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 35
NetBackup™ Status Codes Reference Guide

Media Manager status code 35

Message: volume does not exist in database

Explanation: A requested operation encountered a case where a volume query did not return a volume entry that matched the search criteria.

Recommended Action:

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

  • Ensure that volumes are configured properly on the EMM server that matches the EMM server configured for the robot or set of standalone drives. Use tpconfig -d to list the configured EMM server.

  • Do the following so the volume query can find a matching volume: update the volume or the device configurations, specify the correct EMM server, modify volume properties, or adjust search criteria.

  • If you run vmphyinv, none of the media satisfies the search criterion. As such, vmphyinv cannot inventory the tape library.

Feedback

Was this page helpful?
Previous

Media Manager status code 34

Next

Media Manager status code 36

Feedback

Was this page helpful?