Re: [rdiff-backup-users] rdiff-backup probm

[Davy Durham]

AH MY BAD!  Ignore the previous message..

The patches DID fix the problem.. I just didn't apply them on both machines.

I'm still doing some testing.. will report back.


Also, still two questions:

1) Is it okay/wise to delete the backup.log and restore.log files from 
the rdiff-backup-data directories? 

2) I'm noticing some old empty directory trees within 
rdiff-backup-data/increments that I would presume should have been 
removed as the --remove-older-than flag has been being used all along to 
produce a rolling 30 day window.   These trees have other empty 
directories in them... but no files of any kind.  Is this normal/expected?

Thanks,
 Davy

Ben Escoto wrote:

> > > > > > Davy Durham <address@hidden>
> > > > > > wrote the following on Mon, 15 Aug 2005 16:31:31 -0500
> > > > > >            
> > The following is the output from v1.0.0:
> >
> > Sending back exception 'filetype' of type exceptions.KeyError:
> >    
> ...
>  
>
> >    return self.data['filetype']
> >    
>
> Thanks for the demo script!  Hopefully
>
> http://savannah.nongnu.org/cgi-bin/viewcvs/rdiff-backup/rdiff-backup/rdiff_backup/backup.py.diff?r2=1.30&r1=1.29&diff_format=u
>
> will fix the basic problem, but won't help restore backups that
> already have the unsynced mirror_metadata dir problem.  For that I
> think these two will work:
>
> http://savannah.nongnu.org/cgi-bin/viewcvs/rdiff-backup/rdiff-backup/rdiff_backup/rorpiter.py.diff?r2=1.27&r1=1.26&diff_format=u
> http://savannah.nongnu.org/cgi-bin/viewcvs/rdiff-backup/rdiff-backup/rdiff_backup/rpath.py.diff?r2=1.84&r1=1.83&diff_format=u
>
>
>