Hi Martin,
Thanks for the reply, glad to know that it's not just me. They're
InitCatalog Verify jobs. Going to SQL feels a bit hairy, as we'd have to
be careful to cascade the delete to at least the File and Log tables.
As prune (unfortunately) only lets you work on a single client at a time,
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=" (just the job
record itself) so I don't understand your comment below.
I work around the autoprune is
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.
