Veritas-bu

[Veritas-bu] Bpsched crashing

2006-05-15 10:06:24
Subject: [Veritas-bu] Bpsched crashing
From: Greg.Hindle AT constellation DOT com (Hindle, Greg)
Date: Mon, 15 May 2006 10:06:24 -0400
This is a multi-part message in MIME format.

------_=_NextPart_001_01C67828.C019386A
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

We had the shared memory setting set to use all available memory and
were told by Symantec to lower that figure to 6 gig and leave 2 gig for
Solaris 9 (we jave 8 gig ram). We have not adjusted any msg queues.
Where would I look and what should they be?=20
=20


Greg


________________________________

From: Len Boyle [mailto:Len.Boyle AT sas DOT com]=20
Sent: Monday, May 15, 2006 9:48 AM
To: Hindle, Greg; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Bpsched crashing


Good Morning Greg,=20
=20
Have you changed setting in the /etc/system file to increased things
such as shared memory and msg queues?=20
=20
len

________________________________

From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Hindle,
Greg
Sent: Monday, May 15, 2006 9:04 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Bpsched crashing



Nb 5.0 mp6 Solaris 9=20

We are having an on going issue with bpsched crashing/stopping. When
this happens all the jobs go 150. Sometimes it recovers and restarts the
jobs and other times we have to stop and start the services. Has any one
else had this issues and what you did to fix? We have a open ticket with
Symantec and they have recommend some tuning changes, which we have
done, but it still went down over the weekend. Symantec thinks it is a
resource issue. We have 8 gig of ram in the master server and it seems
to crash most often about 15 minutes in the main backup window. We would
have around 200 jobs running, with 800 queued. This has not been an
issue in the past. Any ideas?


Greg=20

>>> This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely
for the addressee.  If you are not the intended recipient, do not use
the information in this e-mail in any way, delete this e-mail and notify
the sender. CEG-IP1

------_=_NextPart_001_01C67828.C019386A
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Bpsched crashing</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D332480114-15052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>We had the shared memory setting set to use all =
available=20
memory and were told by Symantec to lower that figure to 6 gig and =
leave&nbsp;2=20
gig for&nbsp;Solaris 9 (we jave 8 gig ram). We have not adjusted any msg =
queues.=20
Where would I look and what should =
they&nbsp;be?&nbsp;</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV><!-- Converted from text/rtf format --><BR>
<P><SPAN lang=3Den-us><FONT face=3D"Times New Roman"=20
size=3D2>Greg</FONT></SPAN></P><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Len Boyle =
[mailto:Len.Boyle AT sas DOT com]=20
<BR><B>Sent:</B> Monday, May 15, 2006 9:48 AM<BR><B>To:</B> Hindle, =
Greg;=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
Bpsched=20
crashing<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995502613-15052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Good Morning Greg, </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995502613-15052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995502613-15052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Have you changed setting in the /etc/system =
file to=20
increased things such as shared memory and msg queues? =
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995502613-15052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D995502613-15052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>len</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
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>Hindle,=20
Greg<BR><B>Sent:</B> Monday, May 15, 2006 9:04 AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] =
Bpsched=20
crashing<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=3DArial size=3D2>Nb 5.0 mp6 Solaris 9</FONT> </P>
<P><FONT face=3DArial size=3D2>We are having an on going issue with =
bpsched=20
crashing/stopping. When this happens all the jobs go 150. Sometimes it =
recovers=20
and restarts the jobs and other times we have to stop and start the =
services.=20
Has any one else had this issues and what you did to fix? We have a open =
ticket=20
with Symantec and they have recommend some tuning changes, which we have =
done,=20
but it still went down over the weekend. Symantec thinks it is a =
resource issue.=20
We have 8 gig of ram in the master server and it seems to crash most =
often about=20
15 minutes in the main backup window. We would have around 200 jobs =
running,=20
with 800 queued. This has not been an issue in the past. Any=20
ideas?</FONT></P><BR>
<P><FONT face=3D"Times New Roman" size=3D2>Greg</FONT> =
</P><PRE>&gt;&gt;&gt; This e-mail and any attachments are confidential, =
may contain legal, professional or other privileged information, and are =
intended solely for the addressee.  If you are not the intended =
recipient, do not use the information in this e-mail in any way, delete =
this e-mail and notify the sender. CEG-IP1
</PRE></BODY></HTML>

------_=_NextPart_001_01C67828.C019386A--

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