ehar...@lyricsemiconductors.com wrote:
I thought rsync, would calculate checksums of large files that have
changed timestamps or filesizes, and send only the chunks which
changed. Is this not correct? My goal is to come up with a
reasonable (fast and efficient) way for me to daily incrementally
backup my Parallels virtual machine (a directory structure containing
mostly small files, and one 20G file)
I’m on OSX 10.5, using rsync 2.6.9, and the destination machine has
the same versions. I configured ssh keys, and this is my result:
Upgrade to rsync 3 at least.
Rsync keeps a hash of the blocks of sliding hashes. For older versions
of rsync, the has was of a constant size. This meant that files over 3GB
in size had a high chance of hash collisions. For a 20G file, the
collisions alone might be the cause of your trouble.
Newer rsyncs detect when the hash gets too big, and increase the has
size accordingly, thus avoiding the collisions.
In other words - upgrade both sides (but specifically the sender).
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
