[Veritas-bu] Optimal Disk Setup

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_01C20018.B5383748
Content-Type: text/plain;
        charset="iso-8859-1"

This might be a strange question with several different correct answers. :-) We 
are trying to advise our NT group on the best way to lay out about 350 gig of 
file server space to be able to optimally backup and restore it. One of our 
ideas was to split it up into 7 - 50 gig pieces. They want fast backups aas 
well as restores, and I know there is give and take as far as multiplexing will 
give faster backups, but slow down restores. 

Does anyone have any ideas on how to set this up. For reference we are using 
STK 9840B drives backing up to a Powderhorn w/ ACSLS...

Thanks,
Harry S.
Atlanta

------_=_NextPart_001_01C20018.B5383748
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.2655.35">
<TITLE>Optimal Disk Setup</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>This might be a strange question with several =
different correct answers. :-) We are trying to advise our NT group on =
the best way to lay out about 350 gig of file server space to be able =
to optimally backup and restore it. One of our ideas was to split it up =
into 7 - 50 gig pieces. They want fast backups aas well as restores, =
and I know there is give and take as far as multiplexing will give =
faster backups, but slow down restores. </FONT></P>

<P><FONT SIZE=3D2>Does anyone have any ideas on how to set this up. For =
reference we are using STK 9840B drives backing up to a Powderhorn w/ =
ACSLS...</FONT></P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Harry S.</FONT>
<BR><FONT SIZE=3D2>Atlanta</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C20018.B5383748--