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: 2000
Explanation: The NetBackup Media and Device Selection component (MDS) did not allocate a new tape volume for backups. The storage unit has no more volumes available in the volume pool for this backup. NetBackup does not change storage units during the backup.
Recommended Action: Try the following:
Check the NetBackup Problems report to determine the storage unit that is out of media.
If the storage unit is a robot with empty slots, add more volumes and specify the correct volume pool. If no empty slots exist, move some media to non-robotic and add new volumes. If you have difficulty keeping track of your available volumes, try the available_media script located in the following directory:
On UNIX:
/usr/openv/netbackup/bin/goodies/available_media
On Windows:
install_path\NetBackup\bin\goodies\available_media.cmd
This script lists all volumes in the volume configuration, and information on the volumes currently assigned to NetBackup.
Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup needs a new tape and none are available in the current volume pool, it moves a tape from the scratch pool into the volume pool that the backup uses.
If the storage unit and volume pool appear to have media, verify the following:
Use the NetBackup Media List report to check if the volume is FROZEN or SUSPENDED. If so, use the bpmedia command to unfreeze it or unsuspend it, if so desired.
The volume has not expired or exceeded its maximum number of mounts.
The EMM database host name for the device is correct. If you change the EMM database host name, stop and restart the Media Manager device daemon (ltid for a UNIX server) or the NetBackup Device Manager service (Windows server).
The correct host is specified for the storage unit in the NetBackup configuration. The host connection must be the server (master or media) with drives connected to it.
The Media and Device Management volume configuration has media in the correct volume pool. Unassigned or active media is available at the required retention level. Use the NetBackup Media List report to show the retention levels, volume pools, and status for all volumes. Use the NetBackup Media Summary report to check for active volumes at the correct retention levels.
Create the bptm debug log directory, and set the MDS VxUL logging (OID 143) to debug level 2. Then retry the operation.
If this storage unit is new and this attempt to use it is the first, stop and restart NetBackup on the master server. The MDS unified logging files (OID 143) at debug level 2 usually show the NetBackup media selection process.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.