I guess I don’t understand how verify jobs work at level Data with Accurate=yes.

When scheduled, the verify level=data and accurate=yes job runs well after the 
backup job, but returns with differences, but not showing which files have 
differences.
When run again manually, the same happens.

When running the backup job (incremental) again, and after that the verify job, 
I will also get differences, but now it shows which files are causing them!
That are literally a few hundred! But all of them are some caches, database 
files of macOS, Firefox, etc.

This is kinda puzzling me as I thought that Level=Data does not access the 
client FD, but with Accurate=yes it seems to do that.
I thought this compares the data in the volumes to the metadata in the catalog 
(as opposed to to the files as seen by the client FD). 
If that was the case, how could those differences occur?
And how could they be so numerous, even though I am running the verify job 
right after the backup job?

So I ran a Level=VolumeToCatalog verify and no differences found.
Then I ran a Level=DiskToCatalog verify and voila lots and lots of differences.

Could it be that Level=Data with Accurate=yes does NOT encompass 
VolumeToCatalog (as per the documentation), but really encompasses 
DiskToCatalog (which would be uncalled for, really)?

That still doesn’t answer why the scheduled verify jobs didn’t display the 
files that had the differences as opposed to the manually run verify jobs, 
which did show the files with differences.

Really, what is going on here? Is nobody else using this and wondering? Did I 
get it all wrong?

> On 9. Sep 2022, at 02:25, Justin Case <jus7inc...@gmail.com> wrote:
> 
> Finally 8 of 15 verify jobs returned with differences. I did not have this 
> before when I was only using level Data and not Accurate.
> How can I investigate teh root cause of this?
> 
> What seems counter intuitive to me is that all verify jobs are marked as OK, 
> also those that returned with differences. 
> I guess this means the verify job ran completely and has no relation to 
> potential differences being found.
> 
>> On 9. Sep 2022, at 01:23, Justin Case <jus7inc...@gmail.com> wrote:
>> 
>> Hello all,
>> a disk backup verify with level Data and with Accurate just returned with
>> FD termination status:  Verify differences
>> 
>> However, the job info and the email that was sent about it does not contain 
>> any further information on what file is exhibiting differences. Is it 
>> possible to investigate further? I would be interested which files are 
>> showing difference. I did not find any console commands that seemed suitable 
>> for that.
>> 
>> Another thing that caught my attention is this:
>> bacula-dir JobId 2753: Sending Accurate information to the FD.
>> 
>> I was thinking that Data level verify does not involve the client FD. Does 
>> Accurate cause Data level verify to involve the client FD? If that is the 
>> case it would explain the verify differences, as that client is macOS and 
>> has a lot of files that change frequently.
>> 
>> Thanks for your interest,
>> J/C
>> 
>> 
>> 
>> 
> 



_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to