This is a multipart message in MIME format.
--=_alternative 00673BAE86256E58_=
Content-Type: text/plain; charset="US-ASCII"

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
--=_alternative 00673BAE86256E58_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Well</font>
<br><font size=3>&nbsp;</font>
<table width=100%>
<tr>
<td width=100%><font size=1 face="Arial"># cat 
/usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS<br>
262144</font></table>
<br>
<br><font size=2 face="sans-serif">is ok as far as i know for LTO2 
drives.</font>
<br>
<br><font size=3>&nbsp;</font>
<table width=100%>
<tr>
<td width=100%><font size=1 face="Arial"># cat 
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS<br>
256</font></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>
--=_alternative 00673BAE86256E58_=--