Drew Tomlinson wrote:
Maria McKinley wrote:
Is it possible the volumes in the pool still have the old retention
period? Have you looked at list volumes to see if it gives you what
you expect? Updating the config file won't change the parameters
already set on existing volumes.
I didn't change the volume retention times in the config file as I set
them as I wished initially. Then when the jobs that used the "Default"
pool (which was set at 100 years) disappeared, I looked into the matter
further. That's when I changed the job and file retention times in my
client resources and SIGHUPed the bacula-dir process. Next I ran bscan
to rebuilt the job and file records. But every night the associated job
and file records still get pruned.
Thanks for your help!
Drew
for one setting something to 100 years could easily hit a number border
somewhere and cause unexpected behaviour
why don't you just turn off auto pruning and set a reasonable retention
period (that is as long as you intend to actually keep your backups)
Florian
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
