Hello,
One of my backup repository seams to be mess up alot. I think the backup
have been interrupted multiple time. I do have a very long history for this
backup and I don't want to lose it.
First, I encounter "regressing destination" error. So as usual, I've delete
the current_mirror. But even
After deleting the current_mirror file did you then run rdiff-backup with
--check-destination-dir? This performs the actual regression to the
previous, hopefully consistent, backup.
On 15 September 2015 at 00:46, Patrik Dufresne wrote:
> Hello,
>
> One of my backup repository seams to be mess up
Hello Dominic,
I did not run "--check-destination-dir" right after deleting the
"current_mirror". I try to run it after making a backup.
This morning I had:
current_mirror.2015-08-24T01:12:31-04:00.data
current_mirror.2015-09-14T19:37:48-04:00.data
The last successful backup seams to be "2015-08
On 09/14/2015 06:46 PM, Patrik Dufresne wrote:
One of my backup repository seams to be mess up alot. I think the backup
have been interrupted multiple time. I do have a very long history for
this backup and I don't want to lose it.
First, I encounter "regressing destination" error. So as usual,
I suggest you try using my rdiff-backup-regress - at
http://www.timedicer.co.uk/programs/help/rdiff-backup-regress.sh.php - this
can force a regression (or multiple regressions).
On 15 September 2015 at 12:34, Patrik Dufresne wrote:
> Hello Dominic,
>
> I did not run "--check-destination-dir" ri
I've tried the script. I had issues with it.
It searchs 'current_mirror' file recursively. For some reash, the backup
contains files named 'current_mirror'. I add `-maxdepth 1` to fix this.
Regression also failed:
$ ./rdiff-backup-regress.sh ikus060-rdiff
rdiff-backup-regress.sh v0.7 [09 Dec 201
Hi Patrik
On 22/09/2015 22:00, Patrik Dufresne wrote:
I've tried the script. I had issues with it.
It searchs 'current_mirror' file recursively. For some reash, the
backup contains files named 'current_mirror'. I add `-maxdepth 1` to
fix this.
Good point, I have updated the script with this,
I finally manage to repair the archive ! I've browse the code to determine
where it's failing. I add some debug log for my self to determine where the
error was coming from. It look like recovery was failing because some
"increments" file was left over by failed backup. I've search them and
delete
I'm delighted it worked for you - good work! I guess it is because
deleting the increments files tricks rdiff-backup into thinking that
there are no later backups than 2015-08-21T01:12:31-04:00, and in your
case this was ok because all the subsequent backup attempts hadn't
really changed any of
