On 2/3/2011 11:33 AM, Carl Wilhelm Soderstrom wrote:
> On 02/03 04:37 , John Goerzen wrote:
>> Transferring it using rsync directly takes 13 minutes.  And it has rsync at
>> about 85% CPU usage instead of 99%.
>
> Sounds like you're running into the fact that BackupPC doesn't actually use
> 'real' rsync at both ends of the connection. It has a perl implementation of
> rsync on the server side and only uses the regular rsync package on the
> client side.

And worse for performance, on the server side it has to uncompress the 
copy to compute the block checksums unless you have enabled checksum 
caching and the file hasn't changed for two runs (maybe two fulls).
When there is a mismatch, the server side has to reconstruct a full copy 
of the original, merging any uncompressed matching blocks with the 
differences from the remote.  Unless you have limited bandwidth, this is 
usually much slower than a full new copy would be.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/