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

NetBackup status code: 219

Message: the required storage unit is unavailable

Explanation: The policy or schedule for the backup requires a specific storage unit, which is currently unavailable. This error also occurs for other tries to use the storage unit within the current backup session.

Recommended Action: Look in the Job Details window for the failed job.

  • Verify that the schedule specifies the correct storage unit and the storage unit exists.

  • Verify that the following devices are running: the Media Manager device daemon (ltid) (UNIX or Linux server) or the NetBackup Device Manager service (Windows server). Use bpps on UNIX and Linux and the Activity Monitor on Windows or the Services application in the Windows Control Panel.

  • Verify the following attribute settings:

    • For a disk storage unit, Maximum concurrent jobs is not set to 0.

    • For a Media Manager storage unit, the Maximum concurrent drives attribute is not set to 0.

  • If the storage unit is a tape, verify that at least one of the drives is in the UP state. Use the Device Monitor.

  • Verify that the robot number and host in the storage unit configuration match what is specified in the Media and Device Management device configuration.

  • Verify that the master server can communicate with the bpcd process on the server that has the storage unit.

    • Verify that bpcd listens on the port for connections.

      On a UNIX or Linux server where the storage unit is connected, if you run netstat -a | grep bpcd, it should return something similar to the following:

      *.bpcd   *.*        0      0     0      0 LISTEN

      On a Windows NetBackup server where the storage unit is connected, run netstat -a to print several lines of output. If bpcd listens, one of those lines is similar to the following:

      TCP    myhost:bpcd           0.0.0.0:0              LISTENING
    • Check the nbrb and the mds logs by using the vxlogview command.

    • If the cause of the problem is not obvious, perform some of the steps in the following procedure:

      See Resolving Network Communication Problems in the NetBackup Troubleshooting Guide.

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

Feedback

Was this page helpful?
Previous

NetBackup status code: 218

Next

NetBackup status code: 220

Feedback

Was this page helpful?