Commentary

Howard Marks
 

5 Years Later - Lessons From The Blackout?

Yesterday was the 5th anniversary of the biggest electrical blackout in North American history. Some 50,000,000 people from Ohio to D.C. to Ontario (Canada, not California) were without power for up to four days. The mainstream media is covering the big picture and lessons the power industry can learn to make the grid more resistant to trees knocking down power lines. I wanted to take the opportunity to address the questions this event raises for IT.

Yesterday was the 5th anniversary of the biggest electrical blackout in North American history. Some 50,000,000 people from Ohio to D.C. to Ontario (Canada, not California) were without power for up to four days. The mainstream media is covering the big picture and lessons the power industry can learn to make the grid more resistant to trees knocking down power lines. I wanted to take the opportunity to address the questions this event raises for IT.While I'm not generally a fan of planning for specific disasters, because Murphy's Law says if you prepare for wildfires you'll get hit with mudslides or earthquakes instead, the example of the 2003 blackout does raise some questions your disaster recovery plan will have to address.

First is distance. Various factors, like the effect of distance on network latency, and with synchronous replication and therefore application performance, and the convenience of having someone drive out to the DR site to install a new server or memory upgrade, lead most organizations to keep their DR site within a reasonable driving distance of their primary site. Here in New York that usually means across a river in New Jersey, upstate (yes, for a real New Yorker, White Plains is upstate), or Connecticut. All of which were blacked out.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

So the question comes up, is greater distance -- to, say, Nevada -- worth the cost and trouble?

The second is when to declare a disaster and activate the DR site. The blackout struck New York at 4:11 p.m. on a Thursday. Most New York City locations had power restored by morning. Organizations that didn't activate their DR sites, and being in a NY office tower that didn't have a generator, had to restart their servers. The IT guys either had a really long night or the users had a slow morning.

Those that did activate not only had to limp through Friday running from the DR site, but probably had to spend the weekend failing back from the DR site to their primary systems. The fail-back process is rarely as well-thought-out or tested as the fail over, so I'm sure it was a long weekend for some folks.

Would you have declared a disaster at 4:11? At midnight? Or would you just consider Friday to be like a snow day and postpone the decision till Sunday, knowing blackouts rarely last more than a day?

More important, do you have a process as part of the DR plan?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links