|
[Veritas-bu] OTM Tuning and NBU 3.4
2001-05-04 15:57:58
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_01C0D4D4.8490C7D0
Content-Type: text/plain;
charset="iso-8859-1"
Has anyone messed around with tuning OTM in connection with NBU 3.4? I was
looking for anything to be wary of when changing the OTM_Quiescent_Timeout
and the OTM_Quiescent_Wait parms. I have the OTM Tuning white paper, but it
doesn't tell you much other than what the field is for and the default
value. I was thinking of pushing the OTM_Quiescent_Timeout value to 60
seconds and the OTM_Quiescent_Wait to 300 seconds. Thoughts?
------_=_NextPart_001_01C0D4D4.8490C7D0
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.2654.19">
<TITLE>OTM Tuning and NBU 3.4</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Has anyone messed around with tuning OTM in =
connection with NBU 3.4? I was looking for anything to be wary of =
when changing the OTM_Quiescent_Timeout and the OTM_Quiescent_Wait =
parms. I have the OTM Tuning white paper, but it doesn't tell you much =
other than what the field is for and the default value. I was =
thinking of pushing the OTM_Quiescent_Timeout value to 60 seconds and =
the OTM_Quiescent_Wait to 300 seconds. Thoughts?</FONT></P>
</BODY>
</HTML>
------_=_NextPart_001_01C0D4D4.8490C7D0--
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Veritas-bu] OTM Tuning and NBU 3.4,
Reese, Paul E. (CAP, CMC) <=
|
|
|
