Jason M. Kusar wrote:
>>
> Ok, that helps explain quite a bit that I was unclear on. So, just to
> make sure I'm absolutely clear, doing a full backup doesn't need to
> transfer all the unchanged files because they still exist in the pool,
> correct?
It's not just that it's in the pool - it must appear in the previous
backup of this PC.
> But how does RsyncP tell that the file is there without
> actually transferring to the system to perform the checksum?
The remote rsync transfers its complete directory listing first, then
the two sides romp through it deciding what has changed. On
incrementals, a match in filename, timestamp, and length is enough to
consider the file the same. On fulls, both ends read the contents and
compare checksums with a complex algorithm to identify and send just the
changes. The backuppc side has to work harder because it is using perl
code and uncompressing the pooled file.
> You
> mentioned something about using rsync with checksum caching, but I
> couldn't find any options for it.
Look at the paragraph containing --checksum-seed=32761 in config.pl. If
you enable it, it will save the work of computing the checksums every time.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
