outstanding tape mount request for tape
outstanding/pending tape mount request for tape TP0316.tape is currently in TLD0 and listed as a scratch tape.
What to do in such cases?
Forum Discussion
Run a robot inventory update
Has the tapes been removed from robot without running a inventory ?
Br Nicolai
How sure are you that tape TP0316 is indeed in TLD0?
Does NBU and robot contents agree?
To double-check, check NBU config:
nbemmcmd -listmedia -mediaid TP0316
In the output you will see robot number and slot number.
Next, use robtest, select robot and check slot number that you saw in above output.
Quit robtest.
If all is fine, double-check media server config that is asking for tape mount. Check for all of the following:
Device config - check output of 'tpconfig -l'.
Verify robot number and density of tape drive(s).
Compare with tape density in nbemmcmd output.If you post output of all of the above, we should be able to assist.
onsite team which are monitoring the tapes physically,have asked us to check this.
I am not able to understand what this means?Outstanding /pending.
It means that some NBU action (backup, restore, duplication, import etc) needs to use a particular tape, but cannot find the tape in the robot or inside a standalone drive.
Instead of failing the job, NBU gives you the change to find the tape and put it where it needs to be (e.g. in robot if it is not there or in standalone drive, whichever is applicable).
Once the tape is where it must be, you can right-click on the request and resubmit.Meaning of pending request is also documented in NBU Admin Guide I.
OK.
Media is in TLD 0
NBEMMCMD, Version:7.1====================================================================Media GUID: 2ae237c0-a1b2-11e1-8000-bfe5c0b62211Media ID: TP0316Partner: -Media Type: HCARTVolume Group: 000_00000_TLDApplication: NetbackupMedia Flags: 1Description: NBU Default RuleBarcode: TP0316L4Partner Barcode: --------Last Write Host: NONECreated: 05/19/2012 16:57Time Assigned: -First Mount: 05/20/2012 19:28Last Mount: 08/22/2012 19:34Volume Expiration: -Data Expiration: -Last Written: -Last Read: -Robot Type: TLDRobot Control Host: lxmasterRobot Number: 0Slot: 47Side/Face: -Cleanings Remaining: -Number of Mounts: 7Maximum Mounts Allowed: 0Media Status: ACTIVEKilobytes: 0Images: 0Valid Images: 0Retention Period: -Number of Restores: 0Optical Header Size Bytes: 0Optical Sector Size Bytes: 0Optical Partition Size Bytes: 0Last Header Offset: 0Adamm Guid: 00000000-0000-0000-0000-000000000000Rsm Guid: 00000000-0000-0000-0000-000000000000Origin Host: NONEMaster Host: lxmasterServer Group: -Upgrade Conflicts Flag:Pool Number: 4Volume Pool: ScratchPrevious Pool Name: offsite-all-stdVault Flags: -Vault Container: -Vault Name: -Vault Slot: -Session ID: -Date Vaulted: -Return Date: -====================================================================Command completed successfully.for robtest i have to run which command?media is in slot 67 as by above commandsorry its 47
robtest
m s 47 dx
Where x is the drive number
If you so
s d
This will display the drives and you can pick an empty on, numberd 1,2,3 etc from the top.
If the tape loads successfully, then you will need to unload it
m dx s47
If the tape does not load, you could have an issue with the library (it is possible llibrary faults, incorrect library config prevent certain slots being used) .
Martin
slot 47 (addr 4142) contains Cartridge = yes
Source address = 4142
Barcode = TP0316L4
Above i got from robtest.
slot received from Robtest and nbemmcmd -listmedia commmand are matching for this media id
Please check the rest of my post above: (run command on media server asking for tape mount)
If all is fine, double-check media server config that is asking for tape mount. Check for all of the following:
Device config - check output of 'tpconfig -l'.
Verify robot number and density of tape drive(s).
Compare with tape density in nbemmcmd output.
