Ah yes... I remember from v3 days that the block checksums were
appended to the pool files...
Craig Barratt via BackupPC-users wrote at about 21:28:49 -0700 on Sunday, June
7, 2020:
> Jeff,
>
> Yes, that's correct.
>
> In v4 a full backup using --checksum will compare all the metadata and
Jeff,
Yes, that's correct.
In v4 a full backup using --checksum will compare all the metadata and
full-file checksum. Any file that matches all those will be presumed
unchanged. In v4 the server load for a full is very low, since all that
meta data (including the full-file checksum) is stored a
Silly me... the '--checksum' is only for 'Full' so that explains the
difference between 'incrementals' and 'fulls'... along with presumably
why my case wasn't caught by an incremental.
I still don't fully understand the comment referencing V3 and replacing
--checksum with --ignore-times.
Is the p
Can someone clarify how --checksum works in v4?
And specifically, when could it get 'fooled' thinking 2 files are
identical when they really aren't...
According to config.pl:
The --checksum argument causes the client to send full-file
checksum for every file (meaning the client reads every
