Note that if you're using Vault 4.5, this is a built-in feature:

see p.58 of the vault 4.5 sysadmin guide 
(http://seer.support.veritas.com/246838.htm)

It's basically a checkbox in the vault profile's "duplication" tab 
that says "expire disk originals after ___ hours"

hth
rob


At 7:46 AM -0700 8/15/02, Jeff Kennedy wrote:
>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