Thanks Martin. The implication seems to be that it is not therefore feasible to schedule a disktocatalog verify job.
It can only be run interactively through bconsole. Is that right? Regards Chris Wilkinson On Wed, 6 Mar 2019, 2:35 p.m. Martin Simmons, <mar...@lispworks.com> wrote: > >>>>> On Wed, 27 Feb 2019 22:57:34 +0000, Chris Wilkinson said: > > > > In my setup I use a single pool for incr/diff/full backup running on a > > typical daily/weekly/monthly schedule. I would like to add a > disktocatalog > > verify job since I've been having intermittent disk problems. > > > > It appears from the manual that the last backup that ran (presumably with > > status Term. OK) is used to verify against. The relevant directive seems > to > > be "verifyjob=name". That may be any of incr/diff/full. > > > > There doesn't appear to be a directive to specify the level to be > selected > > for verification. If there were separate pools for incr/diff/full the > > "pool=..." directive would suffice but I don't have that configuration. > > No, "pool=..." will not even work in that configuration I think. > > > > Could anyone clarify the directive needed to ensure that verification is > > performed against a full backup when using a single backup pool? > > The bconsole run command takes a "jobid=..." argument that will force it to > verify against that jobid. There is no equivalent for use in > bacula-dir.conf > though. > > __Martin >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
