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 case anyway), that would be great for cases where the client may not always be accessible.
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 AT lists.sourceforge DOT net
>
> > 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.
> >
>
> 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 can mark
> them as purged.
>
> John
