On Sat, 30 Jul 2011 18:34:47 +0100, Graham Sparks said:
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
...@hotmail.co.uk
CC: dresche...@gmail.com; bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] FW: Pruning/Purging and Volume Retention
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
On Sun, Jul 31, 2011 at 06:24:11PM +0100, Graham Sparks wrote:
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.
If 'run' is a matter of
thanks for all the help I've been given.
Graham
Date: Sun, 31 Jul 2011 20:29:00 +0200
From: bacula-li...@lihas.de
To: g...@hotmail.co.uk
CC: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] FW: Pruning/Purging and Volume Retention
On Sun, Jul 31, 2011 at 06:24:11PM +0100
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 797: Python Dir JobStart: JobId=797 Client=asus-fd
NumVols=0
29-Jul 22:00
29-Jul 22:00 asus-dir JobId 797: Begin pruning Jobs older than 2 years .
29-Jul 22:00 asus-dir JobId 797: No Jobs found to prune.
29-Jul 22:00 asus-dir JobId 797: Begin pruning Jobs.
29-Jul 22:00 asus-dir JobId 797: No Files found to prune.
29-Jul 22:00 asus-dir JobId 797: End auto prune.
.
Arguably I should just be making sure they all run :)!
Thanks for your help.
Graham
Date: Sat, 30 Jul 2011 12:54:44 -0400
Subject: Re: [Bacula-users] FW: Pruning/Purging and Volume Retention
CC: bacula-users@lists.sourceforge.net
29-Jul 22:00 asus-dir JobId 797: Begin pruning Jobs older
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
