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_ST_14_40_41_Thursday_April_08_2004_23582
Content-Type: text/plain
David,
We have been running (well most of the time!) the SQL DB backups with W2k
for three years now. I have always used '4' for 'MAXTRANSFERSIZE' with '6'
as a value for 'BLOCKSIZE'. I did test various values two years ago and
found that '4' and '6' provided the best throughput but I don't have
scientific proof. We are running W2K and W2K3 servers with SAP and SQL
DB's.
Regards,
Rick Morris
IGT - SAP Basis Administration
-----Original Message-----
From: David_Attreed AT Countrywide DOT Com [mailto:David_Attreed AT Countrywide
DOT Com]
Sent: Thursday, April 08, 2004 09:30
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] SQL Batch Settings / NBU 4.5
Good morning,
We're just going to start looking at our W2K SQL backups via NetBackup and I
wanted to get some opinions for people who've been down the road already.
We're currently running several dozen SQL (7/2k) backups via the database
extension batch files to a W2K NBU 4.5_fp6 setup - and the backups are
running fine apart from a few stragglers that take forever.
Having just read through the SQL / NBU pdf, I get the impression that
increasing the "MAXTRANSFERSIZE" from its current setting of "0" to a figure
of "4" (4 x 64k) would then make the data coming off of the database the
same buffer size as the rest of our environment, 256k. Is this a correct
interpretation?
"BLOCKSIZE" is next on my list to test different settings of so any
suggestions on that also?
Its an all W2K NBU environment.
Regards,
David Attreed.
----=_NextPart_ST_14_40_41_Thursday_April_08_2004_23582
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=245360818-08042004><FONT face=Arial color=#0000ff
size=2>David,</FONT></SPAN></DIV>
<DIV><SPAN class=245360818-08042004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=245360818-08042004>We have been running (well most of the time!) the SQL
DB backups with W2k for three years now. I have always used '4' for
<STRONG>'MAXTRANSFERSIZE'</STRONG></SPAN><STRONG> </STRONG><SPAN
class=245360818-08042004><STRONG></STRONG> with '6' as a value for
<STRONG>'BLOCKSIZE'.</STRONG> I did test various values two years ago and
found that '4' and '6' provided the best throughput but I don't have
scientific proof. We are running W2K and W2K3 servers with SAP
and SQL DB's.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=245360818-08042004></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=245360818-08042004>Regards,</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=245360818-08042004><FONT size=2>
<P>Rick Morris</P></FONT><FONT color=#008080 size=2>
<P><STRONG>IGT - SAP Basis
Administration</STRONG></FONT></SPAN></FONT></FONT></FONT></P></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=245360818-08042004></SPAN></FONT></FONT></FONT> </DIV>
<DIV></DIV>
<DIV><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
David_Attreed AT Countrywide DOT Com [mailto:David_Attreed AT Countrywide DOT
Com]
<BR><B>Sent:</B> Thursday, April 08, 2004 09:30<BR><B>To:</B>
Veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] SQL
Batch
Settings / NBU 4.5<BR><BR></DIV></FONT>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px"><BR><FONT face=sans-serif size=2>Good
morning,</FONT> <BR><BR><FONT face=sans-serif size=2>We're just going to
start
looking at our W2K SQL backups via NetBackup and I wanted to get some
opinions
for people who've been down the road already. We're currently running several
dozen SQL (7/2k) backups via the database extension batch files to a W2K NBU
4.5_fp6 setup - and the backups are running fine apart from a few stragglers
that take forever.</FONT> <BR><BR><FONT face=sans-serif size=2>Having just
read through the SQL / NBU pdf, I get the impression that increasing the
"MAXTRANSFERSIZE" from its current setting of "0" to a figure of "4" (4 x
64k)
would then make the data coming off of the database the same buffer size as
the rest of our environment, 256k. Is this a correct interpretation?</FONT>
<BR><BR><FONT face=sans-serif size=2>"BLOCKSIZE" is next on my list to test
different settings of so any suggestions on that also?</FONT> <BR><BR><FONT
face=sans-serif size=2>Its an all W2K NBU environment.</FONT> <BR><FONT
face=sans-serif size=2><BR><BR>Regards,<BR>David
Attreed.<BR></BLOCKQUOTE></FONT></BODY></HTML>
----=_NextPart_ST_14_40_41_Thursday_April_08_2004_23582--
|
