-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Wednesday 2007-04-25 at 16:36 -0400, Greg Freemyer wrote:
> Neither of the solutions I posted earlier in this thread are dependent
> on timestamps.
>
> iirc: Especially for online backups rdiff-backup mentioned before
> ignores timestamps altogether. It calculates the MD5 for every file
> to see if any changes have been introduced. If they have it segments
> the file and drills down to find the smallest unit of change and only
> sends that data across the LAN/WAN.
I doubt that.
rdiff-backup is fast, and calculating MD5 for all files is slow. I think
it does that only for files it thinks that might have changed.
Proof:
Backing up my Mail list archive takes 4" right now. Calculating the
md5sums of one of the same dir takes 47" (37" on a second run).
Therefore, rdif. must be checking metadata instead.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFGMJV2tTMYHG2NR9URAs6tAJ9pAmBnG5E2WfuvpEEEP0vcaCIVrQCgjdfR
Pwgs598jtSrAImJekaKQMBQ=
=x6IY
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
