Hi Martin.
> File and Job pruning work differently for safety reasons.
>
> Pruning files is always safe, because the job remains on the volume and can
> still be used to restore files.
>
> Pruning jobs is not safe because a volume can be recycled if it has no
> remaining jobs in the catalog.
>
> For safety, Bacula tries to avoid losing all copies of a backup. It will only
> prune a job if it can find a similar Full backup that is newer than the Job
> Retention period. Setting Job Retention = 0 makes this impossible, so nothing
> is pruned.
You say auto pruning of job records considers previous backup jobs.
Hum, surely it should do so.
I run another test to know how auto pruning considers older
job records, but I am a little bit confused about its result.
But maybe I missunderstand something or miss-operated.
I try to think about this problem a little more.
Thanks for your apply.
>>>>>> On Tue, 27 Jul 2010 16:02:01 +0900, Kazuhiro Takenaka said:
>> >
>> > Hi All.
>> >
>> > I am a newbie of Bacula and learning how to set up Bacula's
>> > configuration files and how the directives of these files work.
>> > For this study, I complied the RPMS of Bacula 5.0.2 from source RPM
>> > and installed them in Redhat EL 5.4.
>> >
>> > Now, I am checking File and Job Retention of Client resource.
>> > Both of these directives are explained in "Bacula Main Reference".
>> > The manual gives almost same description to these directives,
>> > but I found them work different when auto pruning runs.
>> >
>> > When File Retention is set to 0 and the same job is performed twice,
>> > auto pruning induced by the 2nd job deletes the file records of the
>> > 1st job.
>> >
>> > But when Job Retention is set to 0, auto pruning induces by the 2nd
>> > job doesn't delete any job record of the 1st job. More than that,
>> > no matter how many times the job runs, no job record is deleted by
>> > auto pruning.
>> >
>> > # It seems that setting 0 to Job Retention is to prohibit auto
>> > # proning for job records.
>> >
>> > The definition of the Client resource for this test is:
>> >
>> > Client {
>> > Name = take104-fd
>> > Address = take104
>> > FDPort = 9102
>> > Catalog = MyCatalog
>> > Password = "@@@@@@@@@@" # password for FileDaemon
>> > File Retention = 1000 seconds
>> > Job Retention = 0 seconds
>> > AutoPrune = yes # Prune expired Jobs/Files
>> > }
>> >
>> > The report about auto pruning showed by "messages" command is:
>> >
>> > 27-Jul 14:51 take104-dir JobId 1: Begin pruning Jobs older than 0 secs.
>> > 27-Jul 14:51 take104-dir JobId 1: No Jobs found to prune.
>> > 27-Jul 14:51 take104-dir JobId 1: Begin pruning Jobs.
>> > 27-Jul 14:51 take104-dir JobId 1: No Files found to prune.
>> > 27-Jul 14:51 take104-dir JobId 1: End auto prune.
>> >
>> > # I tried running the same job five times in a row and
>> > # every run makes the same message.
>> >
>> > Is this a feature of Bacula? Is there any reason for this?
>
> File and Job pruning work differently for safety reasons.
>
> Pruning files is always safe, because the job remains on the volume and can
> still be used to restore files.
>
> Pruning jobs is not safe because a volume can be recycled if it has no
> remaining jobs in the catalog.
>
> For safety, Bacula tries to avoid losing all copies of a backup. It will only
> prune a job if it can find a similar Full backup that is newer than the Job
> Retention period. Setting Job Retention = 0 makes this impossible, so nothing
> is pruned.
>
> __Martin
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
