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

[Ralf Gross]

Craig Barratt schrieb:
 Ralf Gross writes:
 
  Craig Barratt schrieb:
 
   Ralf Gross writes:
  
  Is there any side effect on setting $Conf{IncrPeriod} to a very high
  value?
 
 My first reaction was yes, but the answer is actually no.  The normal
 scheduler makes sure a full backup has to be at least $Conf{FullPeriod}
 after the last full backup, and at least $Conf{IncrPeriod} after the
 last incremental backup.
 
 But the BackupPC_serverMesg command starts a manual backup, which
 ignores all the background scheduling rules.  So a large value is
 fine.  That will prevent any normally scheduled backup from occurring
 (provided an incremental backup exists).
 
 In fact, this will move all control to cron, so if you disable your
 crontab entries then no backups will occur without you having to
 set $Conf{FullPeriod} to a negative value (again, provided an
 incremental backup exists).  (And in fact, because of how the
 code is written, if you use a value above, say, 1 million,
 then you don't even need a incremental backup to prevent all
 regular backups.)

That seems to to be exactly what I want!

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
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

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

[Ralf Gross]

Craig Barratt schrieb:
 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 21
 
  5 20 * * 1-4 /usr/share/backuppc/bin/BackupPC_serverMesg backup
  zorg zorg
  root 0 /dev/null 21

 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;

Ok, I changed it to 1.1

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

The full backups only take place at weekend, the incremental backups
from Monday to Friday. I like to know when each backup starts and
therefore I'll stay with cron. At the moment backuppc backups only 6
hosts.

  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.

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?

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
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/