This is not yet for offsite vaulting; currently I just want to get the
images off of disk and onto tape successfully, then I'll worry about
offsite.  The primary reason for this exercise is to use the disk stu
for speed of backups and near-term (less than a week) restores, then use
Vault to move images from disk to tape.  After the disk images expire
the tapes would be the primary restore candidates.

Once all that is successfull I will start dup'ing for Offsite as well. 
This will involve a new profile (if not an entirely new vault due to
different media type for offsite) and new pools as well as catalogue
dup's.  But until the first part is good to go I'm still doing a second
full for offsite.

~JK

> "White, Steve" wrote:
> 
> 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.
> 
> ==============================================================================

-- 
=====================
Jeff Kennedy
Unix Administrator
AMCC
jlkennedy AT amcc DOT com