Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Error nbjm (pid=293) NBU status: 800, EMM status: No drives are available resource request failed (800)"

Created: 19 Apr 2013 | 11 comments

Hi Team,

  Need help regarding the error "Error nbjm (pid=293) NBU status: 800, EMM status: No drives are available 

resource request failed (800)" 

 

 i try to reconfigured the tape drive using the configure storage and it was ok, but if i try to start manually it was failed.

the how to locate the string 

" Try the following: 

Locate the EMM reason string, correct the problem, and rerun the job.

Operating Systems:

Comments 11 CommentsJump to latest comment

Marianne's picture

Please show us output of all of these commands:

<install-path>\veritas\netbackup\bin\admincmd\bpstulist -U

<install-path>\veritas\netbackup\bin\admincmd\bppllist <policy-name> -U   (for policy that is failing)

<install-path>\veritas\volmgr\bin\scan

<install-path>\veritas\volmgr\bin\tpconfig -l

<install-path>\veritas\volmgr\bin\vmoprcmd -d

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Agent47's picture

Hi Team,

 

 

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
 
====================================================================
 
bpstulist -U
 
Label:                phm-intra003-hcart
Storage Unit Type:    Media Manager
Host Connection:      phm-intra003
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        1
Density:              hcart - 1/2 Inch Cartridge
Robot Type:           (not robotic)
Max Fragment Size:    1048576 MB
 
 
D:\coreutil\VERITAS\NetBackup\bin\admincmd>bppllist nb_database -U
------------------------------------------------------------
 
Policy Name:       nb_database
 
  Policy Type:         MS-Windows-NT
  Active:              yes
  Effective date:      12/19/2012 15:24:01
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         NetBackup
  Keyword:             (none specified)
 
  HW/OS/Client:  PC            WindowsNET    Server
 
  Include:  D:\coreutil\VERITAS\nb_database
 
  Schedule:          w_8w_f
    Type:            Full Backup
    Frequency:       every 7 days
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 4 (28 days)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
      EXCLUDE DATE 0 - 12/24/2012
      EXCLUDE DATE 1 - 12/25/2012
      EXCLUDE DATE 2 - 12/31/2012
      EXCLUDE DATE 3 - 01/01/2013
    Daily Windows:
 
  Schedule:          d_2w_f
    Type:            Full Backup
    Frequency:       every 1 day
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 1 (13 days)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
      EXCLUDE DATE 0 - 12/24/2012
      EXCLUDE DATE 1 - 12/25/2012
      EXCLUDE DATE 2 - 12/31/2012
      EXCLUDE DATE 3 - 01/01/2013
    Daily Windows:
 
 
 
=============================================================================
scan
 
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name  : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 3; Bus: 0; Target: 3; LUN: 0
Inquiry    : "HP      Ultrium 1-SCSI  E32D"
Vendor ID  : "HP      "
Product ID : "Ultrium 1-SCSI  "
Product Rev: "E32D"
Serial Number: "HUB1H03GLY"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "HP      Ultrium 1-SCSI  HUB1H03GLY"
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
 
=================================================================================
 
Device Robot Drive       Robot                    Drive                 Device
 
Type     Num Index  Type DrNum Status  Comment    Name                  Path
 
drive      -    0  hcart    -      UP  -          HP.ULTRIUM1-SCSI.000  {3,0,3,0
}
 
========================================================================
 
                                PENDING REQUESTS
 
                                     <NONE>
 
                                  DRIVE STATUS
 
Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart    AVR                -                     No       -         0
 
                             ADDITIONAL DRIVE STATUS
 
Drv DriveName            Shared    Assigned        Comment
  0 HP.ULTRIUM1-SCSI.000  No       -
 
Marianne's picture

All looks OK. Probably stuck resource allocation.
Try the following (in admincmd folder)
nbrbutil -resetall

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mph999's picture

Hi,

Marianne as always has given outstanding advice.

Couple of things I would add.

When logging the post give more detail - In this instance I would want to know how many jobs you had runniing when you got the 'no drives available warning' as well as a description of how many drives you have in total.

An addional command that would be useful is :

nbrbutil -dump

This would show if the drive is reserverd in nbrb.

I suspect that the nbrbutil -resetall command, as suggested by Marianne will bring your drive back to life.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Agent47's picture

 

Hi Team,
 
Don't know how to read this?
need help.
:-(
Allocation Requests
(AllocationRequestSeq 
index=0 (AllocationRequest: id={83B2B978-5907-4D43-971D-7A2866589466} priority=0 secondPriority=1366642800 userid=jobid=106 description=THE_BACKUP_JOB-106-{83B2B978-5907-4D43-971D-7A2866589466} (RequestSeq 
index=0 (Request provider=MPXProvider resourcename=MpxRequest-106  userSequence=-1 (MPXGroupRequest maxmpx=1 media=(RequestSeq 
index=0 (Request provider=DriveOperationProvider resourcename=__ANY__  userSequence=0 (StorageUnitRequest: storageUnit=(StorageUnitRequest: storageUnit=__ANY__ mediaPool=NetBackup retentionLevel=1 mustUseLocalMediaServer=no mpxRequired=no mustBeNdmp=no getMaxFreeSpace=no minFreeSpaceKBytes=0 usageType=1 client=server) preferredMediaServer= requiredMediaServer= previousStuName= previousStuType=0)))
))
index=1 (Request provider=NamedResourceProvider resourcename=server.NBU_CLIENT.MAXJOBS.server  userSequence=-1 (CountedResourceRequest resourcename=server.NBU_CLIENT.MAXJOBS.server max=1))
index=2 (Request provider=NamedResourceProvider resourcename=server.NBU_POLICY.MAXJOBS.server  userSequence=-1 (CountedResourceRequest resourcename=server.NBU_POLICY.MAXJOBS.server max=2147483647)))
))
 
 
Allocations 
(AllocationSeq 
index=0 (Allocation: id={003FEA2C-C658-4D68-BB02-AF71C90BBC06} provider=NamedResourceProvider resourcename=server.NBU_CLIENT.MAXJOBS.server masterserver=server groupid={00000000-0000-0000-0000-000000000000} userSequence=-1 userid="jobid=106" unknown allocation data object)
index=1 (Allocation: id={E94DF613-03D3-4788-BD68-4E4FFFF5001F} provider=NamedResourceProvider resourcename=server.NBU_POLICY.MAXJOBS.server masterserver=server groupid={00000000-0000-0000-0000-000000000000} userSequence=-1 userid="jobid=106" unknown allocation data object)
index=2 (Allocation: id={03615D63-9FC3-477A-8C0A-EC0121C1EBF3} provider=MPXProvider resourcename=anMPXGroup masterserver=server groupid={859D356B-7995-494F-A560-5AC9E8ECB3A9} userSequence=-1 userid="jobid=106" (MPXGroupAllocation: groupId={859D356B-7995-494F-A560-5AC9E8ECB3A9}))
index=3 (Allocation: id={897912A5-06A4-48DB-803C-3D259C60D14D} provider=MPXProvider resourcename=server-hcart masterserver=server groupid={859D356B-7995-494F-A560-5AC9E8ECB3A9} userSequence=0 userid="jobid=106" (Media_Drive_Allocation_Record: allocationKey=88 (Media_Drive_Record: MediaKey=4000002 MediaId=MON02A MediaServer=server DriveKey=0 DriveName= PrimaryPath= PoolName=NetBackup RobotNum=0 RobotType=0 MediaTypeName=NetBackup HCART1 DriveTypeName= NdmpControlHost= RetentionLevel=1 PolicyType=2 JobType=1 MasterServer=server) (Storage_Unit_Record: STU=server-hcart STUType=2 MasterServer=server MediaServer=server RobotType=0 RobotNumber=-1 Density=6 OnDemandOnly=0 ConcurrentJobs=1 ActiveJobs=0 MaxMultiplexing=1 NdmpAttachHost= AbsolutePath=) (Bptm_Strings_Record: 0="MEDIADB 1 88 MON02A 4000002 ------ 6 1366731231 0 0 0 0 0 0 4 1 0 0 0 0 0 0" 1="VOLUME 1 MON02A 4000002 -------- NetBackup *NULL* *NULL* 6 0 0 0 0 {00000000-0000-0000-0000-000000000000} 0" 2="DRIVE 2 *NULL* 0 *NULL* *NULL* 0 0 0 0 0 0 0 0 *NULL* *NULL* *NULL* *NULL* 0 1" 3="STORAGE 0 server-hcart 6 1048576" ) TpReqFileName=)))
 
MDS allocations in EMM: 
 
MdsAllocation allocationKey=88 jobType=1 mediaKey=4000002 mediaId=MON02A driveKey=0 driveName= drivePath= stuName=server-hcart masterServerName=server mediaServerName=server ndmpTapeServerName=
 

 

Dyneshia's picture

Since you mentioned you tried to reconfigure the devices, I would :

Install the latest device mappings - http://www.symantec.com/docs/TECH129536

     -  Symantec is constantly updating them so be sure subscribe to the tech note for to receive alerts when a new version is released.

     -  To confirm what version you are on :

        C:\Program Files\VERITAS\Volmgr\bin\tpext -get_dev_mappings_ver

CONFIRM NO BACKUPS ARE RUNNING

Release all allocations to devices

   From the command line: Install_path\Veritas\NetBackup\bin\admincmd>nbrbutil -resetAll

      (If backups are running, this will cause them to fail. This is why no backups should be running )

Delete all devices - Ref http://www.symantec.com/docs/TECH64327

     OPTION 1 – Delete ALL devices.

      From the command line: Install_path\Veritas\NetBackup\bin\admincmd>nbemmcmd -deletealldevices

  OPTION 2 – Delete all devices on a specified media server.

   From the command line: Install_path\Veritas\NetBackup\bin\admincmd>nbemmcmd -deletealldevices -machinename -machinetype media

Next use the device configuration wizard to configure your devices.

    - Be sure there are no errors during the wizard or any "unused element" . If so, drag the tape drive to the robot in the wizard.

Last Inventory the robot(s) and test.

Please see : https://www-secure.symantec.com/connect/articles/2...

Agent47's picture

it does'nt work :-(

 

it seem there was a compatible issue.or the cartridge is not compatible?

 

Marianne's picture

This section of your output is all that's important:

 

MDS allocations in EMM: 
 
MdsAllocation allocationKey=88 jobType=1 mediaKey=4000002 mediaId=MON02A driveKey=0 driveName= drivePath= stuName=server-hcart masterServerName=server mediaServerName=server ndmpTapeServerName=
 

You have a stuck media allocation: MON02A

There is no drive allocation. but media allocation always assumes drive allocation. 

As per my previous post, 'nbrbutil -resetall' will fix this.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Agent47's picture

Dymeshia, Yes, i already run the resetall command, but the cartridge is not visible. and when i try to run manual backups, it create pending request tape.

 

apoligezed for my late response. MArianne