Jeffrey J. Kosowsky wrote at about 13:07:42 -0400 on Monday, October 27, 2008:
 > To summarize, I have been having problems backing up my Windows
 > machine under cygwin rsync/ssh.
 > 
 > Initially, I thought the problem was a cygwin rsync/ssh problem so I
 > updated my Windows rsync to version 3.0.4 (protocol 30). This allowed
 > me to get backup working under 'rysncd' but running 'rsync' caused
 > both backuppc and a manual running of rsync to hang after downloading
 > only a handful of files. Since even running rsync alone (without
 > backuppc) failed, I assumed the problem was a pure rsync/ssh/cygwin
 > one.
 > 
 > I then decided to try upgrading my Linux rsyncd from 2.6.9 (protocol
 > 28) to 3.0.4 (protocol 30) and now running 'rsync' manually worked but
 > running backuppc still hung leading me to suspect a problem in
 > backuppc.
 > 
 > Specifically, I tried to use almost identical commands when running
 > rsync from the command line vs. the command run by BackupPC_dump.
 > 
 > BackupPC_dump runs:
 >      /usr/bin/ssh -q -x -l mnyname hostmachine /usr/bin/rsync
 >      --server --sender --numeric-ids --perms --owner --group -D --links
 >      --hard-links --times --block-size=2048 --recursive
 >      --checksum-seed=32761 --one-file-system --omit-dir-times . /c/
 > 
 > which hangs after downloading about 8 files... (the same problem I was
 > having before when I was using rysnc-2.6.9)
 > 
 > While I ran:
 >      sudo -u backuppc /usr/bin/rsync -e "ssh -l myname" --numeric-ids
 >      --perms --owner --group -D      --links --hard-links --times
 >      --block-size=2048 --recursive   --one-file-system --omit-dir-times
 >      -vv winsurgeon:/c/ . 
 >  
 > seems to run clean.
 > 
 > Now, the verbose output of BackupPC_dump shows:
 >              Got remote protocol 30
 >              Negotiated protocol version 28
 > while the extra extra verbose output of running rsync manually shows:
 >        (Client) Protocol versions: remote=30, negotiated=30
 >        receiving incremental file list
 >        (Server) Protocol versions: remote=30, negotiated=30
 > 
 > I SUSPECT the problem may be due to perl-File-RsyncP which reportedly
 > only uses protocol 28 while rsync-3.0.4 uses protocol 30. If so,
 > perhaps the reason that the rsyncd method works is that it bypasses
 > such portions of perl-File-RsyncP that cause the problem.
 > 
 > If true, perhaps a lot of the problems with backing up Windows machines
 > could be cleaned up by upgrading perl-File-RsyncP to protocol 30.
 > 
 > IF so, is there any way to update the perl library? (I noticed that
 > Craig is also the author of it)
 > 

Just to add some more confirmation, adding "--protocol=28" to the
command line of the manual rsync command causes it to hang too.

Also, it seems that at least one of the issues with protocol 28 is
that it hangs on very long file names.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/