• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
AWS Summit Stockholm 2014 – T3 – disaster recovery on AWS
 

AWS Summit Stockholm 2014 – T3 – disaster recovery on AWS

on

  • 416 views

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 ...

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.

This session is recommended for attendees who wish to explore options for ensuring the continuity of their business.

Statistics

Views

Total Views
416
Views on SlideShare
416
Embed Views
0

Actions

Likes
1
Downloads
39
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    AWS Summit Stockholm 2014 – T3 – disaster recovery on AWS AWS Summit Stockholm 2014 – T3 – disaster recovery on AWS Presentation Transcript

    • © 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 Jean-Pierre LeGoaller Principal Solutions Architect Amazon Web Services
    • What You Will Learn • Disaster Recovery and Business Continuity • AWS as a platform for DR • Common DR architectures • Backup and restore • Pilot light • Warm Standby • Hot Standby • Customer case study • 8 AWS tools to implement Disaster Recovery • Call to action!
    • Business Continuity
    • Disruptions to Business Continuity Caused by outage of IT infrastructure Affects businesses of all kinds and sizes Can be very expensive
    • Downtime Natural Disaster Security Incidence Equipment Failure Human Error What causes downtime
    • Surviving a Disaster 25% of companies do not reopen after a disaster 43% do not reopen after catastrophic data loss 75% of companies that do not have a business continuity plan fail within 3 years of a natural disaster Source: FEMA (Federal Emergency Management Agency)
    • Conventional Disaster Recovery Sites • High cost • Low ROI • Implemented only for most critical systems • Sometimes scaled down to 50% of production • Systems in a remote region challenging • Costly software licenses based on hardware usage
    • Disaster Recovery on AWS • Unprecedented capabilities to implement DR sites • On Demand hardware capacity • Pay as you go • Cut down DR site cost
    • Global Reach from Your Desktop
    • Common DR architectures Each architecture differs from the other In terms of RTO, RPO and Cost
    • 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
    • Simple to get started Easy starting point for exploring the AWS cloud Low technical barrier to entry Backup & Restore Architecture
    • Lowest cost Very high levels of data durability Low Amazon S3 Cost Tape replacement using Amazon Glacier Backup & Restore Architecture
    • Many Ways to Back Up
    • Back up and Restore Create instances from AMIs Restore data from backups
    • Build resources around replicated dataset Keep ‘pilot light’ on by replicating core databases Build AWS resources around dataset and leave in stopped state Pilot Light Architecture
    • 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
    • Switchover to AWS Make necessary DNS changes to redirect traffic to the DR site on AWS Pilot Light Architecture
    • Pilot Light Architecture
    • Create instances from AMIs Pilot Light Architecture
    • 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 fewer instances than Production. Use RI (Reserved Instances) for capacity reservation and cost saving Warm Standby Architecture
    • 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 fewer instances than Production. Use RI (Reserved Instances) for capacity reservation and cost saving 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
    • Warm Standby Architecture
    • Warm Standby Architecture
    • 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
    • Multi-Site Architecture
    • DR site on AWS can be for • Primary site on customer data center • Set up as part of a migration to AWS • Primary on AWS
    • Open Source Mapping Platform
    • Provide Mapping Services for: • Foursquare • Pinterest • Mozilla • Le Monde • Evernote • Financial Times • USA Today • Hipmunk • National Park Service • NPR • The Washington Post • National Geographic
    • User eu-west-1 (Ireland) us-east-1 (Northern Virginia) us-west-1 (Northern California)us-west-1 (Northern California) DNS Failover + Latency Based Routing
    • User eu-west-1 (Ireland) us-east-1 (Northern Virginia) us-west-1 (Northern California)us-west-1 (Northern California) DNS Failover + Latency Based Routing
    • 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
    • 8 AWS Disaster Recovery Features
    • #1: 10 Isolated AWS regions with multiple Availability Zones US-WEST (N. California) EU-WEST (Ireland) ASIA PAC (Tokyo) ASIA PAC (Singapore) US-WEST (Oregon) SOUTH AMERICA (Sao Paulo) US-EAST (Virginia) Gov Cloud ASIA PAC (Sydney) ASIA PAC (Beijing)
    • Java Python PHP .NET Ruby nodeJS iOS Android AWS Toolkit for Visual Studio AWS Toolkit for Eclipse Tools for Windows PowerShell CLI #2: Cross-region API and SDKs
    • #3: AWS CloudFormation allows quick bootstrap of another region
    • Amazon Route 53 Elastic Load Balancer S3 BucketCloudFront Distribution Web Servers Web Servers Web ASG Elastic Beanstalk App App Master Standby RR 1 RR 2 RR 3 RR 4 ElastiCache Cluster #3: AWS CloudFormation allows quick bootstrap of another region
    • #4: Route 53 latency-based routing and failover
    • #5: Cross-region snapshot copy for Amazon RDS and Amazon EBS
    • #5: Cross-region snapshot copy for Amazon RDS and Amazon EBS
    • #6: Cross-region read-replicas for Amazon RDS MySQL
    • #7: Elastic Data Pipeline
    • #8 Auto-Scaling
    • No DR Strategy yet?
    • Act: 5 reasons to implement DR on AWS 1. Having a DR strategy is critical to the survival of your business 2. DR is an ideal use case for AWS pay-as-you-go pricing model 3. With AWS, cost is not an excuse any longer 1. AWS provides numerous tools to make DR easier 2. DR is great way to get started with AWS
    • © 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 Thanks! Jean-Pierre LeGoaller Principal Solutions Architect Amazon Web Services