Re: Maintenance Windows for Networks Spanning Multiple Time Zones
On Mon, 22 Jan 2001 17:20:03 EST, "Brett L. Hawn" said:
Pardon my intrusion, but common sense tells me: at a time where you will have the least amount of impact on the least amount of people.
I'll play devil's advocate here. Do you want to minimize the impact on the end users, or the number of phone calls generated to the NOC? ;)
And yes, we're alledgedly a one time zone shop. But I've gotten complaints from Europe when our 3AM window for Listserv updates impacted *their* ability to post stuff *right now*. Didn't I *understand* that this was *important* and that it was already *10AM* there? ;)
And I believe the *original* question was (or at least intended to be) "how do I *calculate/guess* when I'll have the least impact on least users". And *that* is probably still in the realm of black magic....
One of doing this is to split into several zones. We have one for US work, one for transatlantic and one for Europe. This increases the complexity but tends to lower the impact per maintenace session. - kurtis -
On Mon, 22 Jan 2001 17:20:03 EST, "Brett L. Hawn" said:
Pardon my intrusion, but common sense tells me: at a time where you will have the least amount of impact on the least amount of people.
I'll play devil's advocate here. Do you want to minimize the impact on the end users, or the number of phone calls generated to the NOC? ;)
One of doing this is to split into several zones. We have one for US work, one for transatlantic and one for Europe. This increases the complexity but tends to lower the impact per maintenace session.
- kurtis -
Too complex. Back in the Day... :) We scheduled our maintaince windows between 09:00 and 10:00 local time. Our techs were awake, we could get vendors on the phone and parts shipped if needed. --bill
participants (2)
-
bmanning＠vacation.karoshi.com -
Kurt Erik Lindqvist