Linux Punk wrote at about 16:53:08 -0600 on Sunday, October 26, 2008:
 > On Sun, Oct 26, 2008 at 4:49 AM, Steen Eugen Poulsen <sep AT lix-world DOT 
 > net> wrote:
 > > Jeffrey J. Kosowsky skrev:
 > >>
 > >> I have googled and read a lot of posts about people having trouble
 > >> with cygwin rsync/ssh but haven't seen any definitive solutions.
 > >
 > > I don't think it has anything to do with cygwin or how you backup windows
 > > machines, it's just that we keep running into file lock issues that messes
 > > up backups.
 > 
 > I would tend to disagree because we have dozens of machines that
 > backup successfully using rsyncd server (no ssh) but we ran into
 > exactly the issues described when tunneling rsync in ssh. If it was a
 > problem with locked files affecting rsync, we would see those problems
 > in both instances. We've also tried backing up dummy directories that
 > have no open files in them, and had that fail with rsync/ssh.
 > 
I just switched over to using rsyncd (without ssh) and it seems to be
working (so far after several gigabytes and several thousand files). I
also just as an experiment tried manually setting up a ssh tunnel
(e.g. -L 1873:localhost:873) and tunneling rsyncd over it -- and it
too seems to work.

So far I have tried the following permutations:
1. From Linux: rsync -av  -e "ssh" <linux remote>:<src>  <local dest>
   WORKS
2. From Linux: rsync -av  -e "ssh" <local src> <linux remote>:<dest> 
   WORKS

3. From Windows: rsync -av  -e "ssh" <windows remote>:<src>  <local dest>
   WORKS
4. From Windows: rsync -av  -e "ssh" <local src> <windows remote>:<dest> 
   WORKS

5. From Linux: rsync -av  -e "ssh" <windows remote>:<src> <local dest>
   FAILS after ~10 files
6. From Window: rsync -av  -e "ssh" <local src> <linux remote>:<dest>
   FAILS (completes but sends 0 files - when done under -vv lots of
   send/receive traffic but nothing effectively sent)

7. From Linux: rsync -av  <local src> <local dest>
   WORKS
8. From Windows: rsync -av  <local src> <local dest>
   WORKS

9. From Linux: rsync -av  <windows remote>::<src> <local dest>
   plus 'rsync --daemon' running on Windows machine
   WORKS 
10. From Linux: rsync -av  --port 1873 127.0.0.1::<src> <local dest>
   plus 'rsync --daemon --address 127.0.0.1 --port 1873 running on Windows
   and ssh tunnel from Linux to Windows with -L 1873:127.0.0.1:1873
   WORKS

NOTE: when I say 'WORKS', I mean that it copies over at least several
thousand files starting from root (either / on Linux or /c/ on
Windows) since I didn't have the time to copy over the 50GB of each
partition for each method.

So it seems of all the multiple combinations of using ssh/rsync/rsyncd
between src/dir and linux/windows (and I haven't enumerated other
obvious permutations that clearly work), the only combo that doesn't
work is using "rsync -e ssh" to copy over Windows root directory to
Linux (whether you initiate rsync from the linux or windows machine).

Can anybody explain what is going on here and what is causing the
problem?

Is this a fundamental ssh/rsync problem between Linux and Windows?
Could the problem be due to the fact that I have different rsync and
ssh versions?

Currently:
Linux: openssh-4.7p1
           rsync-2.6.9

Windows: openssh-5.1p1
                 rsync-3.0.4 protocol version 30

I really would like to get to the bottom of this...

-------------------------------------------------------------------------
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/