Veritas-bu

[Veritas-bu] Error 174

2002-08-15 11:58:03
Subject: [Veritas-bu] Error 174
From: Mark.Donaldson AT experianems DOT com (Donaldson, Mark)
Date: Thu, 15 Aug 2002 09:58:03 -0600
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_01C24474.89DAD3F0
Content-Type: text/plain;
        charset="iso-8859-1"

Perhaps a fixed block versus a flexible block size problem?  I was having
bizarre problems when I was not running the correct st.conf file in my
Solaris master and by default was writing fixed blocks instead of variable
blocks.  

If you've upgraded Solaris, the st.conf file may have been overwritten.
That's what happened to me.

-Mark


-----Original Message-----
From: Darryl Eason [mailto:Darryl.Eason AT mgxgroup DOT com]
Sent: Thursday, August 15, 2002 1:41 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Error 174


Hi World
Scenario: Solaris Master/Media Server and backing up Solaris and Win 2000
clients. 
The customer's daily backups run successfully but the weekly and monthly
backups but fail with error 174 (media manager - system error occurred) on
Win 2000 clients. The error message just before the error 174 is: ' critical
- attempted to write 0 gigabytes, 537321716 bytes, it is not a multiple of
512.'
The Unix client backups run fine.

Thanking you in advance
Regards 
Darryl 
Darryl Eason

------_=_NextPart_001_01C24474.89DAD3F0
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] Error 174</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Perhaps a fixed block versus a flexible block size =
problem?&nbsp; I was having bizarre problems when I was not running the =
correct st.conf file in my Solaris master and by default was writing =
fixed blocks instead of variable blocks.&nbsp; </FONT></P>

<P><FONT SIZE=3D2>If you've upgraded Solaris, the st.conf file may have =
been overwritten.&nbsp; That's what happened to me.</FONT>
</P>

<P><FONT SIZE=3D2>-Mark</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Darryl Eason [<A =
HREF=3D"mailto:Darryl.Eason AT mgxgroup DOT com">mailto:[email protected]=
om</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, August 15, 2002 1:41 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Error 174</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi World</FONT>
<BR><FONT SIZE=3D2>Scenario: Solaris Master/Media Server and backing up =
Solaris and Win 2000 clients. </FONT>
<BR><FONT SIZE=3D2>The customer's daily backups run successfully but =
the weekly and monthly backups but fail with error 174 (media manager - =
system error occurred) on Win 2000 clients. The error message just =
before the error 174 is: ' critical - attempted to write 0 gigabytes, =
537321716 bytes, it is not a multiple of 512.'</FONT></P>

<P><FONT SIZE=3D2>The Unix client backups run fine.</FONT>
</P>

<P><FONT SIZE=3D2>Thanking you in advance</FONT>
<BR><FONT SIZE=3D2>Regards </FONT>
<BR><FONT SIZE=3D2>Darryl </FONT>
<BR><FONT SIZE=3D2>Darryl Eason</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C24474.89DAD3F0--

<Prev in Thread] Current Thread [Next in Thread>