>> 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. > > You can simply set the archived volumes to status "archive" (update > voluume in bconsole).
From what I've read, that means the volumes will not be recycled. But will they still be considered as the base from which an inc/diff backup can be built? As they are to be sent to another continent for safe keeping (I know...) I can't depend on them for restoration. -Ben ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
