β05-08-2012 03:30 AM
Environment
OS = windows 2008 Server
Netbackup Server version = 7.1
Media Multiplexing (Under Policy => Schedule Tab => Schedule) = 1
Allow Multiple data strem (Under Attributes tab) = no (unchecked)
Problem
We have six drives and three are down but remaining three are ok. Although only one is running at a time (Means from the three drives sometimes Drive1 runs and sometimes drive2 and sometimes drive3)
Few results are for reference:
Detail status of Activity Monitor
5/8/2012 2:47:53 PM - awaiting resource netbkup-hcart-robot-tld-0 - No drives are available
Result of tpconfig
C:\Program Files\Veritas\Volmgr\bin>tpconfig.exe -d
Id DriveName Type Residence
SCSI coordinates/Path Status
****************************************************************************
0 IBM.ULT3580-TD5.000 hcart TLD(0) DRIVE=3
{3,0,2,0} DOWN
{4,0,2,0} DOWN
1 IBM.ULT3580-TD5.001 hcart TLD(0) DRIVE=4
{3,0,3,0} DOWN
{4,0,3,0} UP
2 IBM.ULT3580-TD5.002 hcart TLD(0) DRIVE=5
{3,0,4,0} UP
{4,0,4,0} UP
3 IBM.ULT3580-TD5.003 hcart TLD(0) DRIVE=6
{3,0,5,0} DOWN
{4,0,5,0} DOWN
4 IBM.ULT3580-TD5.004 hcart TLD(0) DRIVE=1
{4,0,6,0} DOWN
{3,0,6,0} DOWN
5 IBM.ULT3580-TD5.005 hcart TLD(0) DRIVE=2
{4,0,7,0} UP
{3,0,7,0} UP
Currently defined robotics are:
TLD(0) SCSI coordinates = {3,0,5,1}
EMM Server = netbkup
Solved! Go to Solution.
β05-08-2012 11:12 PM
Hi Zahid,
No problem regarding the solutions, lets just call it a misunderstanding and we can all continue on to help each other. No more needs to be said on the matter :0)
I cannot see how 'stuck' allocations can be connected to stuck tapes, NBU should release the allocations before the tape is ejected, so if the tape is stuck, you only find out after the allocations is released.
However, you could be unlucky and get a tape drive that is stuck, and an allocation is stuck at the same time. This would look like they are connected, but I think it would just be unluckly that they happen at the same time, .
Martin
β05-08-2012 11:36 PM
Thanks mph
Actually I have to forward some words on this that why that happened.
β05-09-2012 12:38 AM
No idea, I've seen this about x3 times in ths past 4 years, where -resetall fixes the issue.
As far as I know, for the customers that we have used this fix, the problem has not returned and so they have been happy with the solution.
I think this is one of those issues that you can look all day for the cause and you will not find anything.
My colleague had one of these, and he did, looked for about 2 days, at every log available - no issue found at all, everything looked good. He tried -resetall as a last resort, and it fixed the issue.
If this is a single occurance, and the problem has not returned I wouldn't worry about it. If it happens again , log a call.
BUT ...
As Marianne pointed out nbrbutil and vmoprcmd did not match, perhaps some config change happened ?
Martin