08-25-2012 08:55 PM
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?
08-26-2012 12:38 AM
Run a robot inventory update
Has the tapes been removed from robot without running a inventory ?
Br Nicolai
08-26-2012 12:41 AM
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.
08-26-2012 01:14 AM
onsite team which are monitoring the tapes physically,have asked us to check this.
08-26-2012 01:16 AM
I am not able to understand what this means?Outstanding /pending.
08-26-2012 01:31 AM
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.
08-26-2012 01:41 AM
OK.
Media is in TLD 0
08-26-2012 01:44 AM
sorry its 47
08-26-2012 01:53 AM
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
08-26-2012 01:54 AM
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
08-26-2012 02:00 AM
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.
08-26-2012 05:08 AM
I also suggested that you try to move the tape in robtest, you haven't done this.
As Marianne suggested, make sure the density of the tapes is set the same as the density of the drives.
We see above that the desity of the tape is hcart, are the density of the drives also hcart ?
You can check this in the output of tpconfig -d
Martin
08-26-2012 05:44 AM
density is also hcart of drive.
08-26-2012 05:48 AM
08-26-2012 06:04 AM
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?
Sometimes I find that hiding under the desk is good in such situations. For example, If a NBAC case is floating around, I can often be found underneath my desk.
:o)
M
08-26-2012 06:05 AM
Please also try and load the tape into the drive using robtest like I explained above.
08-26-2012 06:12 AM
I am able to load the tape into and off the drive
08-26-2012 10:05 AM
We need to see what media server sees.
Please post output of 'tpconfig -l' on media server reporting pending request.
Also output of 'vmoprcmd -d' on same media server.
08-26-2012 10:07 PM
Please post output of 'tpconfig -l' on media server reporting pending request.
Also output of 'vmoprcmd -d' on same media server.
How to check what is the media server which is reporting this request?
08-26-2012 10:29 PM
It would've been listed in Device Monitor as well as the job in Activity Monitor that was waiting for tape mount.
You need to check this WHEN the problem occurs.
Next day won't help. Whatever job was looking for the tape would've failed by now.