Evren Yurtesen wrote:
>> 1.) Rsync checksums are not a feature of BackupPC. They are a feature of the
>> rsync protocol.
>
> BackupPC compares files in the pool using the checksum to find if the exact
> same
> file is in the pool or not. This is not a feature of rsync.
I think you are confusing 2 different things here. When backuppc
transfers in a new file, it computes a hash of some portion of the file
to use as the pool filename and a quick check to see if there is already
a match in the pool. However, this is not done during the rsync
comparison. Rsync just follows the links in the per-pc backup directory
of the last full. Any name not matched from there is transferred in
full, then matched or added to the pool with the filename hashing step.
I just thought of one other thing that might make your transfers appear
to be very slow. Do you happen to have any very large sparse files (dbm
type) on the target machines? For example, a 64-bit linux machine that
uses -1 as the nfsnobody uid will have a 1.2TB /var/log/lastlog
containing only a few blocks of data. While backuppc will compress this
to something small in the archive, rsync and tar don't handle the
transfer very well and it is a good idea to exclude it.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
