On Sat, Jul 30, 2011 at 06:34:47PM +0100, Graham Sparks wrote: > It's a real shame that the pruning takes effect across pools. If it > only affected volumes in the same pool as the job, and didn't happen > if the job failed (I think the latter's the case anyway), that would > be great for cases where the client may not always be accessible. Well, I think I see this situation from a different angle. Job/file retention period is supposed to keep your catalog from overgrowing, but there are other ways of pruning job and file records. For instance, you can set job/file retention periods for your client higher than the volume retention period on the pool(s) used to back up that client--in this case the file/job records will only be pruned when Bacula will "expire" a volume in a pool, when needed. If you're backing up to a pool with a fixed number of voulmes, you can even set the Purge Oldest Volume = yes on that pool which will unconditionally zap file/job records bound to the oldest volume in the pool when Bacula will need a fresh one. If job/file retention periods for your client will be greater than a typical lifetime of a volume in the pool this client is backed up to, the lifetime of the file/job records will be effectively controlled by expiration of the volumes in that pool.
------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
