On Wed, Jan 5, 2011 at 12:06 PM, Ben Beuchler <ins...@gmail.com> wrote: > Once a year, I need to create a full backup that will be stored > off-site. This backup will not be readily available for normal > restores. The obvious approach would be to delete that backup (and > its volumes) from the catalog so they will not be considered when > performing future backups/restores. > > Is there a better approach? This seems rather clumsy. >
I create a duplicate job that has the same fileset. This job goes to an archive pool that does not recycle. John ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
