Embed Size (px)
DESCRIPTION
Everything You Need to Build DR into Your Application Stack. Learn what Cloud DR is (and is not), and how to prevent downtime in public cloud environments. Learn about: • DR Overview and terminology • Building DR into your cloud strategy • Calculating cost of downtime • Selecting the right DR approach • Disaster planning, management, testing and post-mortem
Citation preview
Solving the problem of downtime in the cloud
AWS Cloud Disaster Recovery Crash Course
Welcome
Today’s Panelist
Leonid FeinbergVP ProductCloudEndure
Housekeeping
Questions for Speaker?Submit questions via the Questions tab during the webinar. We will address them at the end
Your line is muted
Twitter Hashtag: #CloudEndureWebinar
Following the webinar, you will be able to access the recorded webinar / slides
Founded: 2012 Offers Disaster Recovery and
Migration to, across, and between multiple cloud locations
Using Continuous Replication of your Entire Application Stack
Source: Forrester
About CloudEndure
Some Of Our Customers
Agenda
DR 101 – Definitions and Terminology Building DR into your cloud strategy Calculating cost of downtime Selecting the right DR approach Disaster planning, management, testing and post-mortem Q&A
Disaster Recovery in 30 Words
Disaster recovery (DR) is the process, policies and procedures that are related to preparing for recovery or continuation of
technology infrastructure which are vital to an organization after a natural or human induced
crisis
DR Key Terminology
RPO – Recovery Point Objective – The maximum tolerable period in which data might be lost.
RTO – Recovery Time Objective - The duration of time and a service level within which a business process must be restored after a disaster (or disruption) in order to avoid unacceptable consequences.
Data replication – sharing information so as to ensure consistency between redundant resources.
DR – What it’s not
Unlike Backup, which is mostly about data loss prevention, DR is about service availability - low RPO and RTO.
DR complements other High Availability activities, but while those deal with disaster prevention, DR is for those times when the preventions failed.
Why DR?
54% of Cloud IT Managers experienced an outage in the past 3 months
Top challenges in meeting availability goals: Insufficient IT resources, Budget limitations, Software Bugs
79% reports a service availability goal of “Three Nines” (99.9%)
Source: 2014 Cloud Disaster Recovery Survey
Available for download in the “Resources” tab of the webinar
Vote: When was your last downtime?
How The Cloud Can Help For DR
Flexible
Define different recovery objectives for different components and change them on the fly. You can grow and shrink your disaster site whenever necessary (even automatically).
Cheap
Pay for hourly usage of resources. Only create your disaster site when it’s needed. Don’t pay for two running sites all the time
Easy
DR and HA made easier – No need to build your DR solution from scratch.
Cost of Downtime
Revenue Loss
Cost of lost employee productivity
Cost of IT Recovery
Projected loss of revenue due to customer loyalty
Projected loss of revenue due to damage to reputation
Cloud Disaster Recovery Approaches
Hot Standby – Always ready for immediate failover
Warm Standby – Ready for immediate failover, but not in full scale
Pilot Light – Partially ready for failover Cold Standby – Creates the entire failover
application on demand
Disaster Recovery Takeaways
Carefully plan you disaster recovery. Every application may need different RPO and RTO and thus a different Disaster Recovery solution.
Re-visit your Disaster Recovery plan periodically. Assumptions that were correct at the time of the original planning may no longer be correct right now.
Test, test and test again. The cloud lets you test your Disaster Recovery plan as frequently as you need without interrupting your operation.
Constantly improve your plan. whether it’s a disaster you experienced or someone else did, try to learn as much as you can to make sure that when you have the next disaster, you are better prepared for it.
