Did your answer in any way involve technology? This blog series confronts that misconception and explains the why and how of a proper disaster recovery plan.
Disaster Recovery (DR) plans are the single most annoying thing that most IT people handle. It is an absolutely massive amount of work, most of which isn’t actually doing IT tasks like setting up servers or configuring software. DR planning is all about documentation: how to recover things, what order to recover things, and trying to explain things in ways that a lay person can understand. The annoyance goes even further because the responsible administrator knows how to do all of this without even thinking about it and it is the ultimate goal that all this work will never be used in any way.
Due to this extreme annoyance, most companies don’t have DR plans or have horribly inadequate plans. The risk from this kind of behavior can’t be understated. One in four businesses fail after a disaster because there is no safeguard in place to recover the data lost. IT is vital to almost every business in modern times. Even the least technical company uses email, phones, and some form of accounting program. Many companies have deep investments in enterprise resource planning systems where the business literally can’t function if the IT infrastructure is down.
It is the responsibility of the administrator to ensure that the company doesn’t go out of business due to an IT disaster. The rest of this series will explain the key tenets and steps towards creating an accurate and useful DR plan and answer that original question, what’s the most important part of DR planning?