Image © maksym yemelyanov, 123RF.com

Image © maksym yemelyanov, 123RF.com

Windows of Change

Welcome

Article from ADMIN 33/2016
By
By a virtual show of hands, how many of you open change records for changes that occur between the hours of 23:00 and 06:00? That's almost all of you. No, I didn't actually have to see you to know how many of you either raised your hands virtually or physically.

By a virtual show of hands, how many of you open change records for changes that occur between the hours of 23:00 and 06:00? That's almost all of you. No, I didn't actually have to see you to know how many of you either raised your hands virtually or physically. Don't forget that I live this life of trips to the data center, change windows, change records, service requests, backout plans, and root cause analysis. I've lived it for a very long time – so long in fact, I find myself asking a good question: Why don't we perform changes when we're actually awake and when everyone who can help, if things inevitably go wrong, is awake, too?

Spoiler alert: I am under no delusion that I will change anyone's behavior by stating my observations and opinions here, but at least you'll have considered them as an alternative to the long-established behaviors.

After having already spent at least eight hours on the job, I often have to plan for a change that begins at or near midnight. For mission-critical business applications, databases, and storage, this doesn't appear to be the wisest decision. Wouldn't it make more sense to perform these changes during the day, when you have a fresh and awake staff to do the work? It makes sense to me, especially when data centers are built with redundancy in mind. Isn't that exactly what the purpose of redundancy is?

Supposedly, every system has a failover option – at least from A to B. Routers, switches, storage arrays, power supplies, services, databases, and applications all have redundancy that protects the business from failure should a system fail. Systems fail during the day, too, although it seems like they fail more often in the wee hours of the morning or over a long holiday weekend than they do during the day. We fix them during the day, too, don't we?

I once presented this case to a project manager and an account executive who couldn't argue with the logic, but the answer was still the same from both:

...
Use Express-Checkout link below to read the full article (PDF).

Buy ADMIN Magazine

SINGLE ISSUES
 
SUBSCRIPTIONS
 
TABLET & SMARTPHONE APPS
Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Looking Backward, Looking Forward
    Whatever IT challenges you face in 2025, will you meet them with anger, fear, and indifference – or will you go forward with interest, curiosity, and humility?
  • Dealing with IT Burnout
    I'm not the first writer or the first system administrator to discuss IT job burnout, but I think I have a few ideas to help when it happens to you.
  • Welcome
    The old saying that no one plans to fail, but many fail to plan is true. However, in the complex and ever-evolving field of IT, sometimes all the planning doesn't guarantee success.
  • Artificial Intelligence in Review
    AI might have come a long way since the days of LISP and Prolog, but it's still primitive – and that's OK.
  • Confessions of a Patchaholic

    Managing patches, service packs and updates in a heterogeneous environment is one of the leading causes of sleep deprivation among system administrators. The big question is, “How do you manage patches in a complex environment?”

comments powered by Disqus
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs



Support Our Work

ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.

Learn More”>
	</a>

<hr>		    
			</div>
		    		</div>

		<div class=