Veritas-bu

[Veritas-bu] disk stu and Vault

2002-08-15 12:21:20
Subject: [Veritas-bu] disk stu and Vault
From: Mark.Donaldson AT experianems DOT com (Donaldson, Mark)
Date: Thu, 15 Aug 2002 10:21:20 -0600
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_01C24477.CA2737C0
Content-Type: text/plain

I do this with a homemade system. 

I backup several classes to a disk STU, then I have a cron jobs that uses
bpimmedia to list the images on the disk and duplicate them to tape.  I then
do a query to verify I have a valid tape image.  If it's on tape, then I
manually expire the copy on disk with bpexpdate.

The tape copy then automatically becomes the primary restore image.

If I had more disk, I'd probably change the expiration to be a couple of
days in the future like you're suggesting.  The disk would be a faster, more
convenient restore source.

-M

-----Original Message-----
From: Jeff Kennedy [mailto:jlkennedy AT amcc DOT com]
Sent: Thursday, August 15, 2002 8: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

------_=_NextPart_001_01C24477.CA2737C0
Content-Type: text/html
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=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] disk stu and Vault</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I do this with a homemade system. </FONT>
</P>

<P><FONT SIZE=3D2>I backup several classes to a disk STU, then I have a =
cron jobs that uses bpimmedia to list the images on the disk and =
duplicate them to tape.&nbsp; I then do a query to verify I have a =
valid tape image.&nbsp; If it's on tape, then I manually expire the =
copy on disk with bpexpdate.</FONT></P>

<P><FONT SIZE=3D2>The tape copy then automatically becomes the primary =
restore image.</FONT>
</P>

<P><FONT SIZE=3D2>If I had more disk, I'd probably change the =
expiration to be a couple of days in the future like you're =
suggesting.&nbsp; The disk would be a faster, more convenient restore =
source.</FONT></P>

<P><FONT SIZE=3D2>-M</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 8: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.&nbsp; 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.&nbsp; 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 =
that 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?&nbsp; 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 =
leave it as primary</FONT>
<BR><FONT SIZE=3D2>for near-term restore performance?&nbsp; 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?&nbsp; Is =
anyone 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=
</FONT>
<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&nbsp; -&nbsp; =
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>
------_=_NextPart_001_01C24477.CA2737C0--

<Prev in Thread] Current Thread [Next in Thread>