Forum Discussion

FayezIT's avatar
FayezIT
Level 3
7 years ago
Solved

Not all resources are utilized in my SUG

Hi all,

I have a storage unit group that has two storage units (one is LTO5 tape library with two drives, and the other is LTO6 library with two drives).

the duplication to tape jobs write to the SUG, so it should utilize the 4 drives. and this is what was happening before. But now it only writes to one LTO, and the other duplication job will say "

awaiting resource B04-SUG. No drives are available.

 Any ideas of what could be the problem ?

  • Hi Marianne and Mph999

    We solved the problem, so i thought its worthy to post it here.
    It was windows driver problem. we removed all the drives and re-added them again after updating the windows driver and all is working fine. Now jobs are utilizing the 8 drives at the same time.

    Thanks a lot for your support.

8 Replies

  • Have you checked if all drives are UP?

    Or for orphaned/stuck drive or media allocations in nbrbutil -dump output? 

    • FayezIT's avatar
      FayezIT
      Level 3

      Hi Marianne

      All drives are up.
      Attached is the dump output

      the thing is that its writing to the LTO5 machine for example, then you will find it writing to the LTO6 machine (but not on both at the same time).

      • Marianne's avatar
        Marianne
        Level 6

        How many drives in total?

        There are 8 MDS allocations in EMM:

        4 drives seem to be in use - or some orphaned allocations?
        allocationKey=3285686 mediaId=O02164 driveName=HP.ULTRIUM6-SCSI.002 stuName=ae-eng-bmd-hp2-hcart3-robot-tld-2
        allocationKey=3286126 mediaId=O02165 driveName=HP.ULTRIUM6-SCSI.001 stuName=ae-eng-bmd-hp2-hcart3-robot-tld-2
        allocationKey=3288493 mediaId=M01830 driveName=HP.ULTRIUM6-SCSI.003 stuName=ae-eng-bmd-hp2-hcart3-robot-tld-1
        allocationKey=3288546 mediaId=M01840 driveName=HP.ULTRIUM5-SCSI.000 stuName=ae-eng-bmd-hp2-hcart2-robot-tld-0

        and then 4 allocations seemingly doing 'nothing' , probably waiting for resources: 
        allocationKey=3288491  mediaId=   driveName=  stuName= 
        allocationKey=3288492  mediaId=   driveName=  stuName= 
        allocationKey=3288544  mediaId=   driveName=  stuName= 
        allocationKey=3288545  mediaId=   driveName=  stuName= 

        You can try to release orphaned allocations with:
        nbrbutil -releaseMDS <allocationKey> 

        If this does not work, you can try to complely clear all resource allocations. This will however kill all active jobs.
        nbrbutil -resetAll