Joe Krahn wrote:
> Rsync is a high quality tool, but I was surprised to learn how poorly
> the hardlink preservation is handled. It keeps a list of inodes for ALL
> files, not just ones with outstanding hardlink counts. The good news is
> that plans for rsync 3.0 include fixing this. This could be even more
> efficient by tracking the senders inode instead of file names, with the
> receiver keeping a remote-to-local inode lookup table. I don't know what
> the current development version actually does. Maybe someone here facing
> backup mirroring problems could try out an rsync-3 pre-release.
That's not going to make a huge difference in terms of handling a
backuppc archive since every file in the cpool and pc directories will
have at least 2 links and thus have to be included in the table.
Mapping local to remote inodes would greatly widen the already present
window where wrong things can happen if the filesystems are active while
being copied.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
