I should also mentioned you can just replace --checksum in
$Conf{RsyncFullArgsExtra} with --ignore-times if you want the "full"
semantics to closely match 3.x.
In this case, 4.x will have more server load than 3.x since it has to read
all the file contents to get the block checksums, while in 3.x they are
cached at the end of the compressed file. On the other hand, 4.x is
running native C code, and 3.x is mostly in perl, so it's hard to predict
that actual difference.
I don't plan to implement block checksum caching in 4.x since I think
--checksum is a better approach. Also, rsync's 30 generations of protocols
(all backward compatible!) has 3 flavors of block checksums, so supporting
all 3 for older versions is extra work, tricky, and takes a lot more
testing. (3.x had to support two of the three.)
Craig
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
