This is a multi-part message in MIME format.
------_=_NextPart_001_01C3DF81.CC86F279
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
>From last nights backups =20
- 2 Win2K servers exhibited the problem. Both use Gb NICs set to =
auto-negotiate.
- 3 WinNT servers exhibited the problem. 1 is set to 100/FDX on NIC and =
NW Switch,
2 are set =
to auto-negotiate and NW Switch (100Mb NICs)
=20
I'll look into reseting the 2 that currently auto-negotiate, but I don't =
think this is the problem
as 3 other backup clients that are configured correctly still exhibit =
this problem.
=20
More Info:
NT Clients are WinNT SP6A
2K Clients are Win2K SP4
=20
I've seen messages saying "Drive at or near capacity" in the event =
logs on several of these
backup clients. Further, I've noticed that the _vxfiVspCacheFilex.tmp =
is eating up most of the
free disk space on these backup clients.
=20
Could VSP be causing this problem?
If so, what can I do about it? (Don't I need VSP to backup open =
files?)
------------------------------------------=20
Tim J. Anderson=20
Tim.Anderson AT palmone DOT com=20
408-503-1287=20
-----Original Message-----
From: Nash, Ebon [mailto:Ebon_Nash AT compuware DOT com]
Sent: Tuesday, January 20, 2004 9:22 AM
To: Tim Anderson
Subject: RE: [Veritas-bu] NBU 5.0 - errors 26, 41, and 42
If you haven't already don't use autonegotiation on the switch ports or =
nics. If on a 100MB network force them to 100FULL.
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu =
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Tim =
Anderson
Sent: Tuesday, January 20, 2004 11:42 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NBU 5.0 - errors 26, 41, and 42
We've recently implemented a backup solution using Veritas NBU 5.0GA on =
a Solaris 8 server.=20
Several of the backup clients (all running NBU 5.0GA) get an error 26 =
(client/server handshaking failed)=20
on the first backup attempt, yet, with no action by myself or others, =
succeed on the second attempt.=20
Sometimes, the clients fail the second attempt and I must manually =
resume the job to get a successful=20
backup.=20
The clients are all WinNT. Three of the WinNT clients have this problem =
regularly. Three other WinNT=20
clients periodically have this problem.=20
Also, I have several Win2K clients (all running NBU 5.0GA) that have a =
similar problem (5 out of 19 clients).=20
These clients get an error 41 and/or 42 (network read/write fail) =
sometime after the backup has begun.=20
Most succeed on the second attempt. Sometimes the second attempt fails =
and I must manually resume=20
the jobs to get a good backup.=20
Veritas support has been looking into this, but as yet it is not =
resolved.=20
Things We've done:=20
- latest patch on network drivers on Solaris Server=20
- set the "client read" and "file browse" timeouts on both the master =
and clients to 900 seconds (up from 300 seconds)
- lots and lots of logging analysis=20
Any suggestions/ideas?=20
------------------------------------------=20
Tim J. Anderson=20
Tim.Anderson AT palmone DOT com=20
408-503-1287=20
The contents of this e-mail are intended for the named addressee only. =
It contains information that may be confidential. Unless you are the =
named addressee or an authorized designee, you may not copy or use it, =
or disclose it to anyone else. If you received it in error please notify =
us immediately and then destroy it.=20
------_=_NextPart_001_01C3DF81.CC86F279
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>NBU 5.0 - errors 26, 41, and 42</TITLE>
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004>From =
last nights=20
backups </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004>- 2 =
Win2K servers=20
exhibited the problem. Both use Gb NICs set to=20
auto-negotiate.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004>- 3 =
WinNT servers=20
exhibited the problem. 1 is set to 100/FDX on NIC and NW=20
Switch,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D980315417-20012004> &nbs=
p;  =
; =
&=
nbsp; &n=
bsp; =20
2 are set to auto-negotiate and NW Switch (100Mb =
NICs)</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D980315417-20012004></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004>I'll =
look into=20
reseting the 2 that currently auto-negotiate, but I don't think this is =
the=20
problem</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004>as 3 =
other backup=20
clients that are configured correctly still exhibit this=20
problem.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D980315417-20012004></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004>More=20
Info:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004> =
NT Clients=20
are WinNT SP6A</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004> =
2K Clients=20
are Win2K SP4</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D980315417-20012004></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004> =
I've seen=20
messages saying "Drive at or near capacity" in the event logs on several =
of=20
these</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004> =
backup=20
clients. Further, I've noticed that the _vxfiVspCacheFilex.tmp is =
eating=20
up most of the</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004> =
free disk=20
space on these backup clients.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D980315417-20012004></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004> =
Could VSP be=20
causing this problem?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D980315417-20012004> =
If so, what=20
can I do about it? (Don't I need VSP to backup open=20
files?)</SPAN></FONT></DIV>
<P><FONT face=3DArial =
size=3D2>------------------------------------------</FONT>=20
<BR><FONT face=3DArial size=3D2>Tim J. Anderson</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Tim.Anderson AT palmone DOT com</FONT> <BR><FONT face=3DArial=20
size=3D2>408-503-1287</FONT> </P>
<BLOCKQUOTE>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Nash, Ebon=20
[mailto:Ebon_Nash AT compuware DOT com]<BR><B>Sent:</B> Tuesday, January 20, =
2004=20
9:22 AM<BR><B>To:</B> Tim Anderson<BR><B>Subject:</B> RE: [Veritas-bu] =
NBU 5.0=20
- errors 26, 41, and 42<BR><BR></FONT></DIV>
<DIV><SPAN class=3D345162117-20012004><FONT face=3DArial =
color=3D#0000ff size=3D2>If=20
you haven't already don't use autonegotiation on the switch ports or=20
nics. If on a 100MB network force them to =
100FULL.</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]<B>On Behalf Of =
</B>Tim=20
Anderson<BR><B>Sent:</B> Tuesday, January 20, 2004 11:42 =
AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] =
NBU 5.0 -=20
errors 26, 41, and 42<BR><BR></FONT></DIV><!-- Converted from =
text/rtf format -->
<P><FONT face=3DArial size=3D2>We've recently implemented a backup =
solution=20
using Veritas NBU 5.0GA on a Solaris 8 server.</FONT> </P>
<P><FONT face=3DArial size=3D2>Several of the backup clients (all =
running NBU=20
5.0GA) get an error 26 (client/server handshaking failed)</FONT> =
<BR><FONT=20
face=3DArial size=3D2>on the first backup attempt, yet, with no =
action by myself=20
or others, succeed on the second attempt.</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Sometimes, the clients fail the second attempt and I must =
manually=20
resume the job to get a successful</FONT> <BR><FONT face=3DArial=20
size=3D2>backup.</FONT> <BR><FONT face=3DArial size=3D2>The clients =
are all=20
WinNT. Three of the WinNT clients have this problem =
regularly. =20
Three other WinNT</FONT> <BR><FONT face=3DArial size=3D2>clients =
periodically=20
have this problem.</FONT> </P>
<P><FONT face=3DArial size=3D2>Also, I have several Win2K clients =
(all running=20
NBU 5.0GA) that have a similar problem (5 out of 19 =
clients).</FONT>=20
<BR><FONT face=3DArial size=3D2>These clients get an error 41 and/or =
42 (network=20
read/write fail) sometime after the backup has begun.</FONT> =
<BR><FONT=20
face=3DArial size=3D2>Most succeed on the second attempt. =
Sometimes the=20
second attempt fails and I must manually resume</FONT> <BR><FONT =
face=3DArial=20
size=3D2>the jobs to get a good backup.</FONT> </P>
<P><FONT face=3DArial size=3D2>Veritas support has been looking into =
this, but=20
as yet it is not resolved.</FONT> <BR><FONT face=3DArial =
size=3D2>Things We've=20
done:</FONT> <BR><FONT face=3DArial size=3D2> - latest patch =
on network=20
drivers on Solaris Server</FONT> <BR><FONT face=3DArial =
size=3D2> - set=20
the "client read" and "file browse" timeouts on both the master and =
clients=20
to 900 seconds (up from 300 seconds)</FONT></P>
<P><FONT face=3DArial size=3D2> - lots and lots of logging =
analysis</FONT>=20
</P>
<P><FONT face=3DArial size=3D2>Any suggestions/ideas?</FONT> </P>
<P><FONT face=3DArial =
size=3D2>------------------------------------------</FONT>=20
<BR><FONT face=3DArial size=3D2>Tim J. Anderson</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Tim.Anderson AT palmone DOT com</FONT> <BR><FONT face=3DArial=20
size=3D2>408-503-1287</FONT> </P><BR></BLOCKQUOTE><BR><BR><BR>
<P><B><FONT face=3DArial size=3D2>The contents of this e-mail are =
intended for the=20
named addressee only. It contains information that may be =
confidential. Unless=20
you are the named addressee or an authorized designee, you may not =
copy or use=20
it, or disclose it to anyone else. If you received it in error please =
notify=20
us immediately and then destroy it.</FONT></B>=20
</P><BR></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C3DF81.CC86F279--
|
