You are correct that autoprune doesn't get rid of Verify jobs.
What is the Level of your Verify jobs? I run VolumeToCatalog Verify jobs but
they never have any files listed by "list files jobid=<jobid>" (just the job
record itself) so I don't understand your comment below.
I work around the autoprune issue by running this SQL command via an Admin
job:
delete from job where (type in ('V', 'D')
or (type = 'B' and jobbytes = 0 and jobfiles = 0))
and starttime < now()-interval '2 months';
It also deletes old Admin jobs and old jobs with no contents.
__Martin
>>>>> On Wed, 4 Nov 2020 17:27:03 +0000 (GMT), Mark Dixon said:
>
> Hi all,
>
> I use bacula to backup my data, but also find verify jobs to be extremely
> useful.
>
> However, after checking my bacula database, I noticed that none of the old
> verify jobs have been pruned, which is making the catalog quite big.
> Actual backup jobs are happily being automatically pruned.
>
> As verify jobs do not use a storage pool, I guess the only relevant
> parameters are in the director's client resource. So I have this:
>
> Client {
> Name = foo
> Address = foo
> FDPort = 9102
> Catalog = MyCatalog
> Password = "bar"
> File Retention = 60 days # 60 days
> Job Retention = 6 months # six months
> AutoPrune = yes # Prune expired Jobs/Files
> SD Calls Client = yes
> }
>
> And yet I can see verify jobs going way back further than 6 months - and
> "list files jobid=<jobid>" shows me every file.
>
> A "prune client=foo jobs yes" seems to do the trick.
>
> Are they supposed to be automatically pruned?
>
> Thanks,
>
> Mark
>
>
> _______________________________________________
> Bacula-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
