Craig Barratt schrieb:
> Ralf Gross writes:
>
> > I changed it to 7.1. If I want to disable full backups for a host for
> > awhile, it is not sufficient to just comment out the crontab entry
> > anymore, I have to remember to set $Conf{FullPeriod} to -1 again?
>
> Your question raises a good point. Unfortunately the backup expiry code
> doesn't do quite the right thing when $Conf{FullPeriod} is negative and
> you are using a list of values for $Conf{FullKeepCnt}. It looks like it
> will behave correctly if you also set $Conf{FullKeepCntMin} to a value
> bigger than the sum of the entries in $Conf{FullKeepCnt}. But I
> haven't tested this case.
>
> In hindsight I shouldn't have overloaded $Conf{FullPeriod} with
> negative settings for disabling backups. I should probably add
> a new config parameter for disabling backups.
I ran into another problem after setting $Conf{IncrPeriod} to 1.1.
For some hosts I schedule the full back on Sunday. The last
incremental backup for these hosts was on Friday morning or evening.
Therefor a new incremental backup started at Sunday morning a few
hours before the full would have started...
Is there any side effect on setting $Conf{IncrPeriod} to a very high
value?
Ralf
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
