This is a multi-part message in MIME format.
------_=_NextPart_001_01C580F0.33691DC5
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Sounds like it may be the tape device drivers? Are the drivers the same
for all of the tape drives on Both servers?
The current/correct tape drives might help? Veritas offers a good set
of drivers on the Master/media server installation CD
Under additional products/tape device drivers. We used to get a lot of
84's using Microsoft driver even with good tapes,
I installed the Veritas tape device drivers and that solved the issue.
=20
Eric
=20
________________________________
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Steven
Jenner
Sent: Monday, July 04, 2005 7:07 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Status code 84
=20
Hi I have started to experience status 84 errors since I upgraded my two
media servers last week. I initially upgraded my master server from 4.5
MP6 to 5.1 with no issues (all backups completing successfully); I
therefore decided to upgrade my two media servers from 4.5MP6 to 5.1. =20
=20
All backups that use media server 2 (sn251180) are successful however
any backups that attempt to use media server1 (sn251170) fail with
status code 84 (media write error). I am having difficulty explaining
this as both servers should in essence be set up exactly the same and I
can see no obvious differences between the two. I have copied below a
problems report detailing the error messages that are being output (the
example is showing an attempted backup of media server 2 by media server
1).
=20
bash-2.05# cat Export2.txt=20
=20
Problems on sn251161.mgmt.internal
=20
=20
Date/Time Client Severity
Description
Process Status
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
---------------------------------
07/04/2005 13:24:10 sn251180.mgmt.internal Error FREEZING
media id 000240, too many data blocks written, check tape/driver block
size configuration bptm =20
07/04/2005 13:24:10 sn251180.mgmt.internal Error from client
sn251180.mgmt.internal: ERR - Cannot write to STDOUT. Errno =3D 32: =
Broken
pipe bpbrm =20
07/04/2005 13:24:12 sn251180.mgmt.internal Warning DOWN'ing
drive index 0, it has had at least 3 errors in last 12 hour(s)
bptm =20
07/04/2005 13:24:13 sn251180.mgmt.internal Error backup of
client sn251180.mgmt.internal exited with status 84 (media write error)
bpsched =20
07/04/2005 13:30:51 sn251180.mgmt.internal Error FREEZING
media id 000225, too many data blocks written, check tape/driver block
size configuration bptm =20
07/04/2005 13:30:51 sn251180.mgmt.internal Error from client
sn251180.mgmt.internal: ERR - Cannot write to STDOUT. Errno =3D 32: =
Broken
pipe bpbrm =20
07/04/2005 13:30:53 sn251180.mgmt.internal Warning DOWN'ing
drive index 1, it has had at least 3 errors in last 12 hour(s)
bptm =20
07/04/2005 13:30:53 sn251180.mgmt.internal Error suspending
further backup attempts for client sn251180.mgmt.internal, policy
NB_Servers_3, schedule NB_Servers_Daily because it has exceeded the
configured number of tries bpsched =20
07/04/2005 13:30:53 sn251180.mgmt.internal Error backup of
client sn251180.mgmt.internal exited with status 84 (media write error)
bpsched =20
=20
Both media servers are running Solaris 9 (at same patch level) and are
connected to IBM LTO2 drives (6 attached to media 1 and 4 attached to
media 2) within a StorageTek L700 tape library. The SIZE_DATA_BUFFERS &
NUMBER_DATA_BUFFERS files are not set up on either server therefore both
should be using the default configuration.
=20
Has anyone else encountered this error following an upgrade?
=20
Any advice would be gratefully appreciated as this has severely limited
my backup system's current capabilities.
=20
Regards,
=20
Steve.
=20
------_=_NextPart_001_01C580F0.33691DC5
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Sounds like it may be the tape =
device
drivers? Are the drivers the same for all of the tape drives on =
Both servers?<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The current/correct tape drives =
might
help? Veritas offers a good set of drivers on the Master/media =
server
installation CD<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Under additional products/tape =
device
drivers. We used to get a lot of 84’s using Microsoft driver =
even with
good tapes,<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I installed the Veritas tape device
drivers and that solved the issue.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Eric<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>
</span></font></div>
<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Steven Jenner<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, July 04, =
2005 7:07
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b>
veritas-bu AT mailman.eng.auburn DOT edu<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Veritas-bu] =
Status code
84</span></font><o:p></o:p></p>
</div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi I have started to experience status 84 errors =
since I
upgraded my two media servers last week. I initially upgraded my master =
server
from 4.5 MP6 to 5.1 with no issues (all backups completing =
successfully); I
therefore decided to upgrade my two media servers from 4.5MP6 to 5.1. =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>All backups that use media server 2 (sn251180) are
successful however any backups that attempt to use media server1 =
(sn251170)
fail with status code 84 (media write error). I am having difficulty =
explaining
this as both servers should in essence be set up exactly the same and I =
can see
no obvious differences between the two. I have copied below a problems =
report
detailing the error messages that are being output (the example is =
showing an
attempted backup of media server 2 by media server 1).<font =
color=3Dred><span
style=3D'color:red'><o:p></o:p></span></font></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>bash-2.05# cat Export2.txt =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>Problems on =
sn251161.mgmt.internal<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>Date/Time &nbs=
p;
Client &=
nbsp;
Severity =
;
&=
nbsp;
Description &n=
bsp; &nb=
sp; &nbs=
p;  =
; =
&=
nbsp; &n=
bsp; &nb=
sp; &nbs=
p;
Process Status<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>-------------------------------------=
-------------------------------------------------------------------------=
-------------------------------------------------------------------------=
------------------------------------------------------------------<o:p></=
o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:24:10
sn251180.mgmt.internal Error
FREEZING media id 000240, too many data blocks written, check =
tape/driver
block size =
configuration =
bptm <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:24:10
sn251180.mgmt.internal Error
from client sn251180.mgmt.internal: ERR - Cannot write to STDOUT. =
Errno =3D
32: Broken =
pipe &nb=
sp;
bpbrm <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:24:12
sn251180.mgmt.internal Warning =
DOWN'ing drive
index 0, it has had at least 3 errors in last 12
hour(s) =
&=
nbsp; &n=
bsp; &nb=
sp;
bptm <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:24:13
sn251180.mgmt.internal Error
backup of client sn251180.mgmt.internal exited with status 84 =
(media write
error) &=
nbsp; &n=
bsp; &nb=
sp;
bpsched <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:30:51
sn251180.mgmt.internal Error
FREEZING media id 000225, too many data blocks written, check =
tape/driver
block size =
configuration
bptm <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:30:51
sn251180.mgmt.internal Error
from client sn251180.mgmt.internal: ERR - Cannot write to STDOUT. =
Errno =3D
32: Broken
pipe &nb=
sp;
bpbrm <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:30:53
sn251180.mgmt.internal Warning =
DOWN'ing
drive index 1, it has had at least 3 errors in last 12
hour(s) =
&=
nbsp; &n=
bsp; &nb=
sp;
bptm <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:30:53
sn251180.mgmt.internal Error
suspending further backup attempts for client =
sn251180.mgmt.internal,
policy NB_Servers_3, schedule NB_Servers_Daily because it has exceeded =
the
configured number of tries bpsched =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'>07/04/2005 13:30:53
sn251180.mgmt.internal Error
backup of client sn251180.mgmt.internal exited with status 84 =
(media
write =
error) &=
nbsp; &n=
bsp; &nb=
sp;
bpsched <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:red'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Both media servers are running Solaris 9 (at same =
patch
level) and are connected to IBM LTO2 drives (6 attached to media 1 and 4
attached to media 2) within a StorageTek L700 tape library. The
SIZE_DATA_BUFFERS & NUMBER_DATA_BUFFERS files are not set up on =
either
server therefore both should be using the default =
configuration.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Has anyone else encountered this error following an =
upgrade?<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Any advice would be gratefully appreciated as this =
has
severely limited my backup system’s current =
capabilities.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Steve.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C580F0.33691DC5--
|