Jeffrey J. Kosowsky wrote:
> Nils Breunese (Lemonbit) wrote at about 01:07:02 +0100 on Tuesday, October 
> 28, 2008:
>  > Jeffrey J. Kosowsky wrote:
>  > 
>  > > 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)
>  > 
>  > File::RsyncP is a (non-complete) implementation of rsync in Perl  
>  > written for use by BackupPC. The latest version of File::RsyncP  
>  > supports protocol version 28, there is nothing to upgrade there. The  
>  > protocol used is the highest version supported by both the client and  
>  > the server, which is 28 in either case you described. There is no  
>  > version of File::RsyncP which supports protocol >28 at the moment.
>  > 
> That's precisely my point. If we want to have the 'rsync' method work
> better with Window, then File::RsyncP needs to be updated to version
> 30. Since File::Rsync was authored by Craig Barratt (the same person
> who leads the BackupPC project) as part of his toolkit for writing
> BackupPC, I thought it would be reasonable to inquire about updating
> File::Rsync.
> 
> And since one of the touted advantages of BackupPC is its ability to
> back up Windows in addition to Linux and since many people have been
> having problems with rsync, it seems reasonable to suggest this as a
> priority area for future development (assuming the developers are
> willing and able). While I have only pidgen-level Perl skills, I would
> certainly be willing to help test and troubleshoot any efforts in this
> direction. 
> 
>  > By the way, we are backing up machines that all run rsync 3.0.4 and  
>  > support protocol 30, but we're using BackupPC with File::RsyncP, so  
>  > the negotiated procotol is protocol 28 for all our backups. And our  
>  > backups are working fine. But we're not backing up any Windows machines.
> 
> My point PRECISELY -- Protocol 30 seems to be important to avoid hangs
> with long and/or weird file names in Windows. Since those file types
> don't exist in Linux, Protocol 28 works just fine there.
> 
> Finally, the reason for summarizing this is that I have seen all types
> of posts about people having issues with rsync on Windows but I failed
> to find any good explanation or solution despite massive
> googling. Even my question asked here about a week ago received a
> variety of answers none of which seemed to focus on this point.
> 
> Now I may be wrong in my diagnosis, but if it is right, hopefully this
> summary will be helpful to other users in a similar situation.
> 
Jeff, just letting you know that I've been silently cheering you on.  I
have intermittent problems with rsyncd hanging while backing up my
Windows machines, and I hope you find a cure!  Unfortunately I don't
have much assistance to provide.  I can only say that backing up my
Linux hosts (rsync over ssh) works more reliably than backing up my
Windows hosts (rsynd).  I do get successful backups of my Windows hosts
via rsyncd, but I also get hangs more often than I'd like.

-Rob
********************************************************

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. If you are not the addressee, any disclosure, reproduction,
copying, distribution, or other dissemination or use of this transmission in
error please notify the sender immediately and then delete this e-mail.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted lost, destroyed, arrive late or
incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message which arise as a result of e-mail
transmission. If verification is required please request a hard copy
version.

********************************************************


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