Well, I tried using the native client, Cygwin wasn't involved in any part of
the transaction, but I still got the file-too-long error. This is running
1.2.5 on both systems.

Stack trace:

Exception '[Error 206] The filename or extension is too long:
'f:/gazelle/rdiff-
backup-data/increments/home/austin/.cxgames/winxp/windata/;083tart;077enu.;067^5
;0693;065^5;070windows^5;070profiles^5;070;065ll^2;066;085sers^5;070;083tart^2;0
66;077enu/;080rograms/;069lectronic+;065rts/;083;080;079;082;069^;0692^84^;0652'
' raised of class '<type 'exceptions.WindowsError'>':
  File "rdiff_backup\Main.pyc", line 304, in error_check_Main
  File "rdiff_backup\Main.pyc", line 324, in Main
  File "rdiff_backup\Main.pyc", line 280, in take_action
  File "rdiff_backup\Main.pyc", line 346, in Backup
  File "rdiff_backup\backup.pyc", line 38, in Mirror
  File "rdiff_backup\backup.pyc", line 232, in patch
  File "rdiff_backup\rorpiter.pyc", line 281, in __call__
  File "rdiff_backup\backup.pyc", line 526, in fast_process
  File "rdiff_backup\longname.pyc", line 203, in get_mirror_inc_rps
  File "rdiff_backup\longname.pyc", line 189, in find_inc_pair
  File "rdiff_backup\longname.pyc", line 128, in check_new_index
  File "rdiff_backup\longname.pyc", line 111, in wrap_call
  File "rdiff_backup\longname.pyc", line 122, in make_parent
  File "rdiff_backup\rpath.pyc", line 988, in makedirs
  File "os.pyc", line 157, in makedirs

Traceback (most recent call last):
  File "rdiff-backup", line 30, in <module>
  File "rdiff_backup\Main.pyc", line 304, in error_check_Main
  File "rdiff_backup\Main.pyc", line 324, in Main
  File "rdiff_backup\Main.pyc", line 280, in take_action
  File "rdiff_backup\Main.pyc", line 346, in Backup
  File "rdiff_backup\backup.pyc", line 38, in Mirror
  File "rdiff_backup\backup.pyc", line 232, in patch
  File "rdiff_backup\rorpiter.pyc", line 281, in __call__
  File "rdiff_backup\backup.pyc", line 526, in fast_process
  File "rdiff_backup\longname.pyc", line 203, in get_mirror_inc_rps
  File "rdiff_backup\longname.pyc", line 189, in find_inc_pair
  File "rdiff_backup\longname.pyc", line 128, in check_new_index
  File "rdiff_backup\longname.pyc", line 111, in wrap_call
  File "rdiff_backup\longname.pyc", line 122, in make_parent
  File "rdiff_backup\rpath.pyc", line 988, in makedirs
  File "os.pyc", line 157, in makedirs
WindowsError: [Error 206] The filename or extension is too long:
'f:/gazelle/rdi
ff-backup-data/increments/home/austin/.cxgames/winxp/windata/;083tart;077enu.;06
7^5;0693;065^5;070windows^5;070profiles^5;070;065ll^2;066;085sers^5;070;083tart^
2;066;077enu/;080rograms/;069lectronic+;065rts/;083;080;079;082;069^;0692^84^;06
52'

Again, thanks for any help. I'm really hoping to get this working, as
rdiff-backup seems to be the ideal solution for my circumstances.

On Thu, Jan 15, 2009 at 1:05 AM, Dominic <[email protected]> wrote:

> Austin Roberts wrote:
>
>> Windows to Linux works fine with the native binary, Linux to Windows is
>> where I'm having problems. Is there any way to start the native windows
>> client as a server and back up to it? I've tried using SSH, and I can run
>> the native Windows client (as opposed to the Cygwin version), but it
>> complains when I try to specify the drive letter.
>>
>> Tomorrow I'm going to try the BackupFromWindowsToLinux instructions, using
>> a remote source and local destination. Hopefully I'll be able to script it
>> so I can run a script from the Linux source and have the Windows destination
>> initiate the rdiff-backup sequence with the native rdiff-backup binary.
>>
>> If I get it working smoothly, I'll make a BackupFromLinuxToWindows page on
>> the wiki.
>>
>> - Austin
>>
>> On Wed, Jan 14, 2009 at 10:45 PM, Andrew Ferguson 
>> <[email protected]<mailto:
>> [email protected]>> wrote:
>>
>>
>>  I guess you need an SSH server on the Windows machine. I had a free one
> installed but recently uninstalled it (as I use rdiff the more usual way:
> Windows -> Linux) and can't find it now. But here is another free one that
> looks ok: http://mobassh-en.mobatek.net/. I think port 22 would need to be
> open for TCP traffic, and you should make sure that the remote command
> (--remote-schema) contains the path to rdiff-backup.exe on the server (or
> that rdiff-backup.exe's location is in the Windows PATH variable). HTH
>
> Dominic
>
>
> _______________________________________________
> rdiff-backup-users mailing list at [email protected]
> http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> Wiki URL:
> http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
>
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Reply via email to