Author: Martin Simmons <martin AT lispworks DOT com>
Date: Mon, 1 Aug 2011 12:05:52 +0100
I think this is fixed in the development branch (for the next release). In 5.0.x, it prunes everything related to the client that was used in the job. __Martin -- Got Input? Slashdot Needs You. Take
This is the output I get after a job has completed. The lines at the end suggest job pruning--does the auto prune not also trigger the purging and recycling? Thanks. -- 29-Jul 22:00 asus-dir JobId 79
Author: John Drescher <drescherjm AT gmail DOT com>
Date: Sat, 30 Jul 2011 12:54:44 -0400
This would prune Job records (for any pool). Then file records (again for any pool). I assume at this point if it finds any volumes that do not contain any jobs (because of the job/ file pruning) it
Many thanks John. 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
Author: Konstantin Khomoutov <flatworm AT users.sourceforge DOT net>
Date: Sat, 30 Jul 2011 23:07:51 +0400
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 i
Thanks for that advise. I'll adjust the retentions and see if I can achieve what you described. Provided I make sure the full backups definitely run every month, this should be an adequate solution.
Author: Adrian Reyer <bacula-lists AT lihas DOT de>
Date: Sun, 31 Jul 2011 20:29:00 +0200
If 'run' is a matter of hosts being reachable, you might consider VirtualFull backups. Regards, Adrian -- LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart Fon: +49 (7 11) 78 28 50 90
Yes--I must look at virtual full backups in more detail. I remember thinking that they'll save some time at the weekends if I replaced the fulls. I've had another look at volume retention and I think