|
[Veritas-bu] Determining bad tape
2001-03-06 11:55:40
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C0A65E.49BF40C2
Content-Type: text/plain;
charset="iso-8859-1"
Jason,
/usr/openv/netbackup/db/media/errors file contains the list of tapes
netbackup has had problems with (readable only by root by default). This
includes a timestamp of the problem and which drive the tape was in, also.
Paul
-----Original Message-----
From: Jason Ahrens [mailto:ahrensj AT psi DOT ca]
Sent: Tuesday, March 06, 2001 10:50 AM
To: veritas-bu AT eng.auburn DOT edu
Subject: [Veritas-bu] Determining bad tape
Hello
Over the weekend, I had a number of jobs 'fail' with status 84 "Media write
error". I beleive this indicates a bad tape. The jukebox we use is huge,
containing hundreds of tapes. I cannot find any jobs in the activity monitor
that failed with status 84, so I cannot find out there which tape was
mounted to determine which was the 'bad' one. The syslog files confirm that
the tape was bad, showing numerous SCSI write errors.
How can I find out which tape is bad? Media and MAster servers are both
Solaris 2.6.
Thanks
Jason
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C0A65E.49BF40C2
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: [Veritas-bu] Determining bad tape</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Jason,</FONT>
<BR> <FONT =
SIZE=3D2>/usr/openv/netbackup/db/media/errors file contains the list of =
tapes netbackup has had problems with (readable only by root by =
default). This includes a timestamp of the problem and which =
drive the tape was in, also.</FONT></P>
<P><FONT SIZE=3D2>Paul</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Jason Ahrens [<A =
HREF=3D"mailto:ahrensj AT psi DOT ca">mailto:ahrensj AT psi DOT ca</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, March 06, 2001 10:50 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Determining bad tape</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hello</FONT>
</P>
<P><FONT SIZE=3D2>Over the weekend, I had a number of jobs 'fail' with =
status 84 "Media write</FONT>
<BR><FONT SIZE=3D2>error". I beleive this indicates a bad tape. =
The jukebox we use is huge,</FONT>
<BR><FONT SIZE=3D2>containing hundreds of tapes. I cannot find any jobs =
in the activity monitor</FONT>
<BR><FONT SIZE=3D2>that failed with status 84, so I cannot find out =
there which tape was</FONT>
<BR><FONT SIZE=3D2>mounted to determine which was the 'bad' one. The =
syslog files confirm that</FONT>
<BR><FONT SIZE=3D2>the tape was bad, showing numerous SCSI write =
errors.</FONT>
</P>
<P><FONT SIZE=3D2>How can I find out which tape is bad? Media and =
MAster servers are both</FONT>
<BR><FONT SIZE=3D2>Solaris 2.6.</FONT>
</P>
<P><FONT SIZE=3D2>Thanks</FONT>
</P>
<P><FONT SIZE=3D2>Jason</FONT>
</P>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C0A65E.49BF40C2--
|
|
|
