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_01C1F5E2.39BE9590
Content-Type: text/plain;
charset="iso-8859-1"
Hi Troy,
I just got three hours of sleep after fixing this problem all night.
Somewhere along the way, several months ago, I patched Solaris and the patch
overwrote the /kernel/drv/st.conf file with the default file. All the
netbackup stuff has been very unhappy about losing the specialized entries
in here. (For your fiber drives, I'm not sure if st.conf still applies but
there may be an analogous file).
Seems like all you'd have to do is fix the file to where it came from and
reboot and you'd be done, right? Wrong.
One fallout of this is I've been writing tapes with fixed block sizes - not
variable ones. Once the st.conf file is fixed, the tapes written with fixed
blocks under the default st.conf file are no longer compatible with the new
st.conf file.
The work-around to this is suspend all non-full assigned tapes. This will
force NB to grab new tapes for backup rather than unsuccessfully trying to
seek to position on the partially-written fixed-block tapes. When the
images on the tapes are expired, NB will turn these suspended tapes back for
reuse.
If you have to read a fixed-block tape you can touch:
/usr/openv/netbackup/db/config/FIXED_LENGTH_BLOCKS
...before the restore then remove it right after.
HTH - Mark
-----Original Message-----
From: Deterding, Troy [mailto:TDeterding AT aegonusa DOT com]
Sent: Monday, May 06, 2002 2:25 PM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] 84 85 86 errors
Good day all,
We've been experiencing a rash of media read, write and position errors
and I wanted to see if anyone else has been through this with a satisfactory
resolution.
We have a sun master server running solaris 8, one aix media server and 6
windows 2k media servers. Our libraries are 2 STK L700's with 7 FC 9840
drives in one and 9 FC 9840 drives in the other. These libraries reside at 2
separate locations. We only see the 84, 85 and 86 errors at one location. I
don't think it's bad media seeing as we share tape at both sites.
Thanks in advance,
Troy
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C1F5E2.39BE9590
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.2653.12">
<TITLE>RE: [Veritas-bu] 84 85 86 errors</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Hi Troy,</FONT>
</P>
<P><FONT SIZE=3D2>I just got three hours of sleep after fixing this =
problem all night. Somewhere along the way, several months ago, I =
patched Solaris and the patch overwrote the /kernel/drv/st.conf file =
with the default file. All the netbackup stuff has been very =
unhappy about losing the specialized entries in here. (For your =
fiber drives, I'm not sure if st.conf still applies but there may be an =
analogous file).</FONT></P>
<P><FONT SIZE=3D2>Seems like all you'd have to do is fix the file to =
where it came from and reboot and you'd be done, right? =
Wrong.</FONT>
</P>
<P><FONT SIZE=3D2>One fallout of this is I've been writing tapes with =
fixed block sizes - not variable ones. Once the st.conf file is =
fixed, the tapes written with fixed blocks under the default st.conf =
file are no longer compatible with the new st.conf file. =
</FONT></P>
<P><FONT SIZE=3D2>The work-around to this is suspend all non-full =
assigned tapes. This will force NB to grab new tapes for backup =
rather than unsuccessfully trying to seek to position on the =
partially-written fixed-block tapes. When the images on the tapes =
are expired, NB will turn these suspended tapes back for =
reuse.</FONT></P>
<P><FONT SIZE=3D2>If you have to read a fixed-block tape you can =
touch:</FONT>
</P>
<P><FONT =
SIZE=3D2>/usr/openv/netbackup/db/config/FIXED_LENGTH_BLOCKS</FONT>
</P>
<P><FONT SIZE=3D2>...before the restore then remove it right =
after.</FONT>
</P>
<P><FONT SIZE=3D2>HTH - Mark</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Deterding, Troy [<A =
HREF=3D"mailto:TDeterding AT aegonusa DOT com">mailto:TDeterding AT aegonusa
DOT com</=
A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, May 06, 2002 2:25 PM</FONT>
<BR><FONT SIZE=3D2>To: 'veritas-bu AT mailman.eng.auburn DOT edu'</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] 84 85 86 errors</FONT>
</P>
<P><FONT SIZE=3D2>Good day all,</FONT>
<BR><FONT SIZE=3D2> We've been experiencing a rash of media read, =
write and position errors</FONT>
<BR><FONT SIZE=3D2>and I wanted to see if anyone else has been through =
this with a satisfactory</FONT>
<BR><FONT SIZE=3D2>resolution.</FONT>
<BR><FONT SIZE=3D2>We have a sun master server running solaris 8, one =
aix media server and 6</FONT>
<BR><FONT SIZE=3D2>windows 2k media servers. Our libraries are 2 STK =
L700's with 7 FC 9840</FONT>
<BR><FONT SIZE=3D2>drives in one and 9 FC 9840 drives in the other. =
These libraries reside at 2</FONT>
<BR><FONT SIZE=3D2>separate locations. We only see the 84, 85 and 86 =
errors at one location. I</FONT>
<BR><FONT SIZE=3D2>don't think it's bad media seeing as we share tape =
at both sites. </FONT>
<BR><FONT SIZE=3D2>Thanks in advance,</FONT>
<BR><FONT SIZE=3D2>Troy </FONT>
<BR><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_01C1F5E2.39BE9590--
|
