NBU status: 830, EMM status: No drives are available

[Spooky7k]

Hello,

I have the following error when the duplication begin.

The error occurred on Friday and since then I'm struggling to fix it.

In device monitor the drive is up and running.

Now the disk pool is full and I get many duplication errors.

NBU status: 830, EMM status: No drives are available

I tried to remove and add the robot and the drive again but without any results.

The media server is active, all the SU, SUG and SLP are configured and are looking fine.

HP.ULTRIUM6-SCSI.002     No      No                     No        hcart
    ro-xxxxx    {2,2,1,0}                            TLD

I also tried to restart the library, media server, remove the lock files, reset the LTID flag.

The density for drive and tape is same

Any ideas?

Please help me yo resolve this error.

[RamNagalla]

please post the below details to anylize the issue. you can send me a private message if you are not comfortable to post the outputs here.

1) detail status of the failed job

2) tpconfig -d output from media server

3) SLP configuration snapshot or from nbstl output for specific SLP

4) selected media servers in stroage server and Storage unit for Disk STU(selected in SLP)

5) Tape stu snapshot or output form nbstulit for specific tape stu selected in SLP

[Marianne]

Ram is correct. We need to see all config. Not just drive status.

[Spooky7k]

Hello,

First of all thank you for your reply.Below please find the results

2) Id  DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************
0   HP.ULTRIUM6-SCSI.002 hcart  TLD(1)  DRIVE=1
      {2,2,1,0}                                                        UP

Currently defined robotics are:
  TLD(1)     SCSI coordinates = {2,2,1,1}

EMM Server = ro-bs01********

[Spooky7k]

After a restart of whole enviroment I got this error

07/23/2017 12:22:12 - begin Duplicate

07/23/2017 12:22:12 - requesting resource LCM_STUG_RO_WH005_TAPE_01

07/23/2017 12:22:12 - granted resource  LCM_STUG_RO_WH005_TAPE_01

07/23/2017 12:22:12 - started process RUNCMD (pid=2788)

07/23/2017 12:22:12 - ended process 0 (pid=2788)

07/23/2017 12:22:13 - requesting resource STUG_RO_WH005_TAPE_01

07/23/2017 12:22:13 - requesting resource @aaaaH

07/23/2017 12:22:13 - reserving resource @aaaaH

07/23/2017 12:22:13 - awaiting resource STUG_RO_WH005_TAPE_01. Waiting for resources. 
          Reason: Tape media server is not active, Media server: ro-005bs01, 
          Robot Type(Number): TLD(1), Media ID: N/A, Drive Name: N/A, 
          Volume Pool: ENCR_RO_WH005_WEK_01, Storage Unit: STU_RO-005BS01_RO-005LIB01_01, Drive Scan Host: N/A, 
          Disk Pool: N/A, Disk Volume: N/A 

07/23/2017 12:29:56 - resource @aaaaH reserved

07/23/2017 12:29:56 - granted resource  W517L6

07/23/2017 12:29:56 - granted resource  HP.ULTRIUM6-SCSI.002

07/23/2017 12:29:56 - granted resource  STU_RO-005BS01_RO-005LIB01_01

07/23/2017 12:29:56 - granted resource  MediaID=@aaaaH;DiskVolume=L:\;DiskPool=DP_RO-005BS01_ADVD_01;Path=L:\;StorageServer=ro-005bs01;MediaServer=ro-005bs01

07/23/2017 12:29:58 - Info bpduplicate (pid=2788) Suspend window close behavior is not supported when the target destination is a storage unit group

07/23/2017 12:29:58 - Info bpduplicate (pid=2788) window close behavior: Continue processing the current image

07/23/2017 12:29:59 - Info bptm (pid=3240) start

07/23/2017 12:29:59 - started process bptm (pid=3240)

07/23/2017 12:30:01 - Info bptm (pid=3240) start backup

07/23/2017 12:30:02 - Info bpdm (pid=5436) started

07/23/2017 12:30:02 - started process bpdm (pid=5436)

07/23/2017 12:30:02 - Info bpdm (pid=5436) reading backup image

07/23/2017 12:30:03 - Info bpdm (pid=5436) using 128 data buffers

07/23/2017 12:30:03 - Info bptm (pid=3240) Waiting for mount of media id W517L6 (copy 2) on server ro-005bs01

07/23/2017 12:30:03 - Info bpdm (pid=5436) requesting nbjm for media

07/23/2017 12:30:03 - started process bptm (pid=3240)

07/23/2017 12:30:03 - mounting W517L6

07/23/2017 12:30:03 - Info bptm (pid=3240) INF - Waiting for mount of media id W517L6 on server ro-005bs01 for writing.

07/23/2017 12:30:04 - begin reading

07/23/2017 12:30:43 - Warning bptm (pid=3240) media id W517L6 load operation reported an error

07/23/2017 12:30:43 - current media W517L6 complete, requesting next media Any

07/23/2017 12:30:48 - Error bptm (pid=3240) NBJM returned an extended error status: No drives are available (2001)

07/23/2017 12:30:48 - Error nbjm (pid=7408) NBU status: 830, EMM status: No drives are available

07/23/2017 12:30:50 - Info bptm (pid=3240) EXITING with status 252 <----------

07/23/2017 12:30:56 - Error bpduplicate (pid=2788) host ro-005bs01 backup id ro-005as01_1500670066 read failed, termination requested by administrator (150).

07/23/2017 12:30:56 - Error bpduplicate (pid=2788) host ro-005bs01 backupid ro-005as01_1500670066 write failed, extended error status has been encountered, check logs (252).

07/23/2017 12:30:56 - Error bpduplicate (pid=2788) Duplicate of backupid ro-005as01_1500670066 failed, extended error status has been encountered, check logs (252).

07/23/2017 12:30:56 - requesting resource @aaaaH

07/23/2017 12:30:56 - granted resource  MediaID=@aaaaH;DiskVolume=L:\;DiskPool=DP_RO-005BS01_ADVD_01;Path=L:\;StorageServer=ro-005bs01;MediaServer=ro-005bs01

07/23/2017 12:30:58 - Info bptm (pid=5528) start

07/23/2017 12:30:58 - started process bptm (pid=5528)

07/23/2017 12:30:58 - Error bptm (pid=5528) NBJM returned an extended error status: No drives are available (2001)

07/23/2017 12:30:58 - Error bpduplicate (pid=2788) write host ro-005bs01: extended error status has been encountered, check logs (252)

07/23/2017 12:30:58 - Error bpduplicate (pid=2788) Duplicate of backupid ro-005sr02_1500670076 failed, extended error status has been encountered, check logs (252).

07/23/2017 12:30:58 - Error bptm (pid=5528) nbjm_media_request() failed: 2001, cannot continue with copy 1

07/23/2017 12:30:58 - Error bptm (pid=5528) INF - No drives are available (2001), cannot continue with copy 2

07/23/2017 12:30:58 - Info bptm (pid=5528) EXITING with status 252 <----------

07/23/2017 12:30:58 - requesting resource STU_RO-005BS01_RO-005LIB01_01

07/23/2017 12:30:58 - Error nbjm (pid=7408) NBU status: 830, EMM status: No drives are available

07/23/2017 12:30:59 - Info bptm (pid=596) start

07/23/2017 12:30:59 - started process bptm (pid=596)

07/23/2017 12:30:59 - Error bptm (pid=596) NBJM returned an extended error status: No drives are available (2001)

07/23/2017 12:30:59 - Error bpduplicate (pid=2788) write host ro-005bs01: extended error status has been encountered, check logs (252)

07/23/2017 12:30:59 - Error bpduplicate (pid=2788) Duplicate of backupid ro-005as01t_1500673449 failed, extended error status has been encountered, check logs (252).

07/23/2017 12:30:59 - Error bptm (pid=596) nbjm_media_request() failed: 2001, cannot continue with copy 1

07/23/2017 12:30:59 - Error bptm (pid=596) INF - No drives are available (2001), cannot continue with copy 2

07/23/2017 12:30:59 - Info bptm (pid=596) EXITING with status 252 <----------

07/23/2017 12:30:59 - requesting resource STU_RO-005BS01_RO-005LIB01_01

07/23/2017 12:30:59 - Error nbjm (pid=7408) NBU status: 830, EMM status: No drives are available

07/23/2017 12:31:00 - Info bptm (pid=5308) start

07/23/2017 12:31:00 - started process bptm (pid=5308)

07/23/2017 12:31:00 - Error bptm (pid=5308) NBJM returned an extended error status: No drives are available (2001)

07/23/2017 12:31:00 - Error bptm (pid=5308) nbjm_media_request() failed: 2001, cannot continue with copy 1

07/23/2017 12:31:00 - Error bptm (pid=5308) INF - No drives are available (2001), cannot continue with copy 2

07/23/2017 12:31:00 - Info bptm (pid=5308) EXITING with status 252 <----------

07/23/2017 12:31:00 - requesting resource STU_RO-005BS01_RO-005LIB01_01

07/23/2017 12:31:00 - Error nbjm (pid=7408) NBU status: 830, EMM status: No drives are available

07/23/2017 12:31:01 - Error bpduplicate (pid=2788) write host ro-005bs01: extended error status has been encountered, check logs (252)

07/23/2017 12:31:01 - Error bpduplicate (pid=2788) Duplicate of backupid ro-005as05._1500685237 failed, extended error status has been encountered, check logs (252).

07/23/2017 12:31:01 - Error bpduplicate (pid=2788) Status = no images were successfully processed.

07/23/2017 12:31:01 - end Duplicate; elapsed time 0:08:49

no images were successfully processed  (191)

[Marianne]

Did you have a good look yourself at the info that you posted?

You show us config of a single robot TLD (1) with a single tape drive.
The you show us the STU config that says TLD (1) has 4 (FOUR) tape drives!!!!!

The STUG shows 2x STUs for TLD (0) and 2x TLD (5) plus some advanced disk.

If you expect NBU to use the 1 tape drive in TLD(1), then you need to change the STU's Max Concurrent drive to 1 and change SLP destination to this STU.

[RamNagalla]

hello,

Thank you very much for the details.

1) Media server is configured with only one tape drive.so no redendancy if drive goes bad.

2) Media owner in SLP does not look correct, you may need to correct this as well.

however current issue seems to be with the tape drive, it got allocation with correct STU and drive, however tape was not able to load into the drive.

07/23/2017 12:30:43 - Warning bptm (pid=3240) media id W517L6 load operation reported an error

07/23/2017 12:30:43 - current media W517L6 complete, requesting next media Any

so have you seen drive went down after the  posted job got failed?

i would suggest you to start with robtest and see if you can manually mount and dismount the tape into the drive, if you are not able to that is something you need to deal with hardware.

if robtest is successfull, then we need to cross the tape dirve confiuration or remove and reconfigure it from Device configuration wizard(NOT from CLI) to make sure drive is configured correclty.

then perform the test backups to make sure it is workig fine.

[Marianne]

@Spooky7k

Apologies for misreading STUG config.

I see you have a single STU in the group - STU_RO-005BS01_RO-005LIB01_01.
Why not explicitly select the STU?

Anyway - the STU config is wrong - number of concurrent write drives MUST be changed to 1.

NBU will try to initiate jobs for 4 drives instead of 1.