Q
Get started Bring yourself up to speed with our introductory content.

What should an AWS cloud disaster recovery plan contain?

Now that we're moving applications into AWS, how should our cloud disaster recovery plan differ from a traditional on-premises DR strategy?

Organizations that depend completely on public cloud providers, such as Amazon Web Services, need to create and...

implement a comprehensive cloud disaster recovery plan for mission-critical workloads. If not, service disruptions from outages can result in user dissatisfaction and potential financial loss. There are familiar tactics that enterprise IT can use to help improve disaster recovery for public cloud.

Often, problems arise because organizations assume a level of provider reliability that doesn't exist. Businesses sometimes underestimate or forget the effect a few hours of downtime can have -- and never adequately prepare a disaster recovery (DR) plan. Take the time to identify mission-critical applications that reside on premises or in the cloud, and ask what happens to the business if those applications go down.

Don't ignore the importance of testing after implementing a cloud disaster recovery plan. Many organizations never check to ensure that the DR strategy works. Implement a regular testing regime to ensure that failover and failback activities work and can adequately handle the user load. In-house testing scenarios include user error recovery to retrieve lost data, lost connectivity to a site and power loss to a site.

Organizations that fully depend on the public cloud may be limited in testing scenarios, but they can still invoke traffic failover to gauge AWS Auto Scaling response and performance. Testing is also a perfect time to work with any monitoring and alerting tools, as well as verify that personnel are adequately informed, and tickets are generated and addressed as expected.

Finally, treat DR as an ongoing process rather than a static, one-time project. Revisit and re-evaluate the DR strategy several times per year. This is an ideal time to measure DR and any response to inevitable changes taking place across the business and the public cloud. For instance, a cloud provider may offer new services, regions or availability zones. All of these can offer opportunities to improve a cloud disaster recovery plan while staying within an established budget. In addition, compliance requirements may change, so review which AWS region is best.

No application is 100% available 100% of the time. Public cloud and telecom providers experience occasional disruptions, resulting in potential service disruptions. Every organization with workloads in the public cloud must expect availability problems and implement a suitable cloud disaster recovery plan to remain flexible and respond accordingly.

Next Steps

Three causes of cloud failure

Reliability trumps risk of AWS outages

Create your cloud DR plan

This was last published in October 2015

Dig Deeper on AWS disaster recovery

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Join the conversation

6 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

How often do you test your AWS cloud disaster recovery plan?
Cancel
>We test all of our Dr plans, whether AWS or on-prem, quarterly at a minimum.
Cancel
Hi, mcorum--

Quarterly is great--and pretty impressive, too! In one of our recent TechTarget/SearchDisasterRecovery surveys we asked companies how often they tested their DR plans. Here are the results:

No specific schedule - 29%
Once a year - 26%
Twice a year - 19%
Once a quarter - 17%
Once a month - 5%
Never - 4%

So, you can see that as quarterly testers you're in an elite segment. Congratulations!

Cancel
There are a lot of good resources located on that page. Thanks for sharing, Rich!
Cancel
My pleasure--glad you're finding it useful. I don't know where all those spaces came from in my last post, but at the least the data is there.
Cancel
It just seems like common sense that an organization would test a DR plan, cloud-based on not, after implementing it. It’s one thing to assume that your car will start in the morning and have it not start than it is to assume that your DR plan for business critical applications works and then find out it doesn’t. 
Cancel

-ADS BY GOOGLE

SearchCloudApplications

TheServerSide.com

SearchSoftwareQuality

SearchCloudComputing

Close