cancel
Showing results for 
Search instead for 
Did you mean: 

problem tape drive , control = TLD , Ready = NO

I have a NetBackup 7.7.1 master server with a tape library that has 4 tape drives. From the NetBackup Console I see 3 tape drives are active and 3 is ready and has a tape in, the other one drive is NO ready and Control=TLD. There're a couple of backup jobs queued and the reason is " awaiting resource Any - No drives are available" .

Tags (2)
1 Solution

Accepted Solutions
Accepted Solution!

Re: problem tape drive , control = TLD , Ready = NO

There is an allocation for 1 piece of media that has no tape drive associated with it:

MdsAllocation: allocationKey=550642 jobType=16 mediaKey=4000075 mediaId=000115 driveKey=0 driveName= drivePath= stuName= masterServerName=netbackup mediaServerName=netbackup

Looking at the allocationKey number - 550xxx vs 553xxx of the other 3 active drives and media, it seems that it has been 'stuck' there for a while. Although there is no drive assiociated with this media allocation, the resource broker automatically assumes that a drive is needed and will therefore not allocate the 4th drive.

Please release this allocation: 
nbrbutil -releaseMDS 550642

View solution in original post

6 Replies

Re: problem tape drive , control = TLD , Ready = NO

@prot1 

First thing to check is Storage Unit config - how many drives configured for concurrent use?

If STU is configured for 4 drives, check for 'orphaned' resource allocations. 
Run 'nbrbutil -dump' from cmd and post the MdsAllocation section. 

Re: problem tape drive , control = TLD , Ready = NO

MdsAllocation: allocationKey=550642 jobType=16 mediaKey=4000075 mediaId=000115 driveKey=0 driveName= drivePath= stuName= masterServerName=netbackup mediaServerName=netbackup ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=0 serverStateFlags=0
MdsAllocation: allocationKey=553772 jobType=1 mediaKey=4000087 mediaId=000127 driveKey=2000104 driveName=HP.ULTRIUM5-SCSI.002 drivePath=/dev/nst3 stuName=quantum masterServerName=netbackup mediaServerName=netbackup ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 serverStateFlags=1
MdsAllocation: allocationKey=553810 jobType=1 mediaKey=4000059 mediaId=000099 driveKey=2000024 driveName=HP.ULTRIUM5-SCSI.000 drivePath=/dev/nst0 stuName=quantum masterServerName=netbackup mediaServerName=netbackup ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 serverStateFlags=1
MdsAllocation: allocationKey=553811 jobType=1 mediaKey=4000092 mediaId=000005 driveKey=2000023 driveName=HP.ULTRIUM5-SCSI.001 drivePath=/dev/nst1 stuName=quantum masterServerName=netbackup mediaServerName=netbackup ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=1 serverStateFlags=1

Re: problem tape drive , control = TLD , Ready = NO

Accepted Solution!

Re: problem tape drive , control = TLD , Ready = NO

There is an allocation for 1 piece of media that has no tape drive associated with it:

MdsAllocation: allocationKey=550642 jobType=16 mediaKey=4000075 mediaId=000115 driveKey=0 driveName= drivePath= stuName= masterServerName=netbackup mediaServerName=netbackup

Looking at the allocationKey number - 550xxx vs 553xxx of the other 3 active drives and media, it seems that it has been 'stuck' there for a while. Although there is no drive assiociated with this media allocation, the resource broker automatically assumes that a drive is needed and will therefore not allocate the 4th drive.

Please release this allocation: 
nbrbutil -releaseMDS 550642

View solution in original post

Re: problem tape drive , control = TLD , Ready = NO

Thanks Marianne

Moved:

Re: problem tape drive , control = TLD , Ready = NO