Veritas NetBackup™ Status Codes Reference Guide
- 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
NetBackup status code: 219
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,
is not set to 0.For a Media Manager storage unit, the
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 in the Veritas Knowledge Base about this status code.