> 
> Not that I know of
> 
> > If I got it right then the file- and job
> > retention is overruled by the volume retention, so I don't see a
> > solution for this problem...
> 
> Consider this...
> 
> Keep File and Job Retention at 3 years.
> 
> Create a new pool with retention 3 years, call it LONGTERM.
> 
> Once a day, run a copy job.  Look for Full backups that are more than
> four weeks old.  Copy such jobs to the LONGTERM pool.
> 
> Then if you wish, have another script which if it sees a newer full in
> the regular pool, it purges the LONGTERM pool.
> 

You could also code up some SQL to push the retention date out to
infinity on the most recent full backup, and reset the retention date on
volumes that not the most recent full backup. Just set it to run on job
completion.

James

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users