Hi,

26.08.2008 20:50, John Drescher wrote:
>>>> File Retention = 365d
>>>> Job Retention = 365d
>>>>
>>>> ...
>>>>
>>>> and for the pool:
>>>> ...
>>>> VolumeRetention = 12h
>> It seems to me, that this is wrong, because it makes no sense. Volume
>> retention should be larger as file or job retention. If a volume is
>> purged, any job and file assoziations to the volume were being deleted.
>> Why so you configure file and job retention so big?
>>
> I agree. It really does not make a lot of sense however it will not
> hurt to have these values. The volume retention has priority over file
> and job retention so basically when the volume is recycled all the
> file and job records on that volume are purged at that time.

I disagree :-)

If you have different pools for full, differential, and incremental 
backups with different retention times you end up with complete 
catalog information for all available jobs, but can have - for example 
- monthly full backups going back one year, weekly differentials 
covering eight weeks, and incrementals for the last two weeks. 
Something I like to implement for my customers. And of course I 
believe this does make sense ;-)

Arno


-- 
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users