On Thu, Feb 7, 2013 at 4:01 AM, Tyler J. Wagner <tyler AT tolaris DOT com> 
wrote:
> >> Elapsed (wall clock) time (h:mm:ss or m:ss): 10:17.32
>>
>> Output from the BPC-server (/bak):
>> User time (seconds): 228.31
>> Elapsed (wall clock) time (h:mm:ss or m:ss): 14:39:44
>>
>> According to
>> <<http://linux.about.com/od/commands/a/Example-Uses-Of-The-Command-Time.htm>>,
>> the wall clock indicates how long the process run would take. With that in
>> mind, the backup from the client should take about ten minutes. This is
>> clearly not so according to the BPC logs.
>
> This indicates that I was wrong; directory/inode traversal is not the
> issue. It's speedy enough to run the test. It is likely in the rsync block
> checksum comparison after all.

How does this time compare to an incremental where few/no files
actually change?  You should only do the checksum comparison on fulls
or files where the directory timestamp/length differ on incrementals.
  If there is an extreme difference, maybe you are out of available
RAM and pushing the server or target into swap with the size of the
directory contents.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
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/