also sprach Holger Parplies <wbppc AT parplies DOT de> [2011.06.01.2010 +0200]:
> > To get my desired behaviour, I set BlackoutGoodCnt to 0 globally and
> > deleted all global BlackoutPeriods.
[…]
> As I understand the concept of blackouts in BackupPC, I think it
> is meant to automagically adapt backup strategy to avoid the
> (global) blackout window ("working hours") for all hosts that can
> be backed up outside this window. That would be the "global
> blackout" case above.
> 
> Actually, I would modify your suggestion in that I'd set
> BlackoutGoodCnt to 0 *locally* in the pc config file, together
> with a local BlackoutPeriods setting. In the global config,
> BlackoutGoodCnt should be != 0. That way, you would get "expected"
> behaviour for both cases.

Yes, I understand the concept too, and it makes sense for an office.
However, I am using BackupPC chiefly to back up globally spread
machines. There are no office hours really. The only "office hours"
that exist are for the machines behind my DSL link, because I cannot
seem to get bandwidth shaping to work properly. Hence, the backups
should not start during the day but run during the night so that
they do not affect our normal usage.

PS: It's still suboptimal, because now at 23:00 hours, BackupPC
    tries to back up all hosts at home, which congests the link
    — I think it would be faster and more effective in this case to
    back each of them up in series, rather than in parallel.
    However, I do not want to set the global limit of concurrent
    backups to 1. This is at the heart of the feature suggestion
    I made here: http://bugs.debian.org/607761

> > It wouldn't hurt if BackupPC had some sort of MaxAgeBeforeIgnoringBlackout
> > setting to force-ensure some backups.
> 
> If you don't have a backup yet, are you supposed to ignore the blackout window
> or not? You can't really say, "respect it for three days, then ignore it if
> there is still no backup", at least not without defining a concept of when a
> host was added to the BackupPC configuration (timestamp of the host.pl file?).
> In any case, you have the email reminders that are supposed to alert you to
> the fact that there is no recent backup (or no backup at all). If such a case
> happens, you will need to consider whether your blackout window needs
> adjustment anyway. Automatically degrading from one backup per IncrPeriod to
> one backup per MaxAgeBefore... doesn't seem like a sufficient resolution.

Sure, you just forgot half a dozen parameters to allow tweaking of
all aspects. ;)

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"good advice is something a man gives
 when he is too old to set a bad example.
                                                  -- la rouchefoucauld
 
spamtraps: madduck.bogus AT madduck DOT net

digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev

_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/