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_01C100D6.4E6C3440
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: 7bit
This is an issue for many app.s. In one of the Sun Blueprint articles (one
of the security ones I think) they recommend reducing
tcp_close_wait_interval significantly (though not as much as this). The
Blueprint article has an associated script (nddconfig) that will check
and/or make the recommended changes of the various ndd settings.
-----Original Message-----
From: W. Curtis Preston [mailto:curtis AT backupcentral DOT com]
Sent: Friday, June 29, 2001 10:27 AM
To: jmeyer AT ptc DOT com; rah_work AT hotmail DOT com
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Qued jobs not being assigned to tapes.
That was it! I believe that we had the same fix for the same problem.
(It's been over a year...)
At 10:40 AM 6/29/2001 -0400, Jonathan Meyer wrote:
>Robert,
>
>we had a problem which was very similar to the symptoms you describe.
>Our problem occurred on a single solaris master server and exhibited
>the following symptoms.
>
> o Tapes were not unloaded when backups completed.
> o Jobs which were queued never became active.
> o Once the problem started, we could not get anything to run until
> we stopped and started all netbackup processes.
>
>We worked with veritas support on this issue for a while, and they
>could not find anything similar at first.
>
>Eventually, they suggested that similar symptoms can be caused by
>running out of reserved ports on the system. The symptoms above are
>not the listed symptoms caused by running out of reserved ports, but
>apparently running out of these ports can cause unpredictable
>behavior.
>
>If your problem is similar to the one we experienced, there are a
>number of possible solutions discussed at
>http://seer.support.veritas.com/docs/234618.htm.
>
>The solution we implemented was to reduce tcp_close_wait_interval by
>putting the following in our boot sequence.
>
>ndd -set /dev/tcp tcp_close_wait_interval 1000
>
>This change fixed our problem. This was on a solaris 2.6 system. I
>am not sure if the same parameter applies to other OS versions.
>
>As the technote warns, this change should not be made lightly and
>should be closely observed afterward. The solaris default for this
>parameter is 250000, so this is a significant change.
>
>However, for those of you who have the vault product, you may
>recognize that this same change is recommended in the vault manuals to
>solve some problems with duplication on solaris. It is my
>understanding that this parameter will probably not cause adverse
>effects if the systems are connected by a high speed switched network.
>
>The technote describes other possible solutions, and also some details
>about what you might see in your bptm log if this is the problem you
>are having.
>
>--------------------------------------------------
>Jonathan Meyer
>(781)370-6594
>UNIX Systems Administrator
>Paramtric Technology Corporation
>--------------------------------------------------
>
>_______________________________________________
>Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
---
W. Curtis Preston
Principal Consultant for Storage Designs, your storage experts
Webmaster: http://www.backupcentral.com Phone: 760 653 1007
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C100D6.4E6C3440
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] Qued jobs not being assigned to tapes.</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>This is an issue for many app.s. In one of the =
Sun Blueprint articles (one of the security ones I think) they =
recommend reducing tcp_close_wait_interval significantly (though not as =
much as this). The Blueprint article has an associated script =
(nddconfig) that will check and/or make the recommended changes =
of the various ndd settings.</FONT></P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: W. Curtis Preston [<A =
HREF=3D"mailto:curtis AT backupcentral DOT com">mailto:curtis AT backupcentral
DOT com=
</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, June 29, 2001 10:27 AM</FONT>
<BR><FONT SIZE=3D2>To: jmeyer AT ptc DOT com; rah_work AT hotmail DOT com</FONT>
<BR><FONT SIZE=3D2>Cc: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] Qued jobs not being =
assigned to tapes.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>That was it! I believe that we had the same fix for =
the same problem.</FONT>
<BR><FONT SIZE=3D2>(It's been over a year...)</FONT>
</P>
<P><FONT SIZE=3D2>At 10:40 AM 6/29/2001 -0400, Jonathan Meyer =
wrote:</FONT>
</P>
<P><FONT SIZE=3D2>>Robert,</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>we had a problem which was very similar to the =
symptoms you describe.</FONT>
<BR><FONT SIZE=3D2>>Our problem occurred on a single solaris master =
server and exhibited</FONT>
<BR><FONT SIZE=3D2>>the following symptoms.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> o Tapes were not =
unloaded when backups completed.</FONT>
<BR><FONT SIZE=3D2>> o Jobs which were =
queued never became active.</FONT>
<BR><FONT SIZE=3D2>> o Once the problem =
started, we could not get anything to run until</FONT>
<BR><FONT SIZE=3D2>> we stopped =
and started all netbackup processes.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>We worked with veritas support on this issue for =
a while, and they</FONT>
<BR><FONT SIZE=3D2>>could not find anything similar at first.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>Eventually, they suggested that similar symptoms =
can be caused by</FONT>
<BR><FONT SIZE=3D2>>running out of reserved ports on the =
system. The symptoms above are</FONT>
<BR><FONT SIZE=3D2>>not the listed symptoms caused by running out of =
reserved ports, but</FONT>
<BR><FONT SIZE=3D2>>apparently running out of these ports can cause =
unpredictable</FONT>
<BR><FONT SIZE=3D2>>behavior.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>If your problem is similar to the one we =
experienced, there are a</FONT>
<BR><FONT SIZE=3D2>>number of possible solutions discussed at</FONT>
<BR><FONT SIZE=3D2>><A =
HREF=3D"http://seer.support.veritas.com/docs/234618.htm"; =
TARGET=3D"_blank">http://seer.support.veritas.com/docs/234618.htm</A>.</=
FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>The solution we implemented was to reduce =
tcp_close_wait_interval by</FONT>
<BR><FONT SIZE=3D2>>putting the following in our boot =
sequence.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>ndd -set /dev/tcp tcp_close_wait_interval =
1000</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>This change fixed our problem. This was on =
a solaris 2.6 system. I</FONT>
<BR><FONT SIZE=3D2>>am not sure if the same parameter applies to =
other OS versions.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>As the technote warns, this change should not be =
made lightly and</FONT>
<BR><FONT SIZE=3D2>>should be closely observed afterward. The =
solaris default for this</FONT>
<BR><FONT SIZE=3D2>>parameter is 250000, so this is a significant =
change.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>However, for those of you who have the vault =
product, you may</FONT>
<BR><FONT SIZE=3D2>>recognize that this same change is recommended =
in the vault manuals to</FONT>
<BR><FONT SIZE=3D2>>solve some problems with duplication on =
solaris. It is my</FONT>
<BR><FONT SIZE=3D2>>understanding that this parameter will probably =
not cause adverse</FONT>
<BR><FONT SIZE=3D2>>effects if the systems are connected by a high =
speed switched network.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>The technote describes other possible solutions, =
and also some details</FONT>
<BR><FONT SIZE=3D2>>about what you might see in your bptm log if =
this is the problem you</FONT>
<BR><FONT SIZE=3D2>>are having.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT =
SIZE=3D2>>--------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>>Jonathan Meyer</FONT>
<BR><FONT SIZE=3D2>>(781)370-6594</FONT>
<BR><FONT SIZE=3D2>>UNIX Systems Administrator</FONT>
<BR><FONT SIZE=3D2>>Paramtric Technology Corporation</FONT>
<BR><FONT =
SIZE=3D2>>--------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>></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>
<P><FONT SIZE=3D2>---</FONT>
<BR><FONT SIZE=3D2>W. Curtis Preston</FONT>
<BR><FONT SIZE=3D2>Principal Consultant for Storage Designs, your =
storage experts</FONT>
<BR><FONT SIZE=3D2>Webmaster: <A HREF=3D"http://www.backupcentral.com"; =
TARGET=3D"_blank">http://www.backupcentral.com</A> Phone: 760 653 =
1007</FONT>
</P>
<P><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_01C100D6.4E6C3440--
|
