dan wrote:
> i understand that unison uses the same algorythm but does it have the same
> memory issues when transfering a lot of files?
There is a small issue with the number of files in that the whole
directory listing is tranferred and held in memory during the
comparison, but the real problem is the number of hardlinks since the
only way to re-create them is to keep a table of inode number and
existing names, then search it for every new file with more than one link.
> alternatively i think i may just break rsync up into smaller jobs and sync
> each specific directory seperately with a 'for x in 'ls /'; do rsync $x
> rsyncd://serveraddress/' script. that would help limit the number of files
> in each rsync interation and work around the memory usage issue. i may have
> to go a step further and omit the backuppc archive directory and run another
> 'for x' script in the top of the hosts directory so i would launch a
> seperate rsync for each host.
Rsync can't re-create the hardlinks unless the entire set is covered in
one job. I think there is another tool now that lets you copy the pool
in one job and the pc directories separately, then rebuilds the links
after the copy, but I haven't tried it that way.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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/
