Forum Discussion

smith_jones's avatar
smith_jones
Level 6
10 years ago

maximum job count has been reached for the storage unit.

Hi,

I ran a policy manually and it got triggered. But only five drives were used for the child jobs and the sixth drive was not used. So one child job became in queue saying maximum job count has been reached for the storage unit. No backup was running on that drive.

I checked and found in the storage unit settings the "maximum concurrent write drives" is set to 6.

Also option "Limit jobs per policy" is not ticked in the policy setting.

Please suggest how to proceed so that that drive can be used.

 

 

 

7.5
Backup and Recovery
NetBackup
Windows Server (2003-2008)
  • Marianne's avatar
    Marianne
    10 years ago

    There may be orphaned resource allocations.

    If the orphaned allocation can be seen in the 'MDS Allocations' section of 'nbrbutil -dump' output, this allocation can be released with 'nbrbutil -releaseMDS <id> '

    Sometimes these orphaned allocations are hidden and can only be released with 'nbrbutil -resetall'.

    There should be no backups active when this command is run.

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    There may be orphaned resource allocations.

    If the orphaned allocation can be seen in the 'MDS Allocations' section of 'nbrbutil -dump' output, this allocation can be released with 'nbrbutil -releaseMDS <id> '

    Sometimes these orphaned allocations are hidden and can only be released with 'nbrbutil -resetall'.

    There should be no backups active when this command is run.

  • smith_jones's avatar
    smith_jones
    Level 6
    10 years ago

    I got this along with other sections after running the command  - 

     

    MDS allocations in EMM:

            MdsAllocation: allocationKey=527528 jobType=1 mediaKey=0 mediaId= driveK
    ey=0 driveName= drivePath= stuName=LocalTape masterServerName=mailbck1
    mediaServerName=mailbck1 ndmpTapeServerName= diskVolumeKey=0 mo
    untKey=0 linkKey=0 fatPipeKey=0 scsiResType=0 serverStateFlags=0

     

    How can I identify that this is orphaned allocation and if this is orphaned then which drive is it?

     

     

    Thanks.

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    Apologies for only responding now...

    I had the following typed up on Friday but seemed to forget to click 'Save':

    I cannot say without seeing all allocations and knowing which drives and media id's are in use.

    Having an allocation without a drive or media-id can possibly be seen as orphaned allocation.

    How many MdsAllocation in total in the output?

  • smith_jones's avatar
    smith_jones
    Level 6
    10 years ago

    We have 6 drives configured and now I ran the command and got -

    MDS allocations in EMM:

            MdsAllocation: allocationKey=528072 jobType=27 mediaKey=4000586 mediaId=
    0239 driveKey=0 driveName= drivePath= stuName= masterServerName=mailbck1
    mediaServerName= ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=
    0 fatPipeKey=0 scsiResType=0 serverStateFlags=0
            MdsAllocation: allocationKey=528087 jobType=27 mediaKey=4000419 mediaId=
    0445 driveKey=0 driveName= drivePath= stuName= masterServerName=mailbck1
    mediaServerName= ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=
    0 fatPipeKey=0 scsiResType=0 serverStateFlags=0
            MdsAllocation: allocationKey=528088 jobType=27 mediaKey=4000580 mediaId=
    0151 driveKey=0 driveName= drivePath= stuName= masterServerName=mailbck1
    mediaServerName= ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=
    0 fatPipeKey=0 scsiResType=0 serverStateFlags=0
            MdsAllocation: allocationKey=528092 jobType=10 mediaKey=4000419 mediaId=
    0445 driveKey=2000323 driveName=6 drivePath={1,0,4,0} stuName= masterServ
    erName=mailbck1 mediaServerName=mailbck1 ndmpTapeServe
    rName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 serverSta
    teFlags=1
            MdsAllocation: allocationKey=528093 jobType=10 mediaKey=4000586 mediaId=
    0239 driveKey=2000328 driveName=2 drivePath={1,0,2,0} stuName= masterServ
    erName=mailbck1 mediaServerName=mailbck1 ndmpTapeServe
    rName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 serverSta
    teFlags=1
            MdsAllocation: allocationKey=528094 jobType=9 mediaKey=4000325 mediaId=0226
    driveKey=2000312 driveName=3 drivePath={2,0,4,0} stuName=LocalTape ma
    sterServerName=mailbck1 mediaServerName=mailbck1 ndmpT
    apeServerName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 s
    erverStateFlags=1
            MdsAllocation: allocationKey=528095 jobType=27 mediaKey=4000577 mediaId=
    0170 driveKey=0 driveName= drivePath= stuName= masterServerName=mailbck1
    mediaServerName= ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=
    0 fatPipeKey=0 scsiResType=0 serverStateFlags=0
            MdsAllocation: allocationKey=528096 jobType=27 mediaKey=4000587 mediaId=
    0176 driveKey=0 driveName= drivePath= stuName= masterServerName=mailbck1
    mediaServerName= ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=
    0 fatPipeKey=0 scsiResType=0 serverStateFlags=0
            MdsAllocation: allocationKey=528097 jobType=27 mediaKey=4000585 mediaId=
    0240 driveKey=0 driveName= drivePath= stuName= masterServerName=mailbck1
    mediaServerName= ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=
    0 fatPipeKey=0 scsiResType=0 serverStateFlags=0
            MdsAllocation: allocationKey=528098 jobType=10 mediaKey=4000577 mediaId=
    0170 driveKey=2000303 driveName=1 drivePath={2,0,3,0} stuName= masterServ
    erName=mailbck1 mediaServerName=mailbck1 ndmpTapeServe
    rName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 serverSta
    teFlags=1
            MdsAllocation: allocationKey=528099 jobType=9 mediaKey=4000319 mediaId=
    0225 driveKey=2000277 driveName=5 drivePath={2,0,5,0} stuName=LocalTape ma
    sterServerName=mailbck1 mediaServerName=mailbck1 ndmpT
    apeServerName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 s
    erverStateFlags=1
            MdsAllocation: allocationKey=528100 jobType=9 mediaKey=4000503 mediaId=
    0227 driveKey=2000288 driveName=4 drivePath={1,0,3,0} stuName=LocalTape ma
    sterServerName=mailbck1 mediaServerName=mailbck1 ndmpT
    apeServerName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 s
    erverStateFlags=1

     

    So I guess the MDSAllocations that are not showing drive name  and media server name are orphaned allocations? Am I right?