Re: [BackupPC-users] $Conf{FullKeepCnt} with $Conf{FullPeriod} set to -1

[Craig B. <cba...@us...>]

"Ralf Gross" writes:

> I schedule backups exclusively with cron with this option and crontab
> entries.
> 
> $Conf{FullPeriod} =  -1;
> 
> 5 20 * * 5 /usr/share/backuppc/bin/BackupPC_serverMesg backup zorg zorg
> root 1 >/dev/null 2>&1
> 
> 5 20 * * 1-4 /usr/share/backuppc/bin/BackupPC_serverMesg backup zorg zorg
> root 0 >/dev/null 2>&1

Yes, this is the right way to do it.  However, I recommend setting
$Conf{IncrPeriod} to a number bigger than 0.95 because currently
there will be a race condition between BackupPC doing it's normal
scheduling of the incremental and the "manual" incremental via cron.
Eg:

    $Conf{IncrPeriod} = 1.1;

Alternatively, you don't need to do the incrementals with cron since
BackupPC can schedule those every day after the full.

> Now I want to keep the last 4 weekly full backups + 3 monthly full
> backups. So I changed the config.
> 
> $Conf{FullKeepCnt} = [4, 0, 3];
> 
> I'm not sure if this will work with $Conf{FullPeriod} set to -1 after
> reading this part of the documentation.
> 
> # Entry #n specifies how many fulls to keep at an interval of
> # 2^n * $Conf{FullPeriod} (ie: 1, 2, 4, 8, 16, 32, ...).

No, it won't work correctly with a negative $Conf{FullPeriod}.
You should set $Conf{FullPeriod} to slightly more than 7, so
that $Conf{FullKeepCnt} works correctly, but cron beats BackupPC
for each full.

Craig