Veritas-bu

[Veritas-bu] Compaq Giga-NIC's - NC6134, NC6136, NC6132

2002-10-28 11:02:04
Subject: [Veritas-bu] Compaq Giga-NIC's - NC6134, NC6136, NC6132
From: Wayne.Cierkowski AT harpercollins DOT com (Cierkowski, Wayne)
Date: Mon, 28 Oct 2002 11:02:04 -0500
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_01C27E9B.5BF0E5E0
Content-Type: text/plain; charset="iso-8859-1"

To all,

I have just spend 5 days attempting to restore a 190 GB SQL database. Every
time we would start the restore, SQL would go out there and create the data
container files and then when it was to start the data restore, the job
would fail with a Socket Write Failed. Indication in the BPBRM log would be
a status 24 and then a 10054 network issue. 

I then discovered that the patch I have been applying to all of our servers
has not really been going on OK, even though the patch install said is
installed successfully. The indication was BPCD module on all of our box's
was at version level 3.41.0.132. This version level is actually from patch
645. The version for patch 3A is actually 3.41.0.175. Even though the patch
reported a successful installation BPCD was not updated not too mention
whatever other modules did not get updated. 

I then brought down Patch 4 from the WEB site and applied it. It did update
module BPCD to 3.41.0.185 as it should. But this did not resolve the issue
of restoring the database. 

After countless calls to tech support on a Sunday afternoon we hit the holy
grail. Tech support was researching their internal knowledge base and hit on
a technote discussing Compaq Gigabit network cards. Low and behold the one
of the suspect NIC's called out in this technote we were running with,
Compaq NC6134. There is a problem with Netbackup and this card that can and
will have network issues. Network timeouts and Socket Write Failures. Oh
yea, tech support also had the output from the NB support script in their
possession from my master/media server. Which if you look at the
local.interfaces it tells them what NIC is installed in your machine. 

I down graded the Master/Media NIC to a Compaq 100 Mb card and attempted
some test restores. They all worked compared to the failures I was getting.
I was then able to restore the 190 GB database in a little over 13 hours. 

Just wanted to let everyone in Netbackup land know about what I went through
the last five days. Also note this problem was originally opened with
Veritas on Wednesday morning 10/23 as a "Sev 1 Server Down" condition and I
finally got problem resolution on Sunday 10/27 at 2:30 in the afternoon.
Sort of glad this was not a major server for our business.... 

Wayne D. Cierkowski



***************************************************************
This message is intended only for the use of the individuals to which it is 
addressed 
and may contain information that is privileged and confidential. If you are not 
the intended 
recipient, you are hereby notified that you have received this transmission in 
error; 
any review, dissemination, distribution or copying of this transmission is 
prohibited.
If you have received this communication in error, please notify us immediately 
by reply 
e-mail and delete this message and all of its attachments.


------_=_NextPart_001_01C27E9B.5BF0E5E0
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>Compaq Giga-NIC's - NC6134, NC6136, NC6132</TITLE>
</HEAD>
<BODY>

<P><FONT FACE=3D"Times New Roman">To all,</FONT>
</P>

<P><FONT FACE=3D"Times New Roman">I have just spend 5 days attempting to re=
store a 190 GB SQL database. Every time we would start the restore, SQL wou=
ld go out there and create the data container files and then when it was to=
 start the data restore, the job would fail with a Socket Write Failed. Ind=
ication in the BPBRM log would be a status 24 and then a 10054 network issu=
e. </FONT></P>

<P><FONT FACE=3D"Times New Roman">I then discovered that the patch I have b=
een applying to all of our servers has not really been going on OK, even th=
ough the patch install said is installed successfully. The indication was B=
PCD module on all of our box's was at version level 3.41.0.132. This versio=
n level is actually from patch 645. The version for patch 3A is actually 3.=
41.0.175. Even though the patch reported a successful installation BPCD was=
 not updated not too mention whatever other modules did not get updated. </=
FONT></P>

<P><FONT FACE=3D"Times New Roman">I then brought down Patch 4 from the WEB =
site and applied it. It did update module BPCD to 3.41.0.185 as it should. =
But this did not resolve the issue of restoring the database. </FONT></P>

<P><FONT FACE=3D"Times New Roman">After countless calls to tech support on =
a Sunday afternoon we hit the holy grail. Tech support was researching thei=
r internal knowledge base and hit on a technote discussing Compaq Gigabit n=
etwork cards. Low and behold the one of the suspect NIC's called out in thi=
s technote we were running with, Compaq NC6134. There is a problem with Net=
backup and this card that can and will have network issues. Network timeout=
s and Socket Write Failures. Oh yea, tech support also had the output from =
the NB support script in their possession from my master/media server. Whic=
h if you look at the local.interfaces it tells them what NIC is installed i=
n your machine. </FONT></P>

<P><FONT FACE=3D"Times New Roman">I down graded the Master/Media NIC to a C=
ompaq 100 Mb card and attempted some test restores. They all worked compare=
d to the failures I was getting. I was then able to restore the 190 GB data=
base in a little over 13 hours. </FONT></P>

<P><FONT FACE=3D"Times New Roman">Just wanted to let everyone in Netbackup =
land know about what I went through the last five days. Also note this prob=
lem was originally opened with Veritas on Wednesday morning 10/23 as a &quo=
t;Sev 1 Server Down&quot; condition and I finally got problem resolution on=
 Sunday 10/27 at 2:30 in the afternoon. Sort of glad this was not a major s=
erver for our business.... </FONT></P>

<P><B><FONT FACE=3D"Comic Sans MS">Wayne D. Cierkowski</FONT></B>
</P>

<CODE><FONT SIZE=3D3><BR>
<BR>
***************************************************************<BR>
This message is intended only for the use of the individuals to which it is=
 addressed <BR>
and may contain information that is privileged and confidential. If you are=
 not the intended <BR>
recipient, you are hereby notified that you have received this transmission=
 in error; <BR>
any review, dissemination, distribution or copying of this transmission is =
prohibited.<BR>
If you have received this communication in error, please notify us immediat=
ely by reply <BR>
e-mail and delete this message and all of its attachments.<BR>
</FONT></CODE>
</BODY>
</HTML>
------_=_NextPart_001_01C27E9B.5BF0E5E0--

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] Compaq Giga-NIC's - NC6134, NC6136, NC6132, Cierkowski, Wayne <=