Andy Thompson wrote at about 13:40:28 -0500 on Tuesday, December 8, 2009: > I want to convert a host from rsync to rsyncd in order to test speed > differences between the two. My concern though is that currently with rsync > my share name is /, which don't believe is valid using rsyncd. If I do > this, will it duplicate all of the data for this server since they are > different share/path names? It's a couple hundred gig of data and I don't > really want it duplicated for any amount of time
While others have correctly pointed out that you won't incur a *storage* penalty due to the magic of pooling, you will have a bandwidth/transfer penalty since the files will still need to be transferred to be compared to the pool. That being said, I don't think "/" will pose a problem since BackupPC saves the rsync "/" share name as "f%2f" (mangled form) which is equivalent to an unmangled "%2f" share name which probably is allowed in rsyncd. So just call the equivalent rsyncd share name "%2f". I haven't tested this, so I may be missing something, but try it... The only potential problem is that the share-level attrib file (sitting in TopDir/pc/<machine name>/<backup number> will label reference the share name as "/" for rsync and as "%2f" for rsyncd but I don't think that will matter since they should be treated equivalently internally.. but again test... If this causes problems, one could write a simple routine to just change that single attrib line. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ 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/
