Subscribe to Mailing Lists     FAQFAQ    SearchSearch      Register  Log in to check your private messagesLog in to check your private messages    Log inLog in 
These forums brought to you by Backup Central, where we also have the Mr. Backup Blog, Mailing Lists, FAQs,
and Directories of Backup Software and Hardware
Fatal Error: Mirror metadata not found - answer

 
Post new topic   Reply to topic    Backup Central Forums Forum Index -> Rdiff-Backup
View previous topic :: View next topic  
Author Message
viczh
Guest





PostPosted: Fri Mar 19, 2004 1:13 am    Post subject: Fatal Error: Mirror metadata not found - answer Reply with quote

Hi,

my name is Victor Joukov and I started porting rdiff-backup to native Windows Python, no Cygwin etc.

I found that rdiff-backup is written mainly to Unix API, and relies on stuff that even when present in Python/Windows, usually

not implemented (many fields of stat structure are zero or bogus)

Up to now, I managed to make a local backup by modifying release 0.13.4. It lacks any permission/ACL/user/group stuff,

despite Windows has almost all of these structures. When trying to compare backup and original, I faced with the same problem

David Kempe did in February - I got misterious message - see subject. I believe the answer is in incorrect code in metadata.py, line 407.

When you try to find an appropriate point in time it is pointless to try to find EXACT match, you should be extremely lucky ;-)

So if you change == into <= in the mentioned line, so that it reads

if rp.getinctime() <= time:

cls._rp = rp

...

etc. it will work. I though need somebody to verify my hypothesis - I am new to the code, and it is not too small to figure out for sure.



I have couple notes about other parts of the system in regard to

Windows. First, to treat Windows filesystem as just case insensitive

and escape every uppercase letter leads to complete visual garbage

in backup directory if your original files had uppercases. We'd

better check for name clashes on backup system, because Windows

filesystem preserves the case. Second, why to use such long, unnesessarily detailed (timezone?) and Windows unfriendly timestamp?

It contains several colons AND uppercase T which is escaped!

Can we just translate into UTC and use something like

current_mirror.20040319082117.data

which is MUCH MORE readable than what is ACTUALLY produced on my

computer:

current_mirror.2004-03-19;08402;05821;05817-06;05800.data

It definitely should read old escaped format (or unescaped - depends

on your platform) for compatibility.



So, I am now trying to solve uid/gid/chown/inode and all other Unix

stuff. It all should work eventually on NTFS at least.



Hope this helps,

sorry for long post,

Victor.



_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com
Back to top
David Kempe
Guest





PostPosted: Fri Mar 19, 2004 3:32 am    Post subject: Fatal Error: Mirror metadata not found - answer Reply with quote

viczh wrote:

Quote:
So, I am now trying to solve uid/gid/chown/inode and all other Unix

stuff. It all should work eventually on NTFS at least.


Hi Victor,
I wish you all the very best in that regard.
let me know if there is anything else I can help with - very happy to
help you test the code and provide hosting etc.
maybe a windows only fork would be a possibility?

dave
Back to top
Display posts from previous:   
Post new topic   Reply to topic    Backup Central Forums Forum Index -> Rdiff-Backup All times are GMT - 8 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Magic SEO URL for phpBB