Hi,
I've a setup where bacula has executed the following bacula jobs:
- job X, record SQL in table "Job":
Job: system.2014-01-15_10.24.38_16
Name: system
Type: B
ClientId: 205
PoolId: 60 (pool_on_disk)
PriorJobId: 0
- administrative copy job Y of the job X, record SQL in table "Job":
Job: copyjob.2014-01-15_10.25.40_18
Name: copyjob
Type: c
ClientId: 26 (fake client None for copyjob, from documentation)
PoolId: 13 (pool_on_tape)
PriorJobId: 0
- copy job Z of the job X (executed by administrative copy
job Y), record SQL in table "Job":
Job: system.2014-01-15_10.25.41_19
Name: system
Type: C
ClientId: 205
PoolId: 13 (pool_on_tape)
PriorJobId: X
After the Job Retention period (in our case 40 days), job X and
related files are pruned by DB.
After the Copy Job Retention period (in our case 60 days), job Y and
related files (none) are pruned by DB.
Job Z and related files are not pruned from catalog anymore, because the
pruning algorithm search:
- first time (after 40 days) for Job with ClientId 205 and PoolId 60
- second time (after 60 days) for Job with ClientId 26 and PoolId 13
I know that one possible solution is to have one copyjob per client, but is
very different from documentation and from our setup.
A workaround is to execute a batch script to run "prune jobs client=<name>"
in bconsole for each client.
Do you have suggestions?
Thanks
--
Davide Belloni
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
