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. NetBackup status codes
  4. NetBackup status codes
  5. NetBackup status code: 83
NetBackup™ Status Codes Reference Guide

NetBackup status code: 83

Message: media open error

Explanation: The tape manager (bptm) or disk manager (bpdm) did not open the device or file that the backup or restore must use.

Recommended Action: For additional information, check the following:

  • NetBackup Problems report

  • Event Viewer Application log (Windows)

  • System log (UNIX)

  • Typically, this status code indicates a drive configuration problem that allows more than one process at a time to open the device. On UNIX, the problem may be due one or more of the following:

    • Two (or more) devices were configured that are the same physical device (for different densities perhaps). Verify that none of the /dev files that were used for these devices have the same major or minor numbers.

    • Links exist in the file system that allows users access to the drives.

    • The configuration for the drives was modified (in the administrator interface or vm.conf) and the Media Manager device daemon, ltid, was not restarted. Verify the configuration and then start ltid.

    On Windows, the problem may be that the Media and Device Management device configuration was modified but the NetBackup Device Manager service was not restarted. Verify the configuration and restart the NetBackup Device Manager service.

  • On Windows, make sure that the tapes are not write protected.

  • For detailed troubleshooting information:

    • Create a debug log directory for bpdm (if the device is disk) or bptm (if the device is tape).

    • On UNIX, restartltid in the verbose mode by running the following:

      /usr/openv/volmgr/bin/ltid -v

      Or, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create the vm.conf file if necessary.

    • On Windows, to enable verbose logging, add VERBOSE on a line by itself in the install_path\Volmgr\vm.conf file. Then, stop and restart the NetBackup Device Manager service.

    • Retry the operation and check the resulting debug log files.

    • On Windows systems, look at the install_path\VERITAS\NetBackup\db\media\errors log for a drive that frequently produces errors.

      On UNIX systems, look at the /usr/openv/netbackup/db/media/errors log (which is also included in the /usr/openv/netbackup/bin/support/nbsu script output) for a drive that frequently produces errors.

Click here to view technical notes and other information on the Cohesity Technical Support website about this status code.

Feedback

Was this page helpful?
Previous

NetBackup status code: 82

Next

NetBackup status code: 84

Feedback

Was this page helpful?