rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] Recovery to Linux from Windows


From: Stefan Lisowski
Subject: Re: [rdiff-backup-users] Recovery to Linux from Windows
Date: Thu, 06 Jun 2013 15:54:10 -0400
User-agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:12.0) Gecko/20120314 Thunderbird/12.0

On 6/4/2013 6:05 PM, Dave Kempe wrote:
----- Original Message -----
From: "Stefan Lisowski"<address@hidden>
To: address@hidden
Sent: Wednesday, 5 June, 2013 3:35:32 AM
Subject: [rdiff-backup-users] Recovery to Linux from Windows

Our Linux box died, so now we're restoring from a rdiff-backup
repository on a Windows box running Cygwin. Fine for lowercase files.
But not fine for uppercase escaped files. I see lots of posts about why
capital letters are escaped and from the FAQ I see "Upon restore (from
the Mac backup server to the Linux system), the filenames are unquoted
and you will get "MyFile" back."

Why wouldn't you just copy the files back? If you need the entire latest 
repository and not an increment, just copy the files back.

Dave
I should have replied-all, but as I'm new to this list, I only replied to Dave. Anyway this was my reply. This is still an outstanding issue for me... I can't believe rdiff-backup does this cryptic naming and then there's no way to recover the files back to normal...?
-------------------------
How?

I did copy the files from Windows to Linux with scp, but they look like this:

# ls \;080roducts/
;065;084;067ontent;084ypes ;067ache;083etup ;080luggable;065uth;083ervice ;065;084;082eference;066rowser;087idget ;068;067;087orkflow ;080lugin;082egistry ;065rchetypes ;069xtended;080ath;073ndex ;080olicy;072;084;084;080;067ache;077anager ;067;077;070;065ction;073cons ;069xternal;069ditor ;080ortal;084ransforms ;067;077;070;067alendar ;071eneric;083etup ;080ython;070ield ;067;077;070;067ore ;071roup;085ser;070older ;082;069;065;068;077;069.txt

Where they should look like words from the English language instead. So with improper names, they aren't useful to me. I need to get back the original filenames, not the ones from the Windows OS where Foo and foo are the same file, so coming from Unix the caps get escaped and I have ;070oo instead of Foo.

- Stefan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]