The document stated:
<quote>
We added two new Pool directives, FileRetention and JobRetention, that take
precedence over Client
directives of the same name. It allows you to control the Catalog pruning
algorithm Pool by Pool. For
example, you can decide to increase Retention times for Archive or O Site
Pool.
It seems obvious to us, but apparently not to some users, that given the de
nition above that the Pool File
and Job Retention periods is a global override for the normal Client based
pruning, which means that when
the Job is pruned, the pruning will apply globally to that particular Job.
Currently, there is a bug in the implementation that causes any Pool
retention periods speci ed to apply
to all Pools for that particular Client. Thus we suggest that you avoid
using these two directives until this
implementation problem is corrected.
</quote>
I am wondering whether this was fixed in latest release, or do we have a
plan to fix it. What i refer is : "Currently, there is a bug in the
implementation that causes any Pool retention periods speci ed to apply to
all Pools for that particular Client. Thus we suggest that you avoid using
these two directives until this implementation problem is corrected."
Thx
baculauser
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
