NO MORE UPDATES TO THIS PAGE PLEASE. SUBMIT ALL FUTURE COMMENTS TO

12.1 pg 237

Your definition of "maintenance window" is a definition I've never come across before. I've heard it used for much smaller events; it could be a period of time when the sales database is unavailable. Typically what makes it a maintenance window is that monitoring and alerting tools are disabled for that service during the window, while maintenance (which could simply be a planned change which takes the service out of action for a while) is performed. The difference between a "change window" and a "maintenance window" is that the latter expects a larger service outage.

I've not actually heard of any term that describes what you are talking about. Indeed, I've never even heard of such a thing as a recurring scheduled activity. Sure, one off events (eg power-down tests - happened once in the past 7 years in the London office; Business Contingency Tests - but these tend to be on an application by application basis; server room migrations - building refurb so we moved the server room from ground floor to fourth floor) but as a regularly scheduled event? Nope. I'm not even sure I even like the concept, myself! shudder so much work going on at once... too much chance of errors. shudder

Given that some companies might do what you've described, the chapter is good, but shudder I wouldn't recommend it!

12.1.7 Console Server pg 242

Prior to the maintwin, ensure the console server works for all the servers you will need console access to. Console servers aren't used for daily activities (correction; shouldn't be used! Never login as root unless unavoidable - no audit trail!) and so when you do need it they may not work properly. So prior to scheduled maintenance test them!!

12.3 pg 244

Maybe update the table with "push to talk" phones?

-- StephenHarris - 16 Aug 2006