Thanks for your unvaluable help Machiel.

I've read your previous topic and effectively it explains the really 
strange behavior of bacula regarding retention parameters :-(

But honestly I think this behavior can be considered as a BUG/PROBLEM, 
cause a situation with a ONE host (= ONE client) with different backup 
types each one with its own retention parameters (TIPICALLY MEANING A 
POOL FOR EVERY BACKUP TYPE) can be considered as normal/usual, and the 
"workaround" of defining for each host different bacula clients (each 
one with its retention parameters) can't be considered the right way.

So...A MESSAGE FOR BACULA DEVELOPERS:

Please correct the bacula behavior using retention parameters.
According the actual features of bacula and (logically) the 
documentation, the right/normal/logical/expected behavior of retention 
parameters (at least from user perspective) would be:
    1- retention parameters defined in CLIENT resource:
         * they must be applied to ALL JOBS of the client, no matter the 
pool they used
    2- retention parameters defined in POOL resource:
         * they must be applied ONLY to jobs of the client using ONLY 
THIS POOL, and never affect jobs in other pools

Another option would be allow retention parameters ONLY in the client 
resource and NOT in the pool resource (updating the documentacion 
accordingly), but I think this would be the wrong way, causing bacula to 
loose functionality and a good feature.

Perhaps are you working on this yet?
Thanks in advance.


El 10/06/10 16:13, Machiel van Veen escribió:
> On Thursday 10 June 2010 03:24:18 pm Area de Sistemas wrote:
>
>> Perhaps a Bacula bug?
>> Perhaps I don't understand the behaviour of retention parameters (I
>> think this is less probable cause the problem appears to affect only
>> some clients/copies)?
>>
>> Any ideas?
>>
>> Thanks in advance.
>>
>>
> It seems you have another job for this client writing to a different pool with
> retention times set in the client directive. When this job runs it wil prune
> all jobs for the client. Regardless of any file or job retention periods set
> in pool directives.
>
> The solution would be to create new client directives for every retention
> period you need and not put them in the pool directive as you do now.
>
> I found this out the hard way too, if you look for the topic "Pool file/job
> retention not updating" you should find my thread on this.
>
> Machiel.
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users