On Fri, Oct 27, 2017 at 9:31 AM, Bzzzz <lazyvi...@gmx.com> wrote:
>
> Correction (as often,I read much too fast):
>
>> This i going against: "I don't think so, because on incrementals BPC
>> doesn't use "--checksum" at all." (v.4.x doc):
>
> The doc doesn't speak about incrementals (only fulls), but to be sure
> about this, you should look at rsync_bpc source.
>
The default for rsync is to quickly skip any files where the timestamp
and length match the existing copy. v3 used --ignore-times on full
runs to go through the motions of transferring by comparing block
checksums and transferring any differences. --checksum is similar but
uses a single checksum over the whole file. I thought in v4 this
mechanism is also related to the ability to match copied, moved or
renamed files to existing matching content in the pool, so removing it
might be a bad idea aside from eliminating the check for corruption or
changes in content that don't update the directory/inode.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
