backup issue-cannot dismount drive

[Krissh]

Hi

In our Netbackup server,backup is failing for last few days with drives going down.In event log following errors are displayed "TLD cannot dismount drive, Slot 5 already full" and "drive is beinig downed,status: unable to SCSI unload drive"

We have checked if there are any  issue with drives,but everything seems to be fine.

could you please help me on this?.

Thanks!!

[Android]

I would check to make sure:

Does NBU think there is a tape in the drive?  If there is and NBU thinks there is not then use the library FPM to unload it and put it back into a slot and re-invnetory the library both from the library and from within NBU.  (NBU does not do a physical inventory when you run inventory robot, it only updates from what the libraries memory has as far as the last physical inventory that was run on the library)

Also if there is a tape in the drive, your library may have ended up in a state where the drive it is currently trying to unload should go into slot 5 and somehow slot 5 now has another tape in that space. Again inventory your robot from the FPM and then run a inventory robot from within NBU.

If NBU thinks there is a tape in the drive and there is not, I would run a physical inventory of the library from the FPM (Front Panel Module) and then run an inventory robot from within NBU. 

[J_H_Is_gone]

you said
"TLD cannot dismount drive, Slot 5 already full" and "drive is being downed,status: unable to SCSI unload drive"


this makes me think that at some point and there after you take tapes out of a tape drive by and and put them in some slot in the library.
If you are doing this - you MUST then do an inventory in NetBackup so the NetBackup database and the library database match as to what tape is in what slot.

So try to do an inventory and I think you will see it say it wants to move a tape from slot# to slot# to make it correct.  Once doing this see then if you have the error show up again.

[Marianne]

I have seen this when operators manually open the robot door to load tapes while backups are running. When a tape is unloaded after backup, it needs to return it to the slot it came from. If the operator has loaded new tapes into any open slot they could find, NBU can obviously not return the tape to it's slot. The tape will be in unloaded state, still in the drive.
Inventory alone won't help.
Use robtest to see where there's empty slots and move tape from drive to the empty slot.
Now inventory to update NBU config.

[Omar_Villa]

If you can get in to the library GUI and do a power cycle can help, this if you have a stuck tape that it cannot go back to the original slot because an other tape was place there, so a manual intervention is required or move the tape from the library GUI or ACSLS to a diferent slot and later inventory the library.

[Andy_Welburn · Accepted solution]

our Oppos aren't concentrating - it's not only annoying, it can cause backup failures due to lack of resources & can be particularly severe if they just happen to have re-populated ALL the empty slots at a time when ALL the drives were busy!

If there's no empty slots to move the tape(s) to from the drive(s) then you can also utilise robtest to move them to the CAP (or even go open the library & remove them manually!).

But, always re-inventory the library after manually moving tapes.

[Krissh]

Hi

We have checked with tape library and our onsite team is saying that there are no medias in drive and no errors are displaying in magzine.
even power cycled by removing all tapes from the library and then reinserting it. From server end we have run inventory.

but still issue persist.

please help!!!

[Android]

Test the functionality of your robot with robtest to be sure that there are no mechanical problems with your library.

[Android]

Were you able to resolve this issue?  If so mark  the solution and close the thread. If not let us know where you are currently.

[Krissh]

Sorry for late response..!

We have resolved the issue..below is the step we followed.

This issue was related to Volume manager database,where the database was not updating properly,so recreated the database and configure the storage devices with proper drive names and was able to run backup successfully..!!

once again thanks for all for response..!!!

regards
Krissh