Details:
Overview:
There can be several causes for a Status 800 (resource request failed) with NetBackup (tm) 6.0. This error indicates that the NetBackup Policy Execution Manager (nbpem) was unable to get the required resources from the Enterprise Media Manager (EMM) processes. Typically, the Status 800 will indicate a failure to get an available drive for the backup, or the drive requested is the wrong density, or a storage unit is disabled. This error does not typically refer to system resources such as disk or memory, it refers to resources managed by the EMM server.
Not every resource request will fail with a Status 800. Here are some other situations that will fail with different error codes:
- A request for a storage unit that no longer exists will generate a Status 219.
- A request for a drive that no longer exists will generate a Status 213.
- A request for media of the wrong density, a request made when no media is available, will generate a Status 96.
· These situations will require different troubleshooting than a Status 800.
Troubleshooting:
Verify the drives in the required storage unit are in an "UP" status. If the drives are "DOWN" this can cause the backups to fail with a Status 800. The following is an example of a DOWN drive.
# /usr/openv/volmgr/bin/tpconfig -d
Id DriveName Type Residence
Drive Path Status
*************************************************
0 QUANTUM.DLT8000.000 dlt2 Standalone
/dev/rmt/0cbn DOWN
Currently defined robotics are:
EMM Server = starfury
Verify the storage unit is configured with the correct number of available drives. Also, verify the density of the storage unit has been set correctly and matches the available media. If this density is set incorrectly the storage unit will be unavailable and the backup can fail with a Status 800.
The following is an example of a dlt2 type storage unit that has been disabled and has no available drives.
# cd /usr/openv/netbackup/bin/admincmd
# bpstulist -label starfury-dlt2 -L
Label: starfury-dlt2
Storage Unit Type: Media Manager
Host Connection: starfury
Number of Drives: 0
On Demand Only: no
Density: dlt2 (15)
Robot Type: (not robotic)
Max Fragment Size: 1048576
Max MPX/drive: 4
Master Server Log Files:
The Unified logs on the EMM server will show the following errors for the backup job. Use the vxlogview command to look up the details for the Job ID that failed with a Status 800 (eg. Job ID 124) .
The following shows Unified logging for Job 307 with the errors highlighted in bold. In this example, the drives in the storage unit are down.
# /usr/openv/netbackup/bin/vxlogview -X "jobid=307" -d all
08/24/05 16:14:46.961 [Debug] NB 51216 mds 143 PID:16879 TID:5 [jobid=307] 1 [allocateTwin] EXIT STATUS = 2005009 (EMM_ERROR_DrivesDownMediaAvailable, All compatible drive paths are down, but media is available)
...
08/24/05 16:14:47.008 [Debug] NB 51216 nbjm 117 PID:16912 TID:1 [307 job_group_id=307 client=starfury type=4] 1 [BackupJob::ERMEvent] initial resource request failed, jobid = 307, requestId = -1, EMM status = All compatible drive paths are down, but media is available, NBU status = 800(BackupJob.cpp:289)
08/24/05 16:14:47.009 [Application] NB 51216 nbjm 117 PID:16912 TID:1 [307 job_group_id=307 client=starfury type=4] [Error] V-117-131 NBU status: 800, EMM status: All compatible drive paths are down, but media is available
..
08/24/05 16:14:47.040 [Application] NB 51216 nbpem 116 PID:16917 TID:7 [parent_jobid=-1,clientname=starfury,type=4] [Info] V-116-14 CLIENT starfury POLICY test-dlt SCHED FULL EXIT STATUS 800 (resource request failed)
08/24/05 16:14:47.059 [Application] NB 51216 nbpem 116 PID:16917 TID:7 [parent_jobid=-1,clientname=starfury,type=4] [Error] V-116-85 backup of client starfury exited with status 800 (resource request failed)
The following shows Unified logging for Job 310 with the errors highlighted in bold. In this example, the storage unit is disabled:
# /usr/openv/netbackup/bin/vxlogview -X "jobid=310" -d all
08/24/05 16:22:15.378 [Debug] NB 51216 mds 143 PID:16879 TID:4 [jobid=310] 1 [allocateTwin] EXIT STATUS = 2005045 (EMM_ERROR_STUNoMaxJobCount, Storage unit is disabled)
...
08/24/05 16:22:15.393 [Debug] NB 51216 nbjm 117 PID:16912 TID:4 [310 job_group_id=310 client=starfury type=4] 1 [BackupJob::ERMEvent] initial resource request failed, jobid = 310, requestId = -1, EMM status = Storage unit is disabled, NBU status = 800(BackupJob.cpp:289)
08/24/05 16:22:15.396 [Application] NB 51216 nbjm 117 PID:16912 TID:4 [310 job_group_id=310 client=starfury type=4] [Error] V-117-131 NBU status: 800, EMM status: Storage unit is disabled
...
08/24/05 16:22:15.439 [Application] NB 51216 nbpem 116 PID:16917 TID:9 [parent_jobid=-1,clientname=starfury,type=4] [Info] V-116-14 CLIENT starfury POLICY test-dlt SCHED FULL EXIT STATUS 800 (resource request failed)
08/24/05 16:22:15.467 [Application] NB 51216 nbpem 116 PID:16917 TID:9 [parent_jobid=-1,clientname=starfury,type=4] [Error] V-116-85 backup of client starfury exited with status 800 (resource request failed)
Resolution:
The following are some known causes of a Status 800 and how to correct them.
If the drives are down:
Ensure all the drives in the storage unit are in an "UP" state. If a drive is "DOWN" check the Windows Event Viewer or UNIX system logs (syslog, messages) for any hardware or SCSI errors that indicate why the drive was brought down. To manually put the drive in an "UP" state do the following:
1. Launch the NetBackup Administration Console
2. Go to the Device Monitor
3. Highlight any drives that appear as "DOWN"
4. Select Actions | Up Drive to up the drive
If the storage unit is misconfigured:
If all the drives are in an "UP" state, verify the storage unit is configured correctly. If the density of the storage unit is wrong or if there are no drives available, a Status 800 can occur.
1. Launch the NetBackup Administration Console
2. Go to Storage Units
3. Right-click the storage unit name and select Change
4. Correct any misconfigured settings such as incorrect density or the wrong number of drives
If necessary, delete and recreate the storage unit.
Additionally, if using the "Multiple Copies" or ITC (Inline Tape Copy) feature of a policy, specifying a Storage Unit directly instead of using "Any Available" has been known to resolve this issue.
E-Mail this document to a colleague 