Re: [BackupPC-users] suggestion: make wakeups start at 8am
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 documentation without renaming the
> > binary. [...]
>
> The name only matters in that people may infer meaning where it is not
> meant. Though this could be fixed through documentation, and a few
> interface changes. For example, if the web interface config displayed
> the setting as DailyMaintenance instead of NightlyMaintenance even
> though the binary that uses the setting was Backuppc_nightly... If
> someone knows enough about backuppc to find the binary name, then they
> should also know enough (to find out) what it does and why.
that is what I meant. But I see that you might infer meaning where it is not
intended. You can find an instance of "BackupPC_nightly" in "ps" and wonder
why it's running in the middle of the day. Hmm.
> > Coincidentally, this maintenance task is not supposed to disturb backups ...
>
> Except it is pretty well acknowledged that it does due to the high
> amount of disk IO...
Sorry, I was unclear. I meant, this maintenance task should be run at a time
where it will not disturb backups, as opposed to other maintenance tasks that
should not disturb humans. So "nightly", from the perspective of a backup job,
is possibly during the day ;-). Or it should disturb neither backups nor
humans and be run in the morning.
There is no question that BackupPC_nightly will slow down backups (and
humans ...). Both running concurrently will almost certainly take longer
than both running sequentially (except perhaps for very slow links).
> > Agreed. The default should be good enough for most people - particularly
> > unexperienced users -, disruptive for nobody, and follow the principle of
> > least surprise. Early morning seems reasonable. Inside the blackout window
> > makes sense but may be surprising.
>
> Only in that a user may think the blackout period applies to all
> backuppc activity as opposed to backup hosts activity...
That is what I meant. "Hey, we're in the blackout period! Why is my disk going
crazy?" But whoever configured the blackout period (or just noticed there is
one) should have come across a reference to the maintenance job, and that
reference should have made clear that it is exempt from blackout.
> However, I agree that it should be scheduled to occur (by default) during the
> (default) blackout period.
I don't say I don't agree. Maybe the documentation/web interface should more
explicitly call it "backup blackout period" or something. Maybe it should even
be less definite than "blackout", since it's really only a hint that BackupPC
will ignore if necessary. It's really the opposite of a "preferred backup
window".
> > I'd argue for making BackupPC_nightly run time independent of
> > the WakeupSchedule. The WakeupSchedule defines possible times when backups
> > may be started (though they may continue or be started delayed due to
> > MaxBackups). Having an independent time for BackupPC_nightly where no
> > backups
> > are considered makes sense, eg.
> >
> > $Conf {WakeupSchedule} = [ 21, 22, 23, 0, 1, 2, 3 ];
> > $Conf {NightlySchedule} = [ 7.75 ];
>
> Not a bad idea, for example if I know all my hosts have a blackout time
> of 7am - 7pm, then why do I need backuppc to wake up and schedule all
> the hosts, only to find out that backups are not needed?
What's worse, it may decide that a backup *is* needed (because of unexpected
ping failures or something), although you never intended for one to be done at
that time.
It should be possible to define when backups are intended to be run
(WakeupSchedule), give preferences for when to run them (BlackoutPeriod) and
configure when to run the maintenance job(s). Maintenance jobs and backups are
really independent. In my opinion, using a common schedule is just saving a
configuration variable. If you want both backups and maintenance to run at
22:00, you can do that just as well with independent settings.
> Also keep in mind that unless you have a very small pool, and/or very
> fast (disks) pool, then your daily maintenance will probably take much
> more than 15 mins... (Mine takes around 3 hours).
I'm totally surprised to see times of 5 minutes on one pool and 23 on another.
I seemed to remember something like 2 hours, too. Well, I'm not complaining ;-).
> Well, we could hive off the pool maintenance into a new binary called
> backuppc_poolmaintenance and have that run separate from the
> backuppc_dailymaintenance which does the email,
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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...
> >> Comments, anyone?
> >
> > 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
> > NightlyWakeupSchedule or such setting that would specify at which time
> > that process would start running. BackupPC would wake up on either
> > WakeupSchedule or NightlyWakeupSchedule, and then would decide if it
> > would run backups or BackupPC_nightly (or both) based on that hour
> > being on the first, second, or both variables. In that case, it would
> > also be much easier to set a sensible default time for
> > BackupPC_nightly to run.
> >
> > 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 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 or caught outside of the blackout
> time because they aren't available at night.
>
> --
I'm warming to the name change to BackupPC_daily since 'daily' most
generically implies once a day whereas 'nightly' would imply during
the nighttime.
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] suggestion: make wakeups start at 8am
-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 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 don't think the name is important. It's an implementation detail. You can
> change related config settings and the documentation without renaming the
> binary. Does anybody care about the name "BackupPC_Admin"? People should read
> documentation, and if they are about to change the time BackupPC_nightly is
> run, they almost certainly have. I would guess that the origins of the name
> are probably from the observation that most maintenance tasks are run during
> the night, when they don't disturb anyone. Server backups are an example of
> such a task, as are "daily" cron jobs.
The name only matters in that people may infer meaning where it is not
meant. Though this could be fixed through documentation, and a few
interface changes. For example, if the web interface config displayed
the setting as DailyMaintenance instead of NightlyMaintenance even
though the binary that uses the setting was Backuppc_nightly... If
someone knows enough about backuppc to find the binary name, then they
should also know enough (to find out) what it does and why.
> Coincidentally, this maintenance task is not supposed to disturb backups ...
Except it is pretty well acknowledged that it does due to the high
amount of disk IO... Of course, there are things that could be done to
off-set that, such as a small sleep every 100 "bits" it processes, but
it will *still* impact on backup performance, just less...
> But you should keep in mind that not everyone has a dedicated backup server.
> For example, I run BackupPC on an NFS/NIS/whatever-server to an external iSCSI
> device. The server is idle during the night, so why not use it as BackupPC
> server? The storage unit is independent; that is what seems to matter.
> Obviously, I prefer BackupPC_nightly disturbing the backups rather than my
> users :). I *have* seen it run during the day, and it wasn't being very subtle
> about it.
Exactly, and that is how obviously it will impact on backup performance
as well.
> If BackupPC_nightly is renamed, then why not to something that makes sense,
> like BackupPC_dailyMaintenance or BackupPC_poolMaintenance or just
> BackupPC_maintenance?
Keep in mind that is is also responsible for sending out the reminder
emails, updating the status.pl, and probably other stuff I don't know
about... It doesn't *just* maintain the pool...
> Agreed. The default should be good enough for most people - particularly
> unexperienced users -, disruptive for nobody, and follow the principle of
> least surprise. Early morning seems reasonable. Inside the blackout window
> makes sense but may be surprising.
Only in that a user may think the blackout period applies to all
backuppc activity as opposed to backup hosts activity... However, I
agree that it should be scheduled to occur (by default) during the
(default) blackout period.
>>> As you said yourself in another thread, even though BackupPC_nightly
>>> can be run while other backups are running, it is better to do so
>>> while no or few backups are running so that they do not compete for
>>> disk I/O
>
> Which is why I'd argue for making BackupPC_nightly run time independent of
> the WakeupSchedule. The WakeupSchedule defines possible times when backups
> may be started (though they may continue or be started delayed due to
> MaxBackups). Having an independent time for BackupPC_nightly where no backups
> are considered makes sense, eg.
>
> $Conf {WakeupSchedule} = [ 21, 22, 23, 0, 1, 2, 3 ];
> $Conf {NightlySchedule} = [ 7.75 ];
Not a bad idea, for example if I know all my hosts have a blackout time
of 7am - 7pm, then why do I need backuppc to wake up and schedule all
the hosts, only to find out that backups are not needed? However, I do
need it to wake up and process the pool at 10am...
Also keep in mind that unless you have a very small pool, and/or very
fast (disks) pool, then your daily maintenance will probably take much
more than 15 mins... (Mine takes around 3 hours).
>> I also agree that setting the default time inside the default backup
>> window is a good idea,
> "Backup window" or "blackout window"?
Damn, did I really say that :( I of course meant:
I also agree that setting the default time insi
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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
> >>> BackupPC_daily, as it makes more sense to run it during the day when
> >>> backups are not running. Isn't that right?
I don't think the name is important. It's an implementation detail. You can
change related config settings and the documentation without renaming the
binary. Does anybody care about the name "BackupPC_Admin"? People should read
documentation, and if they are about to change the time BackupPC_nightly is
run, they almost certainly have. I would guess that the origins of the name
are probably from the observation that most maintenance tasks are run during
the night, when they don't disturb anyone. Server backups are an example of
such a task, as are "daily" cron jobs.
Coincidentally, this maintenance task is not supposed to disturb backups ...
But you should keep in mind that not everyone has a dedicated backup server.
For example, I run BackupPC on an NFS/NIS/whatever-server to an external iSCSI
device. The server is idle during the night, so why not use it as BackupPC
server? The storage unit is independent; that is what seems to matter.
Obviously, I prefer BackupPC_nightly disturbing the backups rather than my
users :). I *have* seen it run during the day, and it wasn't being very subtle
about it.
If BackupPC_nightly is renamed, then why not to something that makes sense,
like BackupPC_dailyMaintenance or BackupPC_poolMaintenance or just
BackupPC_maintenance?
> >> 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 or caught outside of the blackout
> >> time because they aren't available at night.
> >
> > Agreed, however some default has to be provided and the current one
> > (1am) may not be the best possible one.
Agreed. The default should be good enough for most people - particularly
unexperienced users -, disruptive for nobody, and follow the principle of
least surprise. Early morning seems reasonable. Inside the blackout window
makes sense but may be surprising.
> > As you said yourself in another thread, even though BackupPC_nightly
> > can be run while other backups are running, it is better to do so
> > while no or few backups are running so that they do not compete for
> > disk I/O
Which is why I'd argue for making BackupPC_nightly run time independent of
the WakeupSchedule. The WakeupSchedule defines possible times when backups
may be started (though they may continue or be started delayed due to
MaxBackups). Having an independent time for BackupPC_nightly where no backups
are considered makes sense, eg.
$Conf {WakeupSchedule} = [ 21, 22, 23, 0, 1, 2, 3 ];
$Conf {NightlySchedule} = [ 7.75 ];
> > Someone who uses a
> > different setup (backups during the day, at noon, etc.) will have to
> > customize these settings anyway, so they can also choose the best time
> > for BackupPC_nightly at that time.
Agreed.
> Maybe a more simple change is to add a comment to the blackout
> schedule section advising to set the nightly/daily run to during the
> blackout schedule. Also adding a comment to the daily/nightly section
> advising to schedule this for a time when you are least likely to run
> backups to improve performance. Also note that you can run it during a
> backup if desired.
I agree that the important parts are documentation changes. Everything can be
done with BackupPC as it is now, and probably the current default settings
are good enough for people who don't want to customize them. And, yes,
*better* default values may be even better for them :). Good and easily
accessible advice is best of all.
> I also agree that setting the default time inside the default backup
> window is a good idea,
"Backup window" or "blackout window"?
> that way if someone decides to change the
> default, then it is up to them to also change the other value...
>
> I also agree on renaming to daily, consider /etc/cron.daily etc, it is
> something that should be run every 24 hours, not needed to run at night.
"Daily" is not strictly a requirement. "Regularly" is (but BackupPC_regularly
is a bad name ;-). BackupPCNightlyPeriod effectively makes it traverse the
pool less often, and that's ok (hmm, what about e-mails, though?).
> As to running it at intervals less than 24 hours, I'm not sur
Re: [BackupPC-users] suggestion: make wakeups start at 8am
-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 that right? >> 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 or caught outside of the blackout >> time because they aren't available at night. > > Agreed, however some default has to be provided and the current one > (1am) may not be the best possible one. > > As you said yourself in another thread, even though BackupPC_nightly > can be run while other backups are running, it is better to do so > while no or few backups are running so that they do not compete for > disk I/O and there is also the locking overhead of both potentially > accessing the same files (don't know exactly how that works, but just > disk I/O is enough reason to do it while other backups are not > running). > > I agree with the OP that 8am would be more sensible considering it is > inside the default blackout period (when most heavy backups should be > finished and less backups should be running). Someone who uses a > different setup (backups during the day, at noon, etc.) will have to > customize these settings anyway, so they can also choose the best time > for BackupPC_nightly at that time. > > The suggestion on the name change is that "nightly" implies it should > be run during the night, when in fact what you want is to run it once > a day, at the time that is more convenient for you. Maybe a more simple change is to add a comment to the blackout schedule section advising to set the nightly/daily run to during the blackout schedule. Also adding a comment to the daily/nightly section advising to schedule this for a time when you are least likely to run backups to improve performance. Also note that you can run it during a backup if desired. I also agree that setting the default time inside the default backup window is a good idea, that way if someone decides to change the default, then it is up to them to also change the other value... I also agree on renaming to daily, consider /etc/cron.daily etc, it is something that should be run every 24 hours, not needed to run at night. As to running it at intervals less than 24 hours, I'm not sure I see the advantage, better to just get it to process a smaller section of your backup pool each day, rather than run it on the whole pool every x days... Regards, Adam -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpVKo8ACgkQGyoxogrTyiW9MwCgo16jGi/iKRakYz4iRdgXdGLG 3GMAn2aNaJHSQEt45sXgmggxpc8OrSzs =Zlrm -END PGP SIGNATURE- -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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, anyone?
> >
> > 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
> > NightlyWakeupSchedule or such setting that would specify at which time
> > that process would start running. BackupPC would wake up on either
> > WakeupSchedule or NightlyWakeupSchedule, and then would decide if it
> > would run backups or BackupPC_nightly (or both) based on that hour
> > being on the first, second, or both variables. In that case, it would
> > also be much easier to set a sensible default time for
> > BackupPC_nightly to run.
> >
> > 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 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 or caught outside of the blackout
> time because they aren't available at night.
Since "daily" simply implies "with a 24-hour period", while "nightly"
additionally implies that it occurs at night, i believe the more general
term should be given preference (i myself run nightly's at 3pm...).
Furthermore, i agree that separating the setting for the wake-up schedule
from that of the "nightly" schedule would be a good idea - it is just more
intuitive and flexible. And while we're at it, why keep the requirement that
it runs exactly once a day?
--
Pieter
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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 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 or caught outside of the blackout > time because they aren't available at night. Agreed, however some default has to be provided and the current one (1am) may not be the best possible one. As you said yourself in another thread, even though BackupPC_nightly can be run while other backups are running, it is better to do so while no or few backups are running so that they do not compete for disk I/O and there is also the locking overhead of both potentially accessing the same files (don't know exactly how that works, but just disk I/O is enough reason to do it while other backups are not running). I agree with the OP that 8am would be more sensible considering it is inside the default blackout period (when most heavy backups should be finished and less backups should be running). Someone who uses a different setup (backups during the day, at noon, etc.) will have to customize these settings anyway, so they can also choose the best time for BackupPC_nightly at that time. The suggestion on the name change is that "nightly" implies it should be run during the night, when in fact what you want is to run it once a day, at the time that is more convenient for you. Thanks, Filipe -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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 or caught outside of the blackout > time because they aren't available at night. Indeed you are correct, and I considered this. I made my initial suggestion in light of the fact that the default blackout period starts at 7am, indicating a distinct likelihood that backups are typically done at night. I do have some machines which are backed up during the day, but for them, the early morning is a poor time as well. If someone comes into work, plugs in and turns on their laptop, they don't want to be stymied by the machine being backed up (and thereby slowed down) immediately. They typically have backups scheduled for noonish, when the lunch break happens. So I think that 8am is about as good a default time as any, and better than most, for to run the cleanup processes, since it is the least likely time to run a backup. As always, YMMV, but I'm just taking a guess at the time that is likely to be the least inconvenient for the greatest number of people. -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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 during the night...
>> Comments, anyone?
>
> 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
> NightlyWakeupSchedule or such setting that would specify at which time
> that process would start running. BackupPC would wake up on either
> WakeupSchedule or NightlyWakeupSchedule, and then would decide if it
> would run backups or BackupPC_nightly (or both) based on that hour
> being on the first, second, or both variables. In that case, it would
> also be much easier to set a sensible default time for
> BackupPC_nightly to run.
>
> 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?
>
> Filipe
I don't disagree with you, but for the last paragraph, some
environments run backups during the day when the client computers are
on.
Tony
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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
> 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
> NightlyWakeupSchedule or such setting that would specify at which time
> that process would start running. BackupPC would wake up on either
> WakeupSchedule or NightlyWakeupSchedule, and then would decide if it
> would run backups or BackupPC_nightly (or both) based on that hour
> being on the first, second, or both variables. In that case, it would
> also be much easier to set a sensible default time for
> BackupPC_nightly to run.
>
> 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 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 or caught outside of the blackout
time because they aren't available at night.
--
Les Mikesell
lesmikes...@gmail.com
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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 > NightlyWakeupSchedule or such setting that would specify at which time > that process would start running. BackupPC would wake up on either > WakeupSchedule or NightlyWakeupSchedule, and then would decide if it > would run backups or BackupPC_nightly (or both) based on that hour > being on the first, second, or both variables. In that case, it would > also be much easier to set a sensible default time for > BackupPC_nightly to run. > > 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 think these are superior ideas, and should be adopted. -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] suggestion: make wakeups start at 8am
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 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
NightlyWakeupSchedule or such setting that would specify at which time
that process would start running. BackupPC would wake up on either
WakeupSchedule or NightlyWakeupSchedule, and then would decide if it
would run backups or BackupPC_nightly (or both) based on that hour
being on the first, second, or both variables. In that case, it would
also be much easier to set a sensible default time for
BackupPC_nightly to run.
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?
Filipe
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
[BackupPC-users] suggestion: make wakeups start at 8am
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 start at 7am, this setting would seem to be a
reasonable way to make the nightly maintenance job run at a time when
no backup needs to run.
The default configuration causes BackupPC to run the BackupPC_nightly job
when there are backup jobs which may need to run during the night. Many of
us have trouble getting all the backups done in the time allotted; it would
seem to make sense to use that time most efficiently.
Comments, anyone?
Have things changed in such a way that this is not relevant anymore? (I
started doing this with Backuppc 2.1.0, the first version I used).
Downsides to doing this?
--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
