0
© 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or i...
What You Will Learn
• Disaster Recovery and Business Continuity
• Why AWS for disaster recovery?
• Common DR architectures...
Disruptions to Business Continuity
Caused by outage of IT infrastructure
Affects businesses of all kinds and sizes
Can be ...
Downtime
Natural
Disaster
Security
Incidence
Equipment
Failure
Human
Error
What causes downtime
Conventional Disaster Recovery Sites
• High cost
• Low ROI
• Implemented only for most critical systems
• Usually scaled d...
Disaster Recovery on AWS
• Unprecedented capabilities to implement DR sites
• Easily set up DR sites on different geograph...
Global Reach from Your Desktop
Tools for Implementing DR on AWS
• Leverage tools like CloudForamtion to automate deployment.
• Choose an AMI strategy tha...
AWS Storage Options
Simple Storage Service
Highly scalable object storage
1 byte to 5TB in size
99.999999999% durability
E...
Common DR architectures
Each architecture
differs from the other
In terms of RTO, RPO and Cost
Simple to get started
Easy starting point for exploring the AWS cloud
Low technical barrier to entry
Focus on incorporatin...
Back up and restore
Create
instances
from AMIs
Restore data
from backups
Many Ways to Back Up
Backup & Restore Considerations
• Make sure you keep your AMIs current
• Use CloudFormation or other automation tools
• Co...
Build resources around
replicated dataset
Keep ‘pilot light’ on by replicating core
databases
Build AWS resources around d...
Pilot Light Architecture
Create
instances from
AMIs
Pilot Light Architecture
Activating a Pilot Light DR Site
• Use CloudFormation and Auto-Scaling to stage infrastructure.
• Keep your AMIs or bootst...
Build a environment similar to
production at a reduced scale
Keep data and files synchronized between
production and DR si...
Warm Standby Architecture
Warm Standby Architecture
Moving Warm Standby to Production
• Use CloudFormation and Auto-Scaling to resize infrastructure.
• Leverage EC2 heavy uti...
Build DR site as mirror image of Production
Keep all data and files synchronized between production and DR site by
synchro...
Load balance between
production and DR
If latency and error propagation risk
between production and DR sites are
acceptabl...
Multi-site Architecture
DR site on AWS can be for
• Primary site on customer data center
• Primary on AWS itself
Primary and DR Sites on AWS
What enabled this?
• Eight isolated S3 regions
• AWS CloudFormation allows quick bootstrap of
another region.
• Route 53 l...
User in San
Francisco
eu-west-1 (Ireland)
us-east-1 (Northern Virginia)
us-west-1 (Northern California)us-west-1 (Northern...
What didn’t go wrong
• Official NYC evacuation map stayed up
• USA TODAY Weather map stayed up
• Thousands of other maps u...
© 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or i...
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency
Upcoming SlideShare
Loading in...5
×

Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency

745

Published on

Implementation of a disaster recovery (DR) site is crucial for the business continuity of any enterprise. Due to the fundamental nature of features like elasticity, scalability, and geographic distribution, DR implementation on AWS can be done at 10-50% of the conventional cost. In this session, we do a deep dive into proven DR architectures on AWS and the best practices, tools and techniques to get the most out of them.

Published in: Technology, Business
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
745
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
79
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Transcript of "Disaster Recovery Sites on AWS: Minimal Cost, Maximum Efficiency"

  1. 1. © 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.© 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc. Disaster Recovery Site on AWS: Minimal Cost Maximum Efficiency Ryan Holland, AWS July 10, 2014
  2. 2. What You Will Learn • Disaster Recovery and Business Continuity • Why AWS for disaster recovery? • Common DR architectures • Backup and restore • Pilot light • Warm Standby • Hot Standby • Customer case study • Where to go next
  3. 3. Disruptions to Business Continuity Caused by outage of IT infrastructure Affects businesses of all kinds and sizes Can be very expensive
  4. 4. Downtime Natural Disaster Security Incidence Equipment Failure Human Error What causes downtime
  5. 5. Conventional Disaster Recovery Sites • High cost • Low ROI • Implemented only for most critical systems • Usually scaled down to 50% of production • Systems in a remote region challenging • Costly software licenses based on hardware usage
  6. 6. Disaster Recovery on AWS • Unprecedented capabilities to implement DR sites • Easily set up DR sites on different geographic regions • Cut down DR site cost by up to 70% • Substantial savings on software licenses
  7. 7. Global Reach from Your Desktop
  8. 8. Tools for Implementing DR on AWS • Leverage tools like CloudForamtion to automate deployment. • Choose an AMI strategy that fits the RTO requirements. • Cross-region EBS snapshot and AMI copy • Cross-region read replicas for Amazon RDS for MySQL • Amazon Route53 and Auto Scaling • EC2 reserved instances
  9. 9. AWS Storage Options Simple Storage Service Highly scalable object storage 1 byte to 5TB in size 99.999999999% durability Elastic Block Store High performance block storage device 1GB to 1TB in size Mount as drives to instances with snapshot/cloning functionalities Glacier Long term object archive Extremely low cost per gigabyte 99.999999999% durability
  10. 10. Common DR architectures Each architecture differs from the other In terms of RTO, RPO and Cost
  11. 11. Simple to get started Easy starting point for exploring the AWS cloud Low technical barrier to entry Focus on incorporating cloud into your DR strategy, not on complex technical issues related to hot-hot systems Lowest cost Very high levels of data durability at low price Cost of storing snapshots in Amazon S3 Archiving possibilities beyond tape using Amazon Glacier Backup & Restore Architecture
  12. 12. Back up and restore Create instances from AMIs Restore data from backups
  13. 13. Many Ways to Back Up
  14. 14. Backup & Restore Considerations • Make sure you keep your AMIs current • Use CloudFormation or other automation tools • Consider EC2 light utilization reserved instances • Test your DR plan frequently. Then test some more.
  15. 15. Build resources around replicated dataset Keep ‘pilot light’ on by replicating core databases Build AWS resources around dataset and leave in stopped state Scale resources in AWS in response to a DR event Start up pool of resources in AWS when events dictate Scale up the database instance to handle production capacity Pilot Light Architecture
  16. 16. Pilot Light Architecture
  17. 17. Create instances from AMIs Pilot Light Architecture
  18. 18. Activating a Pilot Light DR Site • Use CloudFormation and Auto-Scaling to stage infrastructure. • Keep your AMIs or bootstrapping scripts current. • Leverage EC2 heavy utilization reserved instances for the database • Test your DR plan frequently. Then test some more.
  19. 19. Build a environment similar to production at a reduced scale Keep data and files synchronized between production and DR site by replication Use smaller and/or fewer instances than Production. Scale resources in AWS in response to a DR event Scale out the environment by adding more instance Scale up the instances to handle production capacity Warm Standby Architecture
  20. 20. Warm Standby Architecture
  21. 21. Warm Standby Architecture
  22. 22. Moving Warm Standby to Production • Use CloudFormation and Auto-Scaling to resize infrastructure. • Leverage EC2 heavy utilization reserved instances for the database and the warm standby instances. • Test your DR plan frequently. Then test some more.
  23. 23. Build DR site as mirror image of Production Keep all data and files synchronized between production and DR site by synchronous replication if possible Pick the size and number of instances based on acceptable level of performance without any change in case of a DR event. Use RI (Reserved Instances) for capacity reservation and cost saving Multi-site Architecture
  24. 24. Load balance between production and DR If latency and error propagation risk between production and DR sites are acceptable Multi-site Architecture If DR site is isolated then Switch over to AWS Make necessary DNS changes to redirect traffic to the DR site on AWS
  25. 25. Multi-site Architecture
  26. 26. DR site on AWS can be for • Primary site on customer data center • Primary on AWS itself
  27. 27. Primary and DR Sites on AWS
  28. 28. What enabled this? • Eight isolated S3 regions • AWS CloudFormation allows quick bootstrap of another region. • Route 53 latency based routing and failover
  29. 29. User in San Francisco eu-west-1 (Ireland) us-east-1 (Northern Virginia) us-west-1 (Northern California)us-west-1 (Northern California) DNS Failover
  30. 30. What didn’t go wrong • Official NYC evacuation map stayed up • USA TODAY Weather map stayed up • Thousands of other maps used for weather reporting, data visualization and coordination around the event all stayed up
  31. 31. © 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.© 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc. Disaster Recovery Site on AWS: Minimal Cost Maximum Efficiency Ryan Holland, AWS Thank you!
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×