SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
verify job fails, must init catalog run twice?
Author Message
Post verify job fails, must init catalog run twice? 
Hello,

I see this for quite a while now and it does not seem to disappear with=20
2.0.1... maybe someone has the same problem?

yesterday I was upgrading my system and ran a "InitCatalog" manually=20
thereafter. This morning my regular verify job failed with reporting that=20
some hundred files have changed (all in /lib, /sbin and /usr - stuff update=
d=20
by rpm).

2007-03-13 08:37:11 bender.in.oldnewyork: verify-bender.2007-03-13_08.30.00
[...]
Error: Bacula 2.0.1 (12Jan07): 13-Mar-2007 08:37:11
=C2=A0 JobId: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0183
=C2=A0 Job: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0verify-bender.2007-03-13_08.30.00
=C2=A0 FileSet: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0veri=
fy-bender
=C2=A0 Verify Level: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Catalog
=C2=A0 Client: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 bend=
er-verify
=C2=A0 Verify JobId: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 182
=C2=A0 Verify Job: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=20
=C2=A0 Start time: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 13-Mar-2007 08=
:30:02
=C2=A0 End time: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 13-Mar-20=
07 08:37:11
=C2=A0 Files Examined: =C2=A0 =C2=A0 =C2=A0 =C2=A0 49,803
=C2=A0 Non-fatal FD errors: =C2=A0 =C2=A00
=C2=A0 FD termination status: =C2=A0OK
=C2=A0 Termination: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*** Verify Err=
or ***

now I repeated the very same procedure: manual "InitCatalog" job, then the=
=20
regular (but this time manually started) verify job. This time it went OK. =
No=20
differences found. I bet that tomorrows automatic verify job will also=20
terminate OK as that is what always happened previously.

13-Mar 11:45 bender.in.oldnewyork: Bacula 2.0.1 (12Jan07): 13-Mar-2007=20
11:45:19
JobId: 185
Job: verify-bender.2007-03-13_11.38.07
FileSet: verify-bender
Verify Level: Catalog
Client: bender-verify
Verify JobId: 184
Verify Job:
Start time: 13-Mar-2007 11:38:09
End time: 13-Mar-2007 11:45:19
Files Examined: 49,803
Non-fatal FD errors: 0
FD termination status: OK
Termination: Verify OK

to me it looks like InitCatalog must run twice before all changes are known=
=20
and the regular verify behaves the way it should.

(note: I have not done any changes to the system between the two jobs and a=
uto=20
update is disabled. I am not running a virus scanner or anything else that=
=20
could touch the files).

regards,
Stephan

PS: i can post the complete bconsole conversations and/or config if needed

Post verify job fails, must init catalog run twice? 
to me it looks like InitCatalog must run twice before all changes are known
and the regular verify behaves the way it should.

(note: I have not done any changes to the system between the two jobs and
auto update is disabled. I am not running a virus scanner or anything else
that could touch the files).

one more addition: the "special" thing on my setup is that its using *two*
catalogs. One for backup jobs, one for verify jobs. Could that confuse
bacula?

Stephan

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB