Dan D Niles writes:
> I tracked down the bug. When I changed the config file, it caused
> a problem where something wasn't defined that should have been.
> I uncommented the line
Eeeek! This is a serious bug. Thanks for tracking it down.
The problem is that when it removes multiple fulls in
On Thu, 2005-01-09 at 16:51 -0500, Dan D Niles wrote:
> I figured out how to trigger the bug.
>
> When I went to:
>
> $Conf{FullPeriod} = 6.97;
> $Conf{IncrPeriod} = 0.97;
> $Conf{FullKeepCnt} = [ 1, 1, 1];
> $Conf{IncrKeepCnt} = 4;
>
> it triggers the bug.
>
> If I change the FullKeepCnt to:
>
Dan D Niles writes:
>
> Attached is the backups file that caused this, and a patch to
> prevent it from happening. I'm sure a more elaborate fix is possible,
> this is just a quick hack to keep my backup from disappearing.
I figured out how to trigger the bug.
I previously had:
$Conf{Full
I tracked down the bug. When I changed the config file, it caused
a problem where something wasn't defined that should have been.
I uncommented the line
#printf("Deleting backup $i ($prevFull)\n");
and added some additional prints.
Deleting backup 3 (2)
Deleting backup 2 (1)
Delet
I had been backing up a host for a while using only full backups
($Conf{FullPeriod} = 0.97; $Conf{IncrPeriod} = 1.97;). This was
working fine for a long time.
Yesterday I switched to using incrementals ($Conf{FullPeriod} = 6.97;
$Conf{IncrPeriod} = 0.97;). So last night it should have done an
i
