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_01C24475.3F275580
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Jeff,
This is something very similar to what Curtis Preston talked about at
Vision...I think it's an excellent way to achieve maximum backup and restore
performance, and still have tape copies for historical needs and D/R. Okay
I hate to agree with Curits that easily, but heck, we can't have everything
we want.
As for the catalog backups, how do you send a copy of the catalog backup
offsite for D/R in case you loose your server and your backup tapes? If
you're doing offsite vaulting of tapes, I suggest you also use Vault to
create an offsite copy of your catalog backup, you'll need it if you ever
have a real disaster. If you're not vaulting tapes offsite, then I wouldn't
worry about the extra catalog backup.
On the topic of expiring the disk images, I would always recommend keeping
them around longer so that can be the primary source for your restores.
Doing a single-file restore from a disk image would be significantly faster
than from tape. And yes, I believe the tape copy would become the primary
copy when the disk image is expired.
-----Original Message-----
From: Jeff Kennedy [mailto:jlkennedy AT amcc DOT com]
Sent: Thursday, August 15, 2002 7:47 AM
To: NBU List
Subject: [Veritas-bu] disk stu and Vault
I want to get some opinions on whether or not this is a good idea and if
I'm going about it correctly.
I am backing up to a disk stu attached to master server. I will use
Vault to duplicate the images from disk to tape and have the disk images
expire after 48 hours. I created a vault and profile that duplicates to
the NetBackup pool using 3 drives and making these the primary copy,
skips the catalogue backup step, and e-mails reports that don't require
media to be ejected.
Do I need the catalogue backup step? I am assuming that the catalogue
will get backed up after each successfull scheduled backup (that's how
it's configured) and didn't want NBDB_Backups or Datastore pools to get
full; especially since these are staying in the library.
Should I change the disk expiration to 120 hours and leave it as primary
for near-term restore performance? If so, will the duplicates
automatically be promoted when the disk images expire?
Does anyone see a problem with this setup? Is anyone using disk stu's
with Vault currently?
Thanks.
--
=====================
Jeff Kennedy
Unix Administrator
AMCC
jlkennedy AT amcc DOT com
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------------------------------------------------------------------------------
This email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else,
unless expressly approved by the sender or an authorized addressee, is
unauthorized.
If you are not the intended recipient, any disclosure, copying, distribution or
any action omitted or taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error, please
contact the sender, delete this e-mail and destroy all copies.
==============================================================================
------_=_NextPart_001_01C24475.3F275580
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.45">
<TITLE>RE: [Veritas-bu] disk stu and Vault</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Jeff,</FONT>
</P>
<P><FONT SIZE=3D2>This is something very similar to what Curtis Preston =
talked about at Vision...I think it's an excellent way to achieve maximum =
backup and restore performance, and still have tape copies for historical =
needs and D/R. Okay I hate to agree with Curits that easily, but heck=
,=
we can't have everything we want. </FONT></P>
<P><FONT SIZE=3D2>As for the catalog backups, how do you send a copy of the=
=
catalog backup offsite for D/R in case you loose your server and your backu=
p=
tapes? If you're doing offsite vaulting of tapes, I suggest you also=
=
use Vault to create an offsite copy of your catalog backup, you'll need it =
if you ever have a real disaster. If you're not vaulting tapes =
offsite, then I wouldn't worry about the extra catalog backup.</FONT></P>
<P><FONT SIZE=3D2>On the topic of expiring the disk images, I would always =
recommend keeping them around longer so that can be the primary source for =
your restores. Doing a single-file restore from a disk image would be=
=
significantly faster than from tape. And yes, I believe the tape copy=
=
would become the primary copy when the disk image is expired.</FONT></P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Jeff Kennedy [<A =
HREF=3D"mailto:jlkennedy AT amcc DOT com">mailto:jlkennedy AT amcc DOT
com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, August 15, 2002 7:47 AM</FONT>
<BR><FONT SIZE=3D2>To: NBU List</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] disk stu and Vault</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>I want to get some opinions on whether or not this is a =
good idea and if</FONT>
<BR><FONT SIZE=3D2>I'm going about it correctly.</FONT>
</P>
<P><FONT SIZE=3D2>I am backing up to a disk stu attached to master =
server. I will use</FONT>
<BR><FONT SIZE=3D2>Vault to duplicate the images from disk to tape and have=
=
the disk images</FONT>
<BR><FONT SIZE=3D2>expire after 48 hours. I created a vault and =
profile that duplicates to</FONT>
<BR><FONT SIZE=3D2>the NetBackup pool using 3 drives and making these the =
primary copy,</FONT>
<BR><FONT SIZE=3D2>skips the catalogue backup step, and e-mails reports tha=
t=
don't require</FONT>
<BR><FONT SIZE=3D2>media to be ejected.</FONT>
</P>
<P><FONT SIZE=3D2>Do I need the catalogue backup step? I am assuming =
that the catalogue</FONT>
<BR><FONT SIZE=3D2>will get backed up after each successfull scheduled =
backup (that's how</FONT>
<BR><FONT SIZE=3D2>it's configured) and didn't want NBDB_Backups or =
Datastore pools to get</FONT>
<BR><FONT SIZE=3D2>full; especially since these are staying in the =
library.</FONT>
</P>
<P><FONT SIZE=3D2>Should I change the disk expiration to 120 hours and leav=
e=
it as primary</FONT>
<BR><FONT SIZE=3D2>for near-term restore performance? If so, will the=
=
duplicates</FONT>
<BR><FONT SIZE=3D2>automatically be promoted when the disk images =
expire?</FONT>
</P>
<P><FONT SIZE=3D2>Does anyone see a problem with this setup? Is anyon=
e=
using disk stu's</FONT>
<BR><FONT SIZE=3D2>with Vault currently?</FONT>
</P>
<P><FONT SIZE=3D2>Thanks.</FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</F=
ONT>
<BR><FONT SIZE=3D2>Jeff Kennedy</FONT>
<BR><FONT SIZE=3D2>Unix Administrator</FONT>
<BR><FONT SIZE=3D2>AMCC</FONT>
<BR><FONT SIZE=3D2>jlkennedy AT amcc DOT com</FONT>
<BR><FONT SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu=
</A></FONT>
</P>
</BODY>
</HTML>
<P>------------------------------------------------------------------------=
------<br>
<br>
<br>
This email is confidential and may be legally privileged.<br>
<br>
It is intended solely for the addressee. Access to this email by anyone =
else, unless expressly approved by the sender or an authorized addressee, i=
s=
unauthorized.<br>
<br>
If you are not the intended recipient, any disclosure, copying, distributio=
n=
or any action omitted or taken in reliance on it, is prohibited and may be=
=
unlawful. If you believe that you have received this email in error, please=
=
contact the sender, delete this e-mail and destroy all copies.<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
</P>
------_=_NextPart_001_01C24475.3F275580--
|
