Hi,
Adam Goryachev wrote on 2009-07-09 12:07:11 +1000 [Re: [BackupPC-users]
suggestion: make wakeups start at 8am]:
> Holger Parplies wrote:
> > I don't think the name is important. It's an implementation detail. You can
> > change related config settings and the docum
Les Mikesell wrote at about 10:39:14 -0500 on Wednesday, July 8, 2009:
> Filipe Brandenburger wrote:
> >
> >> $Conf{WakeupSchedule} = ...
> >> The default configuration causes BackupPC to run the BackupPC_nightly job
> >> when there are backup jobs which may need to run during the night...
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Holger Parplies wrote:
> Hi,
>
> Adam Goryachev wrote on 2009-07-09 09:24:05 +1000 [Re: [BackupPC-users]
> suggestion: make wakeups start at 8am]:
>> Filipe Brandenburger wrote:
>>> On Wed, Jul 8, 2009 at 11:39, Les Mikese
Hi,
Adam Goryachev wrote on 2009-07-09 09:24:05 +1000 [Re: [BackupPC-users]
suggestion: make wakeups start at 8am]:
> Filipe Brandenburger wrote:
> > On Wed, Jul 8, 2009 at 11:39, Les Mikesell wrote:
> >>> Also, as an aside, the process should probably be renamed to
> &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filipe Brandenburger wrote:
> On Wed, Jul 8, 2009 at 11:39, Les Mikesell wrote:
>>> Also, as an aside, the process should probably be renamed to
>>> BackupPC_daily, as it makes more sense to run it during the day when
>>> backups are not running. Isn't
On Wed, Jul 08, 2009 at 10:39:14AM -0500, Les Mikesell wrote:
> Filipe Brandenburger wrote:
> >
> >> $Conf{WakeupSchedule} = ...
> >> The default configuration causes BackupPC to run the BackupPC_nightly job
> >> when there are backup jobs which may need to run during the night...
> >> Comments, an
On Wed, Jul 8, 2009 at 11:39, Les Mikesell wrote:
>> Also, as an aside, the process should probably be renamed to
>> BackupPC_daily, as it makes more sense to run it during the day when
>> backups are not running. Isn't that right?
>
> I'm not sure you can make a general assumption about when backu
On 07/08 10:39 , Les Mikesell wrote:
> I'm not sure you can make a general assumption about when backups are
> run. Most places would catch machines that are on all the time at night
> but there may also be a lot of desktop machines that are either started
> manually through the web interface o
On Jul 8, 2009, at 11:08 AM, Filipe Brandenburger wrote:
> Hi,
>
> On Wed, Jul 8, 2009 at 10:15, Carl Wilhelm
> Soderstrom wrote:
>> $Conf{WakeupSchedule} = ...
>> The default configuration causes BackupPC to run the
>> BackupPC_nightly job
>> when there are backup jobs which may need to run du
Filipe Brandenburger wrote:
>
>> $Conf{WakeupSchedule} = ...
>> The default configuration causes BackupPC to run the BackupPC_nightly job
>> when there are backup jobs which may need to run during the night...
>> Comments, anyone?
>
> Yes, I would suggest decoupling the start time for the
> Backup
On 07/08 11:08 , Filipe Brandenburger wrote:
> Yes, I would suggest decoupling the start time for the
> BackupPC_nightly job from the obscure setting of being the first hour
> on which WakeupSchedule is set to.
>
> I believe it would be much more clear if there was a separate
> NightlyWakeupSchedu
Hi,
On Wed, Jul 8, 2009 at 10:15, Carl Wilhelm
Soderstrom wrote:
> $Conf{WakeupSchedule} = ...
> The default configuration causes BackupPC to run the BackupPC_nightly job
> when there are backup jobs which may need to run during the night...
> Comments, anyone?
Yes, I would suggest decoupling the
I tend to do this on my installations, because it makes sense for my
environments.
In config.pl I put:
# set the wakeups to 'start' at 8am,
# so BackupPC_nightly will start doing maintenance
# when the main blackout period starts
$Conf{WakeupSchedule} = [8..24,1..7];
Since the default blackouts
13 matches
Mail list logo
