Menu
▾
▴
[Bacula-bugs] [bacula 0001601]: FIle/Job retention parameters INCORRECTLY APPLIED when defined in Pool resource
|
From: Mantis B. T. <no...@bu...> - 2010-06-29 11:45:45
|
The following issue has been UPDATED. ====================================================================== http://bugs.bacula.org/view.php?id=1601 ====================================================================== Reported By: sistemas Assigned To: ====================================================================== Project: bacula Issue ID: 1601 Category: Director Reproducibility: always Severity: minor Priority: normal Status: closed Resolution: no change required Fixed in Version: ====================================================================== Date Submitted: 2010-06-29 11:11 BST Last Modified: 2010-06-29 12:45 BST ====================================================================== Summary: FIle/Job retention parameters INCORRECTLY APPLIED when defined in Pool resource Description: When the file/job retention periods are defined in the Pool resource (instead in the Client resource), Bacula behavior is incorrect: EXPECTED/SUPPOSED/LOGICAL BEHAVIOR: * When Bacula purges file/jobs entries in catalog: It must delete expired job/file entries according a XXX pool's retention parameters BUT ONLY FROM JOBS DONE IN THIS XXX POOL, *NOT* FROM JOBS DONE IN OTHER POOLS. * Even documentation suggest this behavior. REAL BEHAVIOR (APPARENTLY): * Bacula deletes expired jobs/file entries from jobs DONE IN *ANY* POOL, not only in the pool with the defined retention parameters. * It seems that retention parameters are ALWAYS applied at client level (no matter they were defined at pool or client level), so they always affect ALL client's jobs. RESULT: * Shortest retention parameters are applied to *ALL* pools, so defining different parameters in every pool has no the desired effect. ====================================================================== ---------------------------------------------------------------------- (0005471) ebollengier (administrator) - 2010-06-29 12:44 http://bugs.bacula.org/view.php?id=1601#c5471 ---------------------------------------------------------------------- By default, bacula prunes files according to the client and the pool retention period if specified. If you want to use only pool retention period, you need support to help you to adjust your configuration for this special case (neither professional or community support, see www.bacula.org -> Support) As this part has been rewritten in the 5.0.3 release, please wait a bit and re-open this issue if you still think that it's a bug and you can prove it by real examples when we will release it. Issue History Date Modified Username Field Change ====================================================================== 2010-06-29 11:11 sistemas New Issue 2010-06-29 12:44 ebollengier Note Added: 0005471 2010-06-29 12:44 ebollengier Status new => closed 2010-06-29 12:44 ebollengier Resolution open => fixed 2010-06-29 12:45 ebollengier Resolution fixed => no change required ====================================================================== |