Re: [Bacula-users] (My) Job pruning seems not to work as intended

On 10/23/24 11:51 AM, Justin Case wrote: > Thanks Bill, I got it working with your help. Excellent! That was quick too! :) Glad I could help! Best regards, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature

Re: [Bacula-users] (My) Job pruning seems not to work as intended

Thanks Bill, I got it working with your help. > On 23. Oct 2024, at 19:19, Bill Arlofski wrote: > > On 10/23/24 10:59 AM, Justin Case wrote: >> I used this in an admin job, but no verify/admin jobs older than 6mo got >> deleted: >> Runscript { >> RunsWhen = "Before" >> RunsOnClient =

Re: [Bacula-users] (My) Job pruning seems not to work as intended

On 10/23/24 10:59 AM, Justin Case wrote: I used this in an admin job, but no verify/admin jobs older than 6mo got deleted: Runscript { RunsWhen = "Before" RunsOnClient = no Console = "delete from job where (type in ('V', 'D') or (type = 'B' and jobbytes = 0 and jobfiles = 0))

Re: [Bacula-users] (My) Job pruning seems not to work as intended

I used this in an admin job, but no verify/admin jobs older than 6mo got deleted: Runscript { RunsWhen = "Before" RunsOnClient = no Console = "delete from job where (type in ('V', 'D') or (type = 'B' and jobbytes = 0 and jobfiles = 0)) and starttime < now()-interval '6 months';"

Re: [Bacula-users] (My) Job pruning seems not to work as intended

bob, thank you for you effort to help! Response part (4) was relevant for me. I solved the mystery by now: VOlume sin state Error do not have an expiry date and so the associated jobs also do not get pruned. > On 21. Oct 2024, at 16:08, Rob Gerber wrote: > > Justin, > > I don't have answers t

Re: [Bacula-users] (My) Job pruning seems not to work as intended

Thank you so much Martin, it all makes sense now! regarding (4), the old jobs are on volumes in state Error, those do not have an expiry date. What do you suggest how to proceeds with these? purge the old volumes in Error state and then run a pruning, will that clear out the old jobs? > On 21.

Re: [Bacula-users] (My) Job pruning seems not to work as intended

Justin, I don't have answers to all your questions (really, to any of your specific questions, anyhow). I do have some thoughts, though. Please keep in mind that compared to many on this list, I'm a bacula novice. I might get something wrong. I also haven't entirely understood the problems you're

Re: [Bacula-users] (My) Job pruning seems not to work as intended

> On Sun, 20 Oct 2024 13:15:16 +0200, Justin Case said: > > I have browsed the catalog database a bit more and I saw one thing that might > explain the problem I am having, but I don't have sufficient technical > background on the Bacula implementation details of different versions. > > I a

Re: [Bacula-users] (My) Job pruning seems not to work as intended

I have browsed the catalog database a bit more and I saw one thing that might explain the problem I am having, but I don't have sufficient technical background on the Bacula implementation details of different versions. I am running bacula-dir 15.0.2 and bacularis 3.1.0. The Bacula manual and B

Re: [Bacula-users] (My) Job pruning seems not to work as intended

Hi Bill, please find my response inline below: > On 19. Oct 2024, at 22:59, Bill Arlofski wrote: > > On Wednesday, October 16th, 2024 at 06:15, Justin Case > wrote: > >> I am wondering why I am seeing in my catalog lots of jobs older than the >> JobRetention defi

Re: [Bacula-users] (My) Job pruning seems not to work as intended

On Wednesday, October 16th, 2024 at 06:15, Justin Case 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 adheri

Re: [Bacula-users] (My) Job pruning seems not to work as intended

Yes Martin, I do see these messages. less than every other message it tells me that it has deleted jobs, mostly just 1 job, sometimes 3, very seldomly 4 jobs. It doesn’t tell me which jobs it has deleted though. At the same time it tells me it has upgraded the same number of Copy jobs to Backup

Re: [Bacula-users] (My) Job pruning seems not to work as intended

Messages like "Begin pruning Jobs older than ..." should appear after the termination status of the job. Do you see any messages like that? __Martin > On Wed, 16 Oct 2024 14:15:24 +0200, Justin Case said: > > I am wondering why I am seeing in my catalog lots of jobs older than the > JobRe

[Bacula-users] (My) Job pruning seems not to work as intended

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, probabl