10 Common Disaster Recovery Mistakes

We recently came across this informative disaster recovery article posted by Cisco, and thought it was worth sharing. Written by David Alvarado, Regional Director of Service Delivery at Peak10, provides tips for success when implementing a DR strategy. 

One of the unforgiving truths of disaster recovery David has learned over the last 15 years in the industry is that the success of your recovery depends upon how well you plan – and test – your disaster recovery strategy.

Read about David’s top 10 disaster recovery mistakes below:

Consider preparing for a disaster like getting ready for the Big Game. If you don’t know the rules, how can you play? If you haven’t practiced, how can you expect to succeed? Even though the season is only sixteen games, professional football players spend thousands of hours in preparation. They don’t just look at the playbook and assume everything is going to work out. They practice. They strategize. They test and improve. And the truth is that if they don’t do the work, it shows up on the field where they can’t afford to make mistakes.

Here are some of the important details people often miss when working out a disaster recovery strategy:

1. We don’t need a plan. We have a turnkey solution: Many companies purchase a turnkey DRaaS solution and expect it to protect them. A turnkey solution is designed to do a good job for most situations. It does an excellent job simplifying getting your tier one applications up and running again. However, your business is unique, and it needs to be protected in a unique way. For example, your tier one applications might have dependencies with tier three databases. A working application is of little use when you can’t access the data you need. An effective plan needs to identify these interdependencies and recover accordingly.
2. Our entire business can be operational again in 24 hours: If this is the case, you’re probably spending much more on disaster recovery than you need. For example, your DevTest resources probably don’t need to be back up immediately. Disaster recovery is a process. Critical applications first, then tier two applications within 24 hours, tier three in 72 hours, and so on. Each tier can be handled differently, saving you money on your lower, less essential tiers.
3. We’ve got tier one covered: While lower tier applications don’t need to be up immediately, they do need to be part of your plan. Again, DevTest resources don’t need to be up immediately. If it’s been a week and they’re still down, however, you can’t make updates and this will begin to impact your operations and your customers.
4. We’ve had a comprehensive recovery plan in place for years: Some companies take a “one-and-done” approach to disaster recovery. They put a thoughtful plan in place, knowing they are protected, then forget about it. A robust disaster recovery plan is an evolving plan, one that adapts and changes as your infrastructure changes.
5. My assets in the cloud are safe: Many businesses assume, incorrectly, that their resources in the cloud have automatic disaster recovery protection. If you want your cloud assets protected, you have to implement disaster recovery yourself.
6. All of my data is protected, and that’s enough: If you lose your building, you’re going to lose a lot more than just your data. In fact, you might have to start back up from nothing. Does your plan include contingencies such as securing new computers for all of your employees?
7. We can replace whatever we lose: After a disaster, you have to move fast. But negotiating under pressure isn’t ideal. You’ll pay more when your vendors know you’re desperate. That why it makes sense to establish the relationships you need to help you get back up and running. You’ll always be able to negotiate better pricing and availability before a disaster strikes.
8. We have DR experts on staff to assure a smooth recovery: Sometimes you lose personnel in a disaster. And your disaster recovery plan is worth nothing if there’s no one left who can execute it. Your plan needs to be well-defined, something that a stranger could put in place. Because it might just be a stranger you have to count on.
9. Our operations will be up and running in no time at our backup site: Many recovery plans are great, up to Day 1. Then they begin to falter because they haven’t considered what long term recovery requires. For example, does your plan also include getting back up and running at your primary site? If you operate your business from your recovery infrastructure for too long, you may be forced to declare a second disaster, and that gets expensive.
10. We can restore our business exactly as it was: As disruptive as it is, disaster can be an opportunity. When you move from your recovery site, you don’t have to go back to your original infrastructure. If you’ve been thinking of migrating part or all of your operations to the cloud, this could be the right time. 

If you would like help with sourcing or implementing a successful disaster recovery strategy contact one of our infrastructure experts here.