|
|
Austin Clements wrote:
> I don't know why I didn't think of this before... I reverted your
> patch and tried running the backup again and it worked, suggesting
> that your patch fixes the issue when creating a new backup, but breaks
> something when trying to increment an existing backup. However, then
> I ran the incremental backup again and it failed with a KeyError, so I
> reinstated your patch and it failed with the same KeyError. Just to
> check that the backup itself wasn't wedged, I ran the incremental a
> different way that doesn't use both a remote source and a remote
> destination and it worked. So now I'm just completely bamboozled.
>
> Quoth myself on Jan 21 at 5:12 pm:
>> Scratch that. The initial backup task worked, but the next one failed
>> with a very similar error involving rorp's, fast processing, and
>> KeyErrors. The destination side raised the following exception:
>> *chomp*
>
Austin,
Maybe we can solve this by adjusting the threshold at which rdiff-backup
is flushing the pipeline.
The controlling statement would be line 164 in the backup.py I sent you.
It should say:
flush_threshold = Globals.pipeline_max_length - 2
Try changing that to a smaller number, perhaps with:
flush_threshold = int(Globals.pipeline_max_length/2)
or
flush_threshold = Globals.pipeline_max_length - 20
etc.
See if one of those works for you. I know this is voodoo.... :(
Andrew
--
Andrew Ferguson - owsla@xxxxxxxxxxxxx
_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
|
|