disasterAs networks and devices become increasingly complex, more and more things can go wrong. As a result, disaster recovery plans have also become more complex.

Is yours good enough?

According to Jon William Toigo, the author of Disaster Recovery Planning, 15 or 20 years ago a disaster recovery plan might consist of powering down a mainframe and other computers, disassembling components, and drying circuit boards in the parking lot with a hair dryer. That’s because a disaster, in those days, was usually a fire that set off a company’s sprinklers.

Today, there are many more threats, including sabotage. Moreover, most companies’ IT systems are too large to be recovered using such a simple hands-on approach. Even if you could recover from a disaster in the manner Toigo recalls, you probably wouldn’t want to due to the downtime it would require—downtime that could have a significant financial impact.

Consider the case of Hurricane Katrina. When it slammed the U.S. Gulf Coast in 2005, it wiped out the communications infrastructure of a whole region, uprooting 1,000 wireless towers and knocking down 11,000 utility poles. Many businesses were forced to shut down entirely—even critical ones, including 25 hospitals and 100 broadcast stations. But clients of such company did stay in business—by relocating to off-site facilities equipped with the computing power and backed-up data to keep systems and services online. Some even utilized 18-wheelers with servers and other office equipment inside.

Disaster recovery in the modern age is a detailed, step-by-step course of action for quickly getting back on your feet after a natural or manmade disaster. The details may vary depending on your business needs, and can be developed in-house or purchased as a service.

How prepared are you for disaster? Call us today for a review of your plan.

Published with permission from TechAdvisory.org. Source.