On 7/7/11 5:40 PM, gregrwm wrote:
>>>> Normally you'd have moderately frequent wakeups where the actual
>>> scheduling of the runs is controlled by other settings (which are
>>> checked at each wakeup).  Is there some reason that is a problem?
>
> generally i want backups to run at one specific time only, but i want
> specifically requested backups to be allowed anytime.

Just set $Conf{BlackoutPeriods} to cover all the time you don't want backups to 
start automatically.  If your targets aren't on all the time you may want to 
set 
BlackoutGoodCnt to 0, depending on whether you'd rather skip a backup than run 
it outside of your blackout window - they won't run before IncPeriod has 
elapsed 
anyway.

I don't think wakeups are necessary for manually starting a backup unless it is 
blocked by something at the time of the request.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com



------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
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/