Veritas-bu

[Veritas-bu] Re-queuing jobs due to busy resources(134)

2006-03-01 13:31:27
Subject: [Veritas-bu] Re-queuing jobs due to busy resources(134)
From: cheryl.king AT intrado DOT com (King, Cheryl)
Date: Wed, 1 Mar 2006 11:31:27 -0700
This is a multi-part message in MIME format.

------_=_NextPart_001_01C63D5E.5AD17041
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I get these all the time.  However, when I first put in SSO, I had an
unusually high # of them, like more than 50 every night.  I'm trying to
remember what Veritas support had me do to get these down to a more
reasonable # and I think it was adding SSO_SCAN_ABILITY =3D 9 to
/usr/openv/volmgr/vm.conf on the master server.  This will make the
master server the SCAN host most of the time.

=20

SSO_SCAN_ABILITY may have from to 0 - 9. The larger the scan ability,
the more likely the host will be to become the scan host.  Setting it to
zero means it will never become the SCAN_HOST.

=20

When a 134 occurs the jobs will re-que if the backup window is still
open.   The 134 happens when a job starts and all drives are already
assigned.  In my case, where all 4 media servers share all 8 tape
drives, I could probably set the other media servers to 0 so they would
never become the SCAN_HOST and I'd eliminate the 134s.  I might try
that.=20

=20

________________________________

From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Justin
Piszcz
Sent: Wednesday, March 01, 2006 7:10 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Re-queuing jobs due to busy resources(134)

=20

Does anyone know which kernel sysctl or configuration option or
netbackup? option is related to this error?
Is it the number of maximum file descriptors or the fd limit?

Anyone ever get these in the past and then fix the issue?=20

Thanks,

Justin.


------_=_NextPart_001_01C63D5E.5AD17041
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40";>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I get these all the time.&nbsp; =
However,
when I first put in SSO, I had an unusually high # of them, like more =
than 50
every night.&nbsp; I&#8217;m trying to remember what Veritas support had =
me do
to get these down to a more reasonable # and I think it was adding
SSO_SCAN_ABILITY =3D 9 to /usr/openv/volmgr/vm.conf on the master =
server.&nbsp;
This will make the master server the SCAN host most of the =
time.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>SSO_SCAN_ABILITY may have
from to 0 - 9. The larger the scan ability, the more likely the host =
will be to
become the scan host.&nbsp; Setting it to zero means it will never =
become the
SCAN_HOST.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span style=3D'font-size:10.0pt'>When a 134 =
occurs the
jobs will re-que if the backup window is still open.&nbsp; &nbsp;The 134 =
happens
when a job starts and all drives are already assigned.&nbsp; In my case, =
where
all 4 media servers share all 8 tape drives, I could probably set the =
other
media servers to 0 so they would never become the SCAN_HOST and =
I&#8217;d
eliminate the 134s.&nbsp; I might try that. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Justin Piszcz<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, March =
01, 2006
7:10 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b>
veritas-bu AT mailman.eng.auburn DOT edu<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Veritas-bu] =
Re-queuing
jobs due to busy resources(134)</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Does anyone know which kernel sysctl or configuration option or
netbackup? option is related to this error?<br>
Is it the number of maximum file descriptors or the fd limit?<br>
<br>
Anyone ever get these in the past and then fix the issue? <br>
<br>
Thanks,<br>
<br>
Justin.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C63D5E.5AD17041--

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