On Wednesday 18 July 2007 08:18, Ralf Gross wrote: > Ralf Gross schrieb: > > bacula 2.0.3, debian etch amd64, postgres 8.1 > > > > I've added some verify jobs to my configuration. If I start one of > > these jobs by hand it works as expected. But if the job is scheduled > > and started after the regular backup I get the error message > > > > Fatal error: verify.c:273 Unimplemented Verify level 73(I) > > [...] > > Posted too soon. Found a bug report about this problem, which is not > a bug. > > http://bugs.bacula.org/view.php?id=1http://bugs.bacula.org/view.php?id=1 > > quote: > Most likely you have a Schedule Run "level" override that is forcing > the level to Incremental. > > > That's the case here. I think the only solution will be adding a > different schedule which is not changing the level. > > Ralf Coincidentally, I also ran into this today. The pitfall, I think, is to re-use the backup schedule (complete with Level directives) for use with the verification job and without realising that the Level directives there will override the verify level.
I suspect lots of us have done this. Perhaps there is an opportunity to trap this in the (most excellent) manual? Steve
pgp9PxOsWpevc.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
