Creating a disaster plan for your business is a great idea. It is a way to restore your business and its operations faster than if no such plan existed. Making those plans in a hurry, or never testing them to determine their practicality, could be a serious mistake you want to avoid. Here are some more mistakes made all too often in the disaster recovery plan creation process.
Failing to Create a Priority List
The goal of a disaster recovery plan is to be able to get the IT department back online as quickly as possible, and to minimize the data loss. Various recovery strategies need to be established, but a company must first determine what kind of information and how much is needed to restore essential operations. This evaluation needs to be performed because departments have limited resources during or after a crisis, and these resources need to be directed toward first recovering key data. Other non-critical information can wait.
Failure to Consider Multiple Types of Disasters
Making plans for one or two types of disasters is limited vision. Today, there are possibly many different types of things that could go wrong. Each type needs to be considered and planned for, because different actions will be needed. Problems that may be encountered include power failure, nuclear or radiation accidents, fires, civil unrest, terrorist acts, earthquake, bioterrorism, tornado or hurricane, flood, landslide, and more. While some of these may only be local, some may be regional, and plans need to be made for each of these potential problems.
Not Cross-Training Key People
The State of Oregon, for its state records, requires that all people who need to be involved should be part of the emergency planning processes. Then, they should be cross-trained in all of the recovery processes. The cross-training is an important step in case not all key people are available to aid in the actual disaster recovery process.
Not Considering the Budget
While some service providers make promises about being always on, it just is not true. If the components involved are not kept up to date, or able to handle the workload, what often occurs is that not all data actually falls under the high-availability (HA) capabilities of the new technology. It results in backups and accessibility not always being delivered as promised. Testing is required to ensure the quality of backups and to watch the budget.
Don’t Try to Restore All Data at Once
If you use a cloud service provider, it is important to only restore limited data for basic operations, and not all of it. If your company has uploaded 10 TB over the years, it will take more than a year to restore it if you do it over a T1 network. A better idea is to use different technologies to store backup data on, and recover it slowly as necessary. This also makes it essential to ensure that the cloud company actually has all the features it claims to possess.