This is a multi-part message in MIME format.
------_=_NextPart_001_01C4F766.63497849
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi everyone,
=20
I'm trying to track down the cause of some 84 and 14 failures we've been
having lately. I know the problem is not tape, drive, job, time-of-day
or robot specific. However the problem seems to be happening on the
weekends when we run our full backups. We're on NBU 4.5GA running on
Solaris 8 master and media servers with an STK L700 library that has
Seagate Viper 200s in it.
=20
One of the entries I found in a bptm log bothered me a little bit. Is
this normal, or should I perform an inventory on the robot? The first
line says the media is not in the correct storage unit or volume pool.
However, it looks like the tape ends up being used anyway, and it also
appears that the tape was able to store data. The job associated with
these log entries bombed out roughly 4 hours later with an 84 error.
=20
Also, during the whole backup attempt, I'd see the db_lock_media error
messages about every 30 seconds. I've read elsewhere that this isn't
really a problem.
=20
20:19:23.649 [13116] <2> select_media: skipping media id 000309, it is
not in correct storage unit or volume pool
22:09:35.428 [13711] <2> check_available_drives: checking drives, about
to request media id 000309
22:09:35.589 [13711] <2> select_media: selected media id 000309 for
backup[0], crmmnt52(rl =3D 4) <----------
22:09:35.592 [13711] <2> mount_open_media: Waiting for mount of media id
000309 (copy 1) on server crmmdb17.
22:09:58.590 [13725] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:10:24.370 [13739] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:10:27.510 [13746] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:10:31.100 [13754] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:10:50.500 [13761] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:10:52.710 [13768] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:11:00.730 [13775] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:11:05.320 [13783] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:11:24.389 [13711] <2> io_open: file
/usr/openv/netbackup/db/media/tpreq/000309 successfully opened
22:11:24.389 [13711] <2> write_backup: media id 000309 mounted on drive
index 0, drivepath /dev/rmt/8cbn, drivename LTO_crmmdb17_0, copy 1
22:11:24.588 [13711] <2> io_position_for_write: position media id
000309, copy 1, current number images =3D 23
22:11:25.220 [13790] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:11:36.810 [13799] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:11:59.039 [13711] <2> io_position_for_write: empty header found on
000309, OK, copy 1
22:11:59.039 [13711] <2> io_close: closing
/usr/openv/netbackup/db/media/tpreq/000309, from bptm.c.17346
22:11:59.046 [13711] <2> io_open: file
/usr/openv/netbackup/db/media/tpreq/000309 successfully opened
22:12:07.410 [13807] <2> db_lock_media: unable to lock media at offset
63 (000309)
22:12:22.924 [13711] <4> write_backup: begin writing backup id
crmmnt52_1105157367, copy 1, fragment 1, to media id 000309 on drive
index 0
=20
If our problem is really network-related, are there any unusual causes I
should check first? The clients we're backing up are a mixture of
Solaris 7/8 and Windows XP/2000 Server/2003 Server. I think I've ruled
out the drives altogether since I took the time to run TapeRx on all of
the drives in this system, and have written and read up to 4GB without
an error. I've had backup jobs fail with error 84 that have transferred
less data than that when they failed.
=20
Thanks for any help!
=20
Marshall Skare
ATIS - Unix Engineering
(612) 277-4434
=20
This message is for the designated recipient only and may contain =
privileged, proprietary, or otherwise private information. If you have =
received it in error, please notify the sender immediately and delete =
the original. Any other use of the email by you is prohibited.
------_=_NextPart_001_01C4F766.63497849
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Book Antiqua";
panose-1:2 4 6 2 5 3 5 3 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Book Antiqua";}
h1
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:14.0pt;
font-family:"Book Antiqua";}
h2
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:12.0pt;
font-family:"Book Antiqua";
font-style:italic;}
h3
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:12.0pt;
font-family:"Book Antiqua";
font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Book Antiqua";}
p.MsoFooter, li.MsoFooter, div.MsoFooter
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Book Antiqua";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.ABLOCKPARA, li.ABLOCKPARA, div.ABLOCKPARA
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Book Antiqua";}
p.ABULLET, li.ABULLET, div.ABULLET
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:16.55pt;
margin-bottom:.0001pt;
text-indent:-16.55pt;
font-size:11.0pt;
font-family:"Book Antiqua";}
p.AINDENTEDBULLET, li.AINDENTEDBULLET, div.AINDENTEDBULLET
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:33.1pt;
margin-bottom:.0001pt;
text-indent:-16.55pt;
font-size:11.0pt;
font-family:"Book Antiqua";}
p.AINDENTEDPARA, li.AINDENTEDPARA, div.AINDENTEDPARA
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:16.55pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Book Antiqua";}
span.EmailStyle23
{font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in .75in 1.0in .75in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi everyone,</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I’m trying to track down the cause of some 84 =
and 14
failures we’ve been having lately. I know the problem is not =
tape,
drive, job, time-of-day or robot specific. However the problem =
seems to
be happening on the weekends when we run our full backups. =
We’re on
NBU 4.5GA running on Solaris 8 master and media servers with an STK L700
library that has Seagate Viper 200s in it.</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>One of the entries I found in a </span></font><font =
size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>bptm</span></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> log
bothered me a little bit. Is this normal, or should I perform an
inventory on the robot? The first line says the media is not in =
the correct
storage unit or volume pool. However, it looks like the tape ends =
up
being used anyway, and it also appears that the tape was able to store =
data. The
job associated with these log entries bombed out roughly 4 hours later =
with an
84 error.</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Also, during the whole backup attempt, I’d see =
the </span></font><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>db_lock_media</span></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> error
messages about every 30 seconds. I’ve read elsewhere that =
this isn’t
really a problem.</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>20:19:23.649 [13116] <2> select_media:
skipping media id 000309, it is not in correct storage unit or volume =
pool</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:09:35.428 [13711] <2> =
check_available_drives:
checking drives, about to request media id 000309</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:09:35.589 [13711] <2> select_media: =
selected
media id 000309 for backup[0], crmmnt52(rl =3D 4) =
<----------</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:09:35.592 [13711] <2> =
mount_open_media:
Waiting for mount of media id 000309 (copy 1) on server =
crmmdb17.</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:09:58.590 [13725] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:10:24.370 [13739] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:10:27.510 [13746] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:10:31.100 [13754] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:10:50.500 [13761] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:10:52.710 [13768] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:00.730 [13775] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:05.320 [13783] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:24.389 [13711] <2> io_open: file
/usr/openv/netbackup/db/media/tpreq/000309 successfully =
opened</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:24.389 [13711] <2> write_backup: =
media
id 000309 mounted on drive index 0, drivepath /dev/rmt/8cbn, drivename
LTO_crmmdb17_0, copy 1</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:24.588 [13711] <2> =
io_position_for_write:
position media id 000309, copy 1, current number images =3D =
23</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:25.220 [13790] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:36.810 [13799] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:59.039 [13711] <2> =
io_position_for_write:
empty header found on 000309, OK, copy 1</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:59.039 [13711] <2> io_close: =
closing
/usr/openv/netbackup/db/media/tpreq/000309, from =
bptm.c.17346</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:11:59.046 [13711] <2> io_open: file
/usr/openv/netbackup/db/media/tpreq/000309 successfully =
opened</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:12:07.410 [13807] <2> db_lock_media: =
unable
to lock media at offset 63 (000309)</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>22:12:22.924 [13711] <4> write_backup: =
begin
writing backup id crmmnt52_1105157367, copy 1, fragment 1, to media id =
000309
on drive index 0</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>If our problem is really network-related, are there =
any unusual
causes I should check first? The clients we’re backing up =
are a
mixture of Solaris 7/8 and Windows XP/2000 Server/2003 Server. I =
think I’ve
ruled out the drives altogether since I took the time to run TapeRx on =
all of
the drives in this system, and have written and read up to 4GB without =
an
error. I’ve had backup jobs fail with error 84 that have
transferred less data than that when they failed.</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks for any help!</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Marshall Skare</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>ATIS - Unix Engineering</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>(612) 277-4434</span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3D"Book =
Antiqua"> </font></p>
</div>
<div id=3D"##disclaimer##"><p></p><p style=3D"FONT-SIZE: x-small; =
FONT-FAMILY: Arial, Sans-Serif">This message is for the =
designated recipient only and may contain privileged, proprietary, or =
otherwise private information. If you have received it in error, please =
notify the sender immediately and delete the original. Any other use of =
the email by you is prohibited.</p></div></body>
</html>
------_=_NextPart_001_01C4F766.63497849--
|
