Re: [Duplicity-talk] Verify is not working as expected, for me

[Kenneth Loafman]

Hi David,

You are correct, verify by itself only verifies that the current backup can be recovered.  With --data-compare, it will also compare the backup's data against that on the file system.  This is to save time since the compare operation is expensive.

...Thanks,

...Ken

On Fri, Jun 9, 2017 at 3:49 PM, David Williams via Duplicity-talk <address@hidden> wrote:

I've an odd problem, and was hoping someone could shed some light on it.

If I do a "verify" on my backups, I am told "nothing has changed" (even though I have both modified, deleted, and added files). Such as

Verify complete: 53659 files compared, 0 differences found.

If I use --compare-data, though, it appears to be correct, such as

Verify complete: 53659 files compared, 118 differences found.

What exactly is "verify" comparing, if --compare-data is not used?

Could it be related to some "file system" setting I have? (though, I have nothing special, that I know of).

Some cache that needs to be refreshed? (In both cases, duplicity reports "Local and Remote metadata are synchronized, no sync needed.")

Am I misunderstanding "verify"?

BTW, if I do a "status" and everything looks normal, at least to me, with no problems reported.

So far I've only ran with the default verbosity. Guess I'll try bumping that up to see if it reports anything of interest. But, I am a little concerned I am perhaps missing the point of "verify". Perhaps it just checks "database integrity", so to speak?

Thanks for any insights -- both to the issue and/or how to debug it (if it sounds like a bug).

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk