------=_Part_47517_22085440.1133510020997
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Doing the "mt status" test is a good suggestion, but the fact that the tape=
s
can be sucessfully dismounted using robtest indicates that the device files
are pointing to the correct drives. robtest issues mount commands to the
robot, but dismount commands are sent to the drives themselves.
With these backups that get stuck at "mounting tape", does the robot
actually physically mount the tape in the drive?
What is the status of the drives in Device Monitor (or vmoprcmd)?
Is the Storage Unit pointing to the correct robot?
Any error messages on the library console (if it has one)?
Or any errrors in /var/adm/messages on your master/media ?
I personally wouldn't get too hung up on the " db_lock_media:unable to lock
media at offset" message. The message has appeared continuously on most or
all systems I've worked on. Although I don't know what it means, it doesn't
seem to indicate a problem.
Cheers,
Dean
On 12/2/05, Sean Clarke <sean_clarke AT softhome DOT net> wrote:
>
> Have you tried putting the tape into each drive in turn using robtest
> and then try to see the tape by pointing an "mt status" command at the
> relevant device file as obtained from tpconfig?
>
> This will tell you if you have cross linked drives or not ie. You could
> have the situation where NBU sticks a tape in robot drive 1, thinks it
> is trying to talk to the device file for that drive when in fact that
> particular device file is for robot drive 2 where there is no tape.
> It'll just sit there until it times out.
>
> Had this situation last week when an engineer from a storage company
> that will remain nameless swapped over a pair of SCSI cables to test a
> drive and forgot to swap them back :-(
>
> HTH
>
> Sean
>
> > -----Original Message-----
> > From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> > [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
> > Tschida, Tom (C)(STP)
> > Sent: 01 December 2005 19:07
> > To: veritas-bu AT mailman.eng.auburn DOT edu
> > Subject: [Veritas-bu] Backups stuck at tape mount
> >
> >
> > All,
> >
> > I've recently upgraded from 4.5MP8 to 5.1MP2. Master server
> > is a V880 running Solaris 8. Immediately following the
> > upgrade, all backups hang at "mounting tape###".
> >
> > I've looked through the bptm logs and found the following message:
> >
> > db_lock_media:unable to lock media at offset (tape###)
> >
> > In looking through the mail list and the Veritas website,
> > I've found references that tell me some other process is
> > trying to use that tape.
> >
> > What I've done so far:
> >
> > * Rebuild the sg drivers
> > * Rebuild the globDB (several time)
> > * reboot -r the master
> > * use robtest to manually mount and unmount tapes - works fine
> > * remove the /usr/openv/netbackup/db/jobs directory
> >
> > Has anyone else come across this? If so, what else can I try
> > besides backing out and trying the upgrade again?
> >
> > Tom Tschida
> > Guidant Corp
> >
> > _______________________________________________
> > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo> /veritas-bu
> >
>
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
------=_Part_47517_22085440.1133510020997
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Doing the "mt status" test is a good suggestion, but the fact tha=
t the
tapes can be sucessfully dismounted using robtest indicates that the
device files are pointing to the correct drives. robtest issues mount
commands to the robot, but dismount commands are sent to the drives
themselves.<br>
<br>
With these backups that get stuck at "mounting tape", does the ro=
bot actually physically mount the tape in the drive?<br>
<br>
What is the status of the drives in Device Monitor (or vmoprcmd)? <br>
Is the Storage Unit pointing to the correct robot?<br>
Any error messages on the library console (if it has one)?<br>
Or any errrors in /var/adm/messages on your master/media ?<br>
<br>
I personally wouldn't get too hung up on the " db_lock_media:unable to
lock media at offset" message. The message has appeared continuously o=
n
most or all systems I've worked on. Although I don't know what it
means, it doesn't seem to indicate a problem.<br>
<br>
Cheers,<br>
Dean<br>
<br><div><span class=3D"gmail_quote">On 12/2/05, <b class=3D"gmail_senderna=
me">Sean Clarke</b> <<a href=3D"mailto:sean_clarke AT softhome DOT
net">sean_cl=
arke AT softhome DOT net</a>> wrote:</span><blockquote class=3D"gmail_quote"
st=
yle=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex=
; padding-left: 1ex;">
Have you tried putting the tape into each drive in turn using robtest<br>an=
d then try to see the tape by pointing an "mt status" command at =
the<br>relevant device file as obtained from tpconfig?<br><br>This will tel=
l you if you have cross linked drives or not ie. You could
<br>have the situation where NBU sticks a tape in robot drive 1, thinks it<=
br>is trying to talk to the device file for that drive when in fact that<br=
>particular device file is for robot drive 2 where there is no tape.<br>
It'll just sit there until it times out.<br><br>Had this situation last wee=
k when an engineer from a storage company<br>that will remain nameless swap=
ped over a pair of SCSI cables to test a<br>drive and forgot to =
swap them back :-(
<br><br>HTH<br><br>Sean<br><br>> -----Original Message-----<br>> From=
: <a href=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT
edu">veritas-bu-adm=
in AT mailman.eng.auburn DOT edu</a><br>> [mailto:<a
href=3D"mailto:veritas-bu-=
admin AT mailman.eng.auburn DOT edu">
veritas-bu-admin AT mailman.eng.auburn DOT edu</a>] On Behalf Of<br>>
Tschida, =
Tom (C)(STP)<br>> Sent: 01 December 2005 19:07<br>> To: <a href=3D"ma=
ilto:veritas-bu AT mailman.eng.auburn DOT edu">veritas-bu AT mailman.eng.auburn
DOT edu
</a><br>> Subject: [Veritas-bu] Backups stuck at tape mount<br>><br>&=
gt;<br>> All,<br>><br>> I've recently upgraded from 4.5MP8 to 5.1M=
P2. Master server<br>> is a V880 running Solaris 8. &nbs=
p;Immediately following the
<br>> upgrade, all backups hang at "mounting tape###".<br>>=
<br>> I've looked through the bptm logs and found the following message:=
<br>><br>> db_lock_media:unable to lock media at offset (t=
ape###)
<br>><br>> In looking through the mail list and the Veritas website,<=
br>> I've found references that tell me some other process is<br>> tr=
ying to use that tape.<br>><br>> What I've done so far:<br>><br>
> * Rebuild the sg drivers<br>> * Rebuild the g=
lobDB (several time)<br>> * reboot -r the master<br>> *&nb=
sp; use robtest to manually mount and unmount tapes - works fine<br>&g=
t; * remove the /usr/openv/netbackup/db/jobs directory
<br>><br>> Has anyone else come across this? If so, what e=
lse can I try<br>> besides backing out and trying the upgrade again?<br>=
><br>> Tom Tschida<br>> Guidant Corp<br>><br>> _____________=
__________________________________
<br>> Veritas-bu maillist - <a href=3D"mailto:Veri=
tas-bu AT mailman.eng.auburn DOT edu">Veritas-bu AT mailman.eng.auburn DOT
edu</a><br>>=
; <a href=3D"http://mailman.eng.auburn.edu/mailman/listinfo";>http://mailman=
.eng.auburn.edu/mailman/listinfo
</a>> /veritas-bu<br>><br><br><br>___________________________________=
____________<br>Veritas-bu maillist - <a href=3D"mail=
to:Veritas-bu AT mailman.eng.auburn DOT edu">Veritas-bu AT mailman.eng.auburn
DOT edu</a>=
<br><a href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</a><br></blockquo=
te></div><br>
------=_Part_47517_22085440.1133510020997--
|
