Disaster Recovery with AWS - Simone Brunozzi - AWS Summit 2012 Australia -
•
1 like•1,931 views
Simone Brunozzi gave a presentation on implementing disaster recovery strategies using AWS cloud services. He discussed how AWS can be used to backup and restore data, maintain a pilot light architecture where core systems are replicated in AWS, and implement warm standby or multi-site solutions. Key benefits of AWS for DR include reduced infrastructure costs, ability to easily scale resources, pay only for what is used, and high security. Common architectures patterns like backup/restore, pilot light, warm standby and multi-site solutions were covered along with relevant AWS services.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (9)
Similar to Disaster Recovery with AWS - Simone Brunozzi - AWS Summit 2012 Australia -
Similar to Disaster Recovery with AWS - Simone Brunozzi - AWS Summit 2012 Australia - (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
Disaster Recovery with AWS - Simone Brunozzi - AWS Summit 2012 Australia -
- 1. AWS Summit 2012 | Sydney Disaster Recovery with the AWS Cloud by Simone Brunozzi Technology Evangelist, APAC Twitter: @simon 1:45pm
- 2. Today’s Agenda If a cloud-based DR strategy is right for you How to implement some common DR architectures The AWS services that can be used How to get started © 2012 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.
- 3. You might be able to: Slash parts of your DR budget by 50% Eliminate 30%+ of your on premises IT footprint Eliminate your need for physical secondary site(s) Eliminate tape for backup and archive © 2012 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.
- 4. First poll question: Do we really know what Disaster Recovery means? © 2012 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.
- 5. Let’s start with where DR fits into your plans High Backup Disaster Availability Storage Recovery It’s part of a business continuity continuum It’s not an all or nothing proposition In the face of internal or external events, how do you… • Keep your applications running 24x7 • Make sure you data is safe • Get an application back up after a major disaster © 2012 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.
- 6. Disaster recovery on the continuum Recover from any event (small to large scale) Recovery Time Objective (RTO) Recovery Point Objective (RPO) Business Continuity / Incident Management timelines © 2012 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.
- 7. Question: Do we really know how frequently disasters occur? © 2012 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.
- 9. Frequency Murphy’s law the “human” factor © 2012 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.
- 10. Disaster recovery on the continuum Traditional IT model has DR in a second physical site • Low end DR: off-site backups • High end DR: hot site active-active architecture © 2012 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.
- 11. AWS is used for DR in a variety of ways Enterprise Fast, secure, cost effective backup and application backup DR for Oracle apps and DR DR for regulated Reducing cost of vaulting and DR industries implementations by up to 50% Oracle E-business Suite DR and dev/ IT and Operations are more responsive to the business test Hot site DR for Avoiding $1M of infrastructure and enterprise clients admin costs © 2012 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.
- 12. Here’s why you save with AWS as the 2nd site Site 1 (data center): Site 2 (AWS): Routers Routers Firewalls Firewalls IP Network IP Network Application Licenses Application Licenses Operating Systems Operating Systems Hypervisor Hypervisor Servers Servers Storage Network Storage Network Snapshot storage Primary Storage Primary Storage Backup SW Backup SW Backup Tapes Backup Tapes Tape Silos Tape Silos Archive SW Archive SW Archive Storage Archive Storage © 2012 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.
- 13. Question: If you are planning an implementation, how would you go about it? My answer: AWS in DR scenarios © 2012 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.
- 14. Our infrastructure is global AWS Regions AWS Edge Locations © 2012 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.
- 15. Data on our infrastructure is durable © 2012 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.
- 16. AWS is built for enterprise security standards Certifications Physical Security HW, SW, Network SOC 1 Type 2 Datacenters in nondescript Systematic change (formerly SAS-70) facilities management ISO 27001 Physical access strictly Phased updates deployment controlled PCI DSS for EC2, S3, EBS, Safe storage decommission VPC, RDS, ELB, IAM Must pass two-factor authentication at least twice Automated monitoring and FISMA Moderate Compliant for floor access self-audit Controls Physical access logged and Advanced network protection HIPAA & ITAR Compliant audited Architecture © 2012 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.
- 17. These are some relevant AWS services Amazon Simple Storage Service (Amazon S3) Amazon Import/Export Amazon Elastic Compute Cloud (Amazon EC2) AWS Storage Gateway Amazon Route 53 © 2012 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.
- 18. AWS storage is ideal for backup and DR Amazon Simple Storage Service (Amazon S3) • Highly durable blob storage • Excellent for backup and archive Amazon Elastic Block Store (Amazon EBS) and EBS snapshots • Persistent data volumes for Amazon EC2 instances • Redundant within a single Availability Zone • Snapshot backups provide long term durability, and volume sharing / cloning capability within a Region © 2012 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.
- 19. The Cloud Scales: Amazon S3 Growth 762 Billion Peak Requests: 500,000+ per second 262 Billion 102 Billion 14 Billion 40 Billion 2.9 Billion Q4 2006 Q4 2007 Q4 2008 Q4 2009 Q4 2010 Q4 2011 Total Number of Objects Stored in Amazon S3 © 2012 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.
- 20. You have several networking alternatives Amazon S3 10G Bucket Corporate data center Using AWS Direct Connect Over the Internet Amazon Elastic Compute Cloud (EC2) Availability Zone AWS Import/Export On-site infrastructure AWS Region © 2012 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.
- 21. The AWS Storage Gateway © 2012 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.
- 22. A few things about AWS networking & security AWS Direct Connect Amazon Virtual Private Dedicated Instances Cloud (VPC) Single Tenant Compute Instance Internet Dedicated connection between Private VPN connection to Amazon EC2 resources running your datacenter and AWS your AWS resources on private hardware © 2012 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.
- 23. Common architecture patterns © 2012 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.
- 24. There are two main approaches to recovery Starting from AWS • Implement a high availability architecture • Implement a disaster recovery strategy • Rapidly restore and failover within AWS • Implement a high availability architecture Starting from your • Implement a disaster recovery strategy Data Center • Use backed up data to run analytics in AWS • Rapidly restore from AWS to on-premises • Rapidly failover to AWS while restoring on-premises © 2012 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.
- 25. There are four common architecture patterns Backup and Pilot light for quick recovery Restore into AWS Warm standby solution Multi-site solution deployed in AWS on AWS and on-site © 2012 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.
- 26. Let’s start with Backup and Restore Backup and Pilot light for quick recovery Restore into AWS Warm standby solution Multi-site solution deployed in AWS on AWS and on-site © 2012 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.
- 27. About the Backup and Restore pattern Advantages to simple Backup and Restore • Simple to get started • Extremely cost effective (mostly backup storage) The preparation phase • Take backups of current systems • Store backups in Amazon S3 • Describe procedure to restore from backup on AWS © 2012 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.
- 28. Back up data to Amazon S3 Amazon Route 53 Data copied to S3 Traditional server S3 Bucket with Objects AWS Import/ Export On-premises Infrastructure © 2012 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.
- 29. What you’d do in case of disaster Retrieve backups from Amazon S3 Bring up required infrastructure Restore system from backup Switch over to the new system or © 2012 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.
- 30. This is what restoring to AWS looks like Amazon EC2 Instance Data copied from objects in S3 Data Volume Instance Quickly provisioned from Amazon S3 AMI Bucket Pre-bundled with OS and applications AMI Availability Zone AWS Region © 2012 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.
- 31. Now let’s look at the Pilot Light architecture Backup and Pilot light for quick recovery Restore into AWS Warm standby solution Multi-site solution deployed in AWS on AWS and on-site © 2012 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.
- 32. About the “Pilot Light” architecture pattern Automatically bring up AWS resources around the replicated core data set Scale the system as needed to handle current production traffic Switch over to the new system in AWS © 2012 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.
- 33. Pilot Light in Non-DR Phase User or system Web Web Server Server Amazon Route 53 Not Running Application Application Server Server Database Database Smaller Instance Server Data Mirroring/ Server Replication Data Data Volume Volume © 2012 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.
- 34. Pilot Light in Disaster Phase User or system Web Web Server Server Amazon Route 53 Not Running Application Application Server Server Database Database Smaller Instance Server Server Data Data Volume Volume © 2012 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.
- 35. Pilot Light in Recovered Phase User or system Web Web Server Server Amazon Route 53 Start in Minutes Application Application Server Server Database Database Resize Instance Server Server to prod’n capacity Data Volume Data Volume © 2012 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.
- 36. Wrap up © 2012 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.
- 37. Let’s review the main benefits to DR with AWS Durable Reduced Pay Only for Infrastructure What You Use Recover Easy Distribution Easily Scale Up Security and Spin Down Deploy © 2012 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.
- 38. Many solution provider partners you can work with © 2012 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.
- 39. Here’s where you can get more information Slides http://www.slideshare.net/AmazonWebServices Webinars http://aws.amazon.com/resources/webinars Videos http://www.youtube.com/user/AmazonWebServices Website http://aws.amazon.com AWS Disaster Recovery page http://aws.amazon.com/ disaster-recovery Blog http://aws.typepad.com White papers http://aws.amazon.com/whitepapers Partners https://aws.amazon.com/solution-providers © 2012 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.
- 40. Many backup/DR webinars online: Check out: http://aws.amazon.com/storagegateway © 2012 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.
- 41. Third poll question: Are you more inclined to DR with the Cloud? © 2012 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.
- 42. Thank You! Disaster Recovery with the AWS Cloud by Simone Brunozzi Technology Evangelist, APAC Twitter: @simon
Editor's Notes
- \n
- \n
- \n
- On your own\nBringing on a full time consultant\nWith an ISV solution\nWith a system integrator\n
- So let’s start with where DR fits into your continuity plans overall. It’s part of a business continuity continuum. And I’d like to point out that implementing DR is not an all or nothing proposition – you can work your way across the continuum, and today we’ll discuss some of the things to consider and how AWS can play a part. \n\nThe starting point is usually thinking about how to keep you applications up and running. You’ll have a requirement in the form of how many nines of reliability you need, keeping in mind that every nine you add after the first few add a lot of cost, often around 10x for each additional nine. \n\nThe next thing you’re likely to plan for is how to backup your data so it’s safe and available to you in the event of a disaster. How do you store your data so it’s durable and available when you need it. \n\nAnd then you need to have a plan for what to do in the unlikely event that you have one of those black swan events where a true disaster occurs. How do you deal with recovery? \n
- Disaster recovery is at one end of that continuum, and how you choose to implement your DR is influenced by your requirements with a couple of things:\nHow long you’re able to be down; and that’s your Recovery Time Objective, or RTO\nHow much data you can tolerate losing, or how in synch does your backup data have to be with what you have in your operating environment. That’s your Recovery Point Objective, or RPO\n\nbusiness continuity timeline usually runs parallel with an incident management timeline\n\nThese are not technological things, these are business considerations. The easy answer is to have the RTO be minutes and the RPO no data loss, but that’s likely to be much more expensive than is feasible. And chances are you don’t need to be that stringent. \nSo now you can start analyze the trade-offs between the cost of achieving various recovery times and data restore. \n\nAnd you start to think about the requirements for different types of outages – say from restoring a file that was accidentally deleted through to how to handle a complete system outage due to a natural disaster. \n\nA common path to the cloud is to start with backup and recovery plans using the cloud for your backups, and then identify the applications that are candidates for you to implement a full DR plan with in the cloud. Any app that you can run in the cloud is low hanging fruit. Replicating the full stack would be at the more complex and involved end of the scale. \n\nSo you have a lot of flexibility in how you approach the solution that fits you best, and we are going to talk about what some of those architectures look like and how you can implement them.\n\n
- On your own\nBringing on a full time consultant\nWith an ISV solution\nWith a system integrator\n
- \n
- On your own\nBringing on a full time consultant\nWith an ISV solution\nWith a system integrator\n
- Disaster recovery is at one end of that continuum, and how you choose to implement your DR is influenced by your requirements with a couple of things:\nHow long you’re able to be down; and that’s your Recovery Time Objective, or RTO\nHow much data you can tolerate losing, or how in synch does your backup data have to be with what you have in your operating environment. That’s your Recovery Point Objective, or RPO\n\nbusiness continuity timeline usually runs parallel with an incident management timeline\n\nThese are not technological things, these are business considerations. The easy answer is to have the RTO be minutes and the RPO no data loss, but that’s likely to be much more expensive than is feasible. And chances are you don’t need to be that stringent. \nSo now you can start analyze the trade-offs between the cost of achieving various recovery times and data restore. \n\nAnd you start to think about the requirements for different types of outages – say from restoring a file that was accidentally deleted through to how to handle a complete system outage due to a natural disaster. \n\nA common path to the cloud is to start with backup and recovery plans using the cloud for your backups, and then identify the applications that are candidates for you to implement a full DR plan with in the cloud. Any app that you can run in the cloud is low hanging fruit. Replicating the full stack would be at the more complex and involved end of the scale. \n\nSo you have a lot of flexibility in how you approach the solution that fits you best, and we are going to talk about what some of those architectures look like and how you can implement them.\n\n
- \n
- We’re often asked how it is that some customers are able to reduce costs as dramatically as the claims I made earlier, while still getting the recovery performance they need. That’s a great question so I’ll take a minute to point out in simple terms one of the ways that can be accomplished. \n\n[talk to the slide]\n
- On your own\nBringing on a full time consultant\nWith an ISV solution\nWith a system integrator\n
- AWS has eight Regions, and each Region is a separate cloud. This gives our customers complete control over where data is stored, and a lot of options for where to host your disaster recovery site. You are literally a few mouse clicks away from deploying across the globe. This is a lot easier than doing that with off-site tape backup, your own data centers or CoLos. \n
- Slide notes:\nYou can choose to deploy and run your applications in multiple physical locations within the AWS cloud. Amazon Web Services are available in geographic Regions. When you use AWS, you can specify the Region in which your data will be stored, instances run, queues started, and databases instantiated. For most AWS infrastructure services, including Amazon EC2, there are eight regions: US East (Northern Virginia), US West (Northern California), EU (Ireland), Asia Pacific (Singapore) and Asia Pacific (Tokyo), AWS GovCloud (US), US West (Oregon), and South America (Sao Paulo).\n\nWithin each Region are Availability Zones (AZs). Availability Zones are distinct locations that are engineered to be insulated from failures in other Availability Zones and provide inexpensive, low latency network connectivity to other Availability Zones in the same Region. By launching instances in separate Availability Zones, you can protect your applications from a failure (unlikely as it might be) that affects an entire zone. Regions consist of one or more Availability Zones, are geographically dispersed, and are in separate geographic areas or countries. The Amazon EC2 service level agreement commitment is 99.95% availability for each Amazon EC2 Region.\n
- With AWS, you’ll see that the same security isolations are employed as would be found in a traditional data center. These include physical data center security, separation of the network, isolation of the server hardware, and isolation of storage. AWS customers have control over their data: they own the data, not us; they can encrypt their data at rest and in motion, just as they would in their own data center. \n
- \n
- \n
- Our customers continue to make very heavy use of Amazon S3. We now process up to 500,000 S3 requests per second. Many of these are PUT requests, representing new data that is flowing in to S3. As of the end of the fourth quarter of 2011, there are 762 billion (762,000,000,000) objects in S3. \n
- \n
- \n
- AWS Direct Connect makes it easy to establish a dedicated network connection from your premise to AWS. Using AWS Direct Connect, you can establish private connectivity between AWS and your datacenter, office, or colocation environment, which in many cases can reduce your network costs, increase bandwidth throughput, and provide a more consistent network experience than Internet-based connections. AWS Direct Connect lets you establish a dedicated network connection between your network and one of the AWS Direct Connect locations. Using industry standard 802.1q VLANs, this dedicated connection can be partitioned into multiple logical connections. This allows you to use the same connection to access public resources such as objects stored in Amazon S3 using public IP address space, and private resources such as Amazon EC2 instances running within an Amazon Virtual Private Cloud (VPC) using private IP space, while maintaining network separation between the public and private environments. Logical connections can be reconfigured at any time to meet your changing needs. http://aws.amazon.com/directconnect/\n\nAmazon Virtual Private Cloud (Amazon VPC) lets you provision a private, isolated section of the Amazon Web Services (AWS) Cloud where you can launch AWS resources in a virtual network that you define. With Amazon VPC, you can define a virtual network topology that closely resembles a traditional network that you might operate in your own datacenter. You have control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways. You can easily customize the network configuration for your Amazon VPC. For example, you can create a public-facing subnet for your webservers that has access to the Internet, and place your backend systems such as databases or application servers in a private-facing subnet with no Internet access. You can leverage multiple layers of security, including security groups and network access control lists, to help control access to Amazon EC2 instances in each subnet. Additionally, you can create a Hardware Virtual Private Network (VPN) connection between your corporate datacenter and your VPC and leverage the AWS cloud as an extension of your corporate datacenter. http://aws.amazon.com/vpc/\n\nDedicated Instances are Amazon EC2 instances launched within your Amazon VPC that run hardware dedicated to a single customer. Dedicated Instances let you take full advantage of the benefits of Amazon VPC and the AWS cloud – on-demand elastic provisioning, pay only for what you use, and a private, isolated virtual network, all while ensuring that your Amazon EC2 compute instances will be isolated at the hardware level. You can easily create a VPC that contains dedicated instances only, providing physical isolation for all Amazon EC2 compute instances launched into that VPC, or you can choose to mix both dedicated instances and non-dedicated instances within the same VPC based on application-specific requirements. http://aws.amazon.com/dedicated-instances/\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Advantages to simple Backup and Restore\n Simple to get started\n Extremely cost effective (mostly backup storage)\nPreparation Phase\n Take backups of current systems\n Store backups in S3\n Describe procedure to restore from backup on AWS\n Know which AMI to use, build your own as needed\n Know how to restore system from backups\n Know how to switch to new system\n Know how to configure the deployment\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n