Early September 2013 saw the US state of Colorado hit by enormous floods that resulted in tragic deaths, towns cut off, and thousands of people displaced from their homes.
Meanwhile, the rain and the subsequent breaching of riverbanks caused serious outages in key infrastructure, including electricity supplies and telecoms infrastructures.
The Colorado flood occurred less than a year after “Superstorm” Sandy caused similar destruction in New York State.
Natural disasters such as these cause justifiable concern amongst technical professionals, making them wonder if the disaster recovery provisions they have in place would work adequately if they were caught up in a similar incident.
One key detail that has emerged in the aftermath of the Colorado disaster is the fact that not that many businesses suffered physical damage to their internal infrastructures. The main impact was on core public infrastructure. Internet connections died, power went off, and even the cellphone network failed to cope.
This all goes to show that the procedural planning for disaster recovery is just as important as the technical provisioning, if not more important. Different disasters have completely different profiles, and a localized flood in just one building would present a completely different set of challenges to a natural disaster.
So, if you are an MSP involved in disaster recovery planning for your customers, what lessons should you learn from the Colorado floods? We would suggest the following:
Disaster recovery often falls too far down a client’s list of priorities. If a client fails to plan and ends up in a disaster situation, it’s sure to prove equally stressful for you as the MSP. Don’t let this happen!