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
Drew Tomlinson wrote:
Maria Mckinley wrote:
From the manual under pool resource:
The Volume Retention applied independently to the Job Retention and
the File Retention periods defined in the Client resource. This
means that the shorter period is the one that applies. Note, that
when the Volume Retention period has been reached, and it is
necessary to obtain a new volume, Bacula will prune both the Job and
the File records.
The first sentence isn't really a complete sentences, so I'm not
really sure what it is trying to say. However, I think the quote as
a whole means that if you have a job or a client resource that you
are backing up using this pool, and if more than one of these
resources has a volume retention time, then bacula will use the
smallest of these retention times. You didn't include your job
resources, but I assume that this is where you will find the
conflict in retention times.
hope someone corrects me if I read this wrong...
Thank you for your reply.
Yes, I read the part under pool resource which led me to checking the
client resources (which have a default retention period of 60 days)
and changing them to 100 years. However I have just re-read the job
resource section and am unable to find any references to job
retention times. Did you find something there?
I'm still lost. Help!!! :)
Thanks,
Drew
Drew Tomlinson wrote:
I would like to prune based on the volume retention I set in pool
resources, not based upon client. In reading the docs, I found
that auto pruning can occur based on statements in both the client
and pool resources. Thus I set all of my client resources file and
job retention times to 100 years, assuming this would prevent any
auto pruning from occurring based upon the clients. Then I set my
various pool resources volume retention times as I wished.
However I have one pool "Default" that I really don't want to prune
automatically and thus I set its volume retention time to 100
years. I assume it's associated job (and thus file?) records were
pruned initially because of the 60 default retention times for
clients. Now I've made the changes to bacula-dir.conf and SIGHUPed
the process. But after running bscan to rebuild the job and file
records, it still gets pruned every night.
Can someone explain what I'm missing? Hopefully before tonight?
:) The client and pool resource portions of my bacula-dir.conf
file follow.
Thanks,
Drew
[snipped bacula-dir.conf as this thread is getting kind of long]
-------------------------------------------------------
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
