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_01C1E70F.B2EAC2E0
Content-Type: text/plain;
charset="iso-8859-1"
This close to v4.5, it might be cleaner, though to do as suggested before, a
Dup class with drive letters and a non-dup class with the other drives.
When we get dual-writes in 4.5, it'll be all set for write-time duplications
on a per class basis. Until that time, he can identify the images to be
backed up by class name.
-----Original Message-----
From: Winkeler, Paul [mailto:PWinkeler AT officemax DOT com]
Mark,
Right you are there! I have some Perl code that will pull the file list for
an image so I can tie it all together. So, in theory anyway, I could figure
out on the fly which of the image corresponds to which of the drives. But
as I heard one of my professors state once:
"In theory, the difference between theory and practice is a lot smaller
than in practice!"
Let me know if anyone wants to pursue this path. I've got to believe, given
the speed with which NT systems get backed up, that this would still be
faster than backing the same drive up twice, no?
PaulW
-----Original Message-----
From: Donaldson, Mark [mailto:Mark.Donaldson AT experianems DOT com]
The trick, however, is figuring out at duplication time which of the images
contains the drives he wants. I think the only option on this is to take
the image list, then dig into the images database for the specific images
that contain the drives he wants to duplicate.
-Mark
-----Original Message-----
From: Winkeler, Paul [ mailto:PWinkeler AT officemax DOT com
<mailto:PWinkeler AT officemax DOT com> ]
Sent: Thursday, April 18, 2002 10:37 AM
To: dayalsd AT lycos DOT com
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] off-site backups
If you back the NT clients up with the ALL_LOCAL_DRIVES directive and you
set the option, multiple streams allowed to true, then you will generate one
image per drive. You can then duplicate the images you want to take
off-site without further ado.
PaulW
_______________________________________________
------_=_NextPart_001_01C1E70F.B2EAC2E0
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.2653.12">
<TITLE>RE: [Veritas-bu] off-site backups</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>This close to v4.5, it might be cleaner, though to do =
as suggested before, a Dup class with drive letters and a non-dup class =
with the other drives. When we get dual-writes in 4.5, it'll be =
all set for write-time duplications on a per class basis. Until =
that time, he can identify the images to be backed up by class =
name.</FONT></P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Winkeler, Paul [<A =
HREF=3D"mailto:PWinkeler AT officemax DOT com">mailto:PWinkeler AT officemax
DOT com</=
A>]</FONT>
</P>
<P><FONT SIZE=3D2>Mark,</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>Right you are there! I have some Perl code =
that will pull the file list for</FONT>
<BR><FONT SIZE=3D2>an image so I can tie it all together. So, in =
theory anyway, I could figure</FONT>
<BR><FONT SIZE=3D2>out on the fly which of the image corresponds to =
which of the drives. But</FONT>
<BR><FONT SIZE=3D2>as I heard one of my professors state once:</FONT>
<BR><FONT SIZE=3D2> "In theory, the difference =
between theory and practice is a lot smaller</FONT>
<BR><FONT SIZE=3D2>than in practice!"</FONT>
<BR><FONT SIZE=3D2>Let me know if anyone wants to pursue this =
path. I've got to believe, given</FONT>
<BR><FONT SIZE=3D2>the speed with which NT systems get backed up, that =
this would still be</FONT>
<BR><FONT SIZE=3D2>faster than backing the same drive up twice, =
no?</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2> PaulW</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Donaldson, Mark [<A =
HREF=3D"mailto:Mark.Donaldson AT experianems DOT com">mailto:Mark.Donaldson@exp=
erianems.com</A>]</FONT>
</P>
<P><FONT SIZE=3D2>The trick, however, is figuring out at duplication =
time which of the images</FONT>
<BR><FONT SIZE=3D2>contains the drives he wants. I think the only =
option on this is to take</FONT>
<BR><FONT SIZE=3D2>the image list, then dig into the images database =
for the specific images</FONT>
<BR><FONT SIZE=3D2>that contain the drives he wants to =
duplicate.</FONT>
</P>
<P><FONT SIZE=3D2>-Mark </FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message----- </FONT>
<BR><FONT SIZE=3D2>From: Winkeler, Paul [ <A =
HREF=3D"mailto:PWinkeler AT officemax DOT com">mailto:PWinkeler AT officemax
DOT com</=
A></FONT>
<BR><FONT SIZE=3D2><<A =
HREF=3D"mailto:PWinkeler AT officemax DOT com">mailto:PWinkeler AT officemax
DOT com</=
A>> ] </FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, April 18, 2002 10:37 AM </FONT>
<BR><FONT SIZE=3D2>To: dayalsd AT lycos DOT com </FONT>
<BR><FONT SIZE=3D2>Cc: veritas-bu AT mailman.eng.auburn DOT edu </FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] off-site backups </FONT>
</P>
<BR>
<P><FONT SIZE=3D2>If you back the NT clients up with the =
ALL_LOCAL_DRIVES directive and you </FONT>
<BR><FONT SIZE=3D2>set the option, multiple streams allowed to true, =
then you will generate one</FONT>
</P>
<P><FONT SIZE=3D2>image per drive. You can then duplicate the =
images you want to take </FONT>
<BR><FONT SIZE=3D2>off-site without further ado. </FONT>
</P>
<P><FONT SIZE=3D2> PaulW </FONT>
<BR><FONT SIZE=3D2>_______________________________________________ =
</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C1E70F.B2EAC2E0--
|
