Re: (My) Job pruning seems not to work as intended
Justin Case <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Bill, please find my response inline below: > On 19. Oct 2024, at 22:59, Bill Arlofski <[email protected]> wrote: > > On Wednesday, October 16th, 2024 at 06:15, Justin Case <[email protected] <mailto:[email protected]>> wrote: > >> I am wondering why I am seeing in my catalog lots of jobs older than the JobRetention defined in the pools, and also older than the default JobRetention assumed for the clients. >> The volume recycling seems to work fine adhering to the VolumeRetention in the pools. >> > >> To me it is a mystery, probably be cause I overlook some dependencies I am not aware of. >> Can someone please help me understanding this. > > Hello Justin, > > From the rest of this thread, it appears that your prunining is working as configured/expected. I doubt that, at least no as intended. > Where are you seeing the old jobs? bconsole? BWeb? Bacularis? Bacularis. > They could be coming from the `jobhisto` table. > > And you can prove this by querying the `job` and `jobhisto` tables and compare the results. job has all the jobs jobhisto is empty Still sounds to me like job expiry not work as intended - maybe config is wrong, but I don’t understand where the mistake is. You find the config excerpt in my initial post. Can you help? All the best, J/C _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users