--0-1978300418-1079381184=:37216
Content-Type: text/plain; charset=us-ascii

do you see error messages about allocating shared mem when you have jobs 
starting up  (in the netbackup logs)?  if not, what does prstat (or top if you 
have it) show for process mem usage?  is your swap getting killed?

Karl.Rossing AT Federated DOT CA wrote:
Well 
  # cat /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
262144

is ok as far as i know for LTO2 drives. 

  # cat /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
256

Which might be a little bit excessive in our environment. 

I think i'll drop it to 128 for tonight and see if things speed up. 


veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 03/15/2004 12:30:17 PM:

> It's going to be a number-data-buffers times size-data-buffers 
> thing.  Can't exceed memory, of course. 
>   
> There's a tuning doc that describes the relationship at: 
>   
> http://seer.support.veritas.com/docs/183702.htm 
>   
> -M 
> -----Original Message-----
> From: Karl.Rossing AT Federated DOT CA [mailto:Karl.Rossing AT Federated DOT 
> CA]
> Sent: Monday, March 15, 2004 10:41 AM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] LTO2 maxing out memory

> 
> I got a sneaking suspicion that our netbackup server with an  LTO2 
> tape drive is maxing out on memory(512MB) on solaris 8. 
> 
> Doesn't anyone have any tips on how to check this in solaris 8? 
> 
> Thanks, 
> Karl


aaarrrggghhh!!!!
FreeBSD rocks
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
--0-1978300418-1079381184=:37216
Content-Type: text/html; charset=us-ascii

<DIV>do you see error messages about allocating shared mem when you have jobs 
starting up&nbsp; (in the netbackup logs)?&nbsp; if not, what does prstat (or 
top if you have it) show for process mem usage?&nbsp; is your swap getting 
killed?<BR><BR><B><I>Karl.Rossing AT Federated DOT CA</I></B> wrote:
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; 
BORDER-LEFT: #1010ff 2px solid"><BR><FONT face=sans-serif size=2>Well</FONT> 
<BR><FONT size=3>&nbsp;</FONT> 
<TABLE width="100%">
<TBODY>
<TR>
<TD width="100%"><FONT face=Arial size=1># cat 
/usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS<BR>262144</FONT></TR></TBODY></TABLE><BR><BR><FONT
 face=sans-serif size=2>is ok as far as i know for LTO2 drives.</FONT> 
<BR><BR><FONT size=3>&nbsp;</FONT> 
<TABLE width="100%">
<TBODY>
<TR>
<TD width="100%"><FONT face=Arial size=1># cat 
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS<BR>256</FONT></TR></TBODY></TABLE><BR><BR><FONT
 size=3>Which might be a little bit excessive in our environment.</FONT> 
<BR><BR><FONT size=3>I think i'll drop it to 128 for tonight and see if things 
speed up.</FONT> <BR><BR><BR><FONT size=2><TT>veritas-bu-admin AT 
mailman.eng.auburn DOT edu wrote on 03/15/2004 12:30:17 PM:<BR><BR>&gt; It's 
going to be a number-data-buffers times size-data-buffers <BR>&gt; thing. 
&nbsp;Can't exceed memory, of course.</TT></FONT> <BR><FONT size=2><TT>&gt; 
&nbsp;</TT></FONT> <BR><FONT size=2><TT>&gt; There's a tuning doc that 
describes the relationship at: </TT></FONT><BR><FONT size=2><TT>&gt; 
&nbsp;</TT></FONT> <BR><FONT size=2><TT>&gt; 
http://seer.support.veritas.com/docs/183702.htm</TT></FONT> <BR><FONT 
size=2><TT>&gt; &nbsp;</TT></FONT> <BR><FONT size=2><TT>&gt; -M</TT></FONT> 
<BR><FONT size=2><TT>&gt; -----Original Message-----<BR>&gt; From:
 Karl.Rossing AT Federated DOT CA [mailto:Karl.Rossing AT Federated DOT 
CA]<BR>&gt; Sent: Monday, March 15, 2004 10:41 AM<BR>&gt; To: veritas-bu AT 
mailman.eng.auburn DOT edu<BR>&gt; Subject: [Veritas-bu] LTO2 maxing out 
memory<BR></TT></FONT><BR><FONT size=2><TT>&gt; <BR>&gt; I got a sneaking 
suspicion that our netbackup server with an &nbsp;LTO2 <BR>&gt; tape drive is 
maxing out on memory(512MB) on solaris 8. <BR>&gt; <BR>&gt; Doesn't anyone have 
any tips on how to check this in solaris 8? <BR>&gt; <BR>&gt; Thanks, <BR>&gt; 
Karl</TT></FONT></BLOCKQUOTE></DIV><BR><BR>aaarrrggghhh!!!!<br>FreeBSD 
rocks<p><font face=arial size=-1>Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/mailtag_us/*http://mail.yahoo.com"; 
target="_blank"><b>Yahoo! Mail</a></b> - More reliable, more storage, less spam
--0-1978300418-1079381184=:37216--