Re: [BackupPC-users] UPDATE: Hypothesis: Problems backing up Windows machines under 'rsync' traced to perl-File-RsyncP protocol 28 limitation
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. 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. Nils Breunese. - 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=100url=/ ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] UPDATE: Hypothesis: Problems backing up Windows machines under 'rsync' traced to perl-File-RsyncP protocol 28 limitation
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 - 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=100url=/ ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] UPDATE: Hypothesis: Problems backing up Windows machines under 'rsync' traced to perl-File-RsyncP protocol 28 limitation
Jeffrey J. Kosowsky wrote: Nils Breunese (Lemonbit) wrote at about 01:07:02 +0100 on Tuesday, October 28, 2008: 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. Are you sure? What makes you think that? I believe that File::RsyncP only implements the parts of rsync that are actually used by BackupPC. It only makes sense to support protocol 28 in File::RsyncP when features in BackupPC will use functionality only available with protocol 28. 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. What do you mean by saying that long and/or weird file names don't exist in Linux? Can file names be longer when using Windows than they can when using Linux? Can Windows file names be weirder? (If so, what does that mean exactly?) I'm not saying that it's not true that protocol 30 did not add functionality that somehow fixes your problem (because I'm not really up to speed on what the protocol differences are), but I just have this gut feeling that the protocol version is not the problem. Craig might be able to explain all of this better. Nils Breunese. - 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=100url=/ ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] UPDATE: Hypothesis: Problems backing up Windows machines under 'rsync' traced to perl-File-RsyncP protocol 28 limitation
Nils Breunese (Lemonbit) wrote at about 02:04:40 +0100 on Tuesday, October 28, 2008: Jeffrey J. Kosowsky wrote: Nils Breunese (Lemonbit) wrote at about 01:07:02 +0100 on Tuesday, October 28, 2008: 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. Are you sure? What makes you think that? I believe that File::RsyncP only implements the parts of rsync that are actually used by BackupPC. It only makes sense to support protocol 28 in File::RsyncP when features in BackupPC will use functionality only available with protocol 28. I believe my earlier email was pretty explicit about showing how rsync hangs with protocol 28 but not with protocol 30. I believe that I have pretty soundly narrowed it down to that difference. 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. What do you mean by saying that long and/or weird file names don't exist in Linux? Can file names be longer when using Windows than they can when using Linux? Can Windows file names be weirder? (If so, what does that mean exactly?) This I believe is also well known that Windows creates some very long file names (255 characters) that rsync cannot handle. I'm not saying that it's not true that protocol 30 did not add functionality that somehow fixes your problem (because I'm not really up to speed on what the protocol differences are), but I just have this gut feeling that the protocol version is not the problem. Craig might be able to explain all of this better. I dunno seems pretty clear to me that when I run an analogous rsync command manually with 3.0.4 from the command line and it hangs just like Backuppc does when protocol is forced to 28 but it works when protocol is set to 30. But I'm not an expert and if someone can prove me wrong or find an alternate explanation or solution I would be happy to oblige.. Nils Breunese. - 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=100url=/ ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/ - 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=100url=/ ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
