data recovery and backup in cloud computing ppt


{ AWS Storage Gateway enables snapshots of your on-premises data volumes to be transparently copied into Amazon S3 for backup. Recovery Time Objective and Recovery Point ObjectiveRecovery time objective (RTO) The time it takes after a disruption to restore a business process to its service level, as defined by the operational level agreement (OLA). For example, when deployed in Multi-AZ mode, Amazon RDS uses synchronous replication (data is atomically updated in multiple locations) to duplicate data in a second Availability Zone. This solution is not scaled to take a full-production load, but it is fully functional. Increase the size of the Amazon EC2 fleets in service with the load balancer (horizontal scaling). 2. Add resilience or scale up your database. Change DNS to point at the Amazon EC2 servers. The cost of this scenario is determined by how much production traffic is handled by AWS during normal operation. "name": "Pilot Light \u2013 Recovery Phase", Key steps for preparation: 1. ", Transferring data to and from Amazon S3 is typically done through the network. Have application logic for failover to use the local AWS database servers for all queries. You can further reduce cost by purchasing Amazon EC2 Reserved Instances for your always on AWS servers. Have application logic for failover to use the local AWS database servers for all queries. Backing up of data can be done through various mechanisms and your choice will be based on the RPO (Recovery Point Objective). "description": "What happens when you don\u2019t have the right DR system! Amazon S3 is an ideal destination for backup data that might be needed quickly to perform a restore. Multi-Site Solution Preparation PhaseThe following figure shows the use of weighted routing policy of the Amazon Route 53 DNS to route a portion of the traffic to the AWS site. It provides even greater fault tolerance for applications by seamlessly providing the load-balancing capacity that is needed in response to incoming application traffic. However if your data is mostly static with a low frequency ofchanges,you can opt for periodic incremental backup. "@type": "ImageObject", Key steps for recovery: 1. 5. Select an appropriate tool or method to back up your data into AWS. There are two main approaches for replicating data: synchronous and asynchronous. Have application logic for failover to use the local AWS database servers for all queries. In AWS, Availability Zones within a region are well connected, but physically separated. "contentUrl": "https://slideplayer.com/slide/12621176/76/images/10/Data+Backup+Options+to+Amazon+S3.jpg", Create and maintain AMIs of key servers where fast recovery is required. Configure automated failover to re-route traffic away from the affected site. Key steps for preparation: 1. 3. Recovery time objective (RTO) The time it takes after a disruption to restore a business process to its service level, as defined by the operational level agreement (OLA). For example, you can add more web servers at peak times. It further decreases the recovery time because some services are always running. "contentUrl": "https://slideplayer.com/slide/12621176/76/images/5/Recovery+Time+Objective+and+Recovery+Point+Objective.jpg", A company typically decides on an acceptable RTO and RPO based on the financial impact to the business when systems are unavailable. The application on AWS might access data sources in the on-site production system. Backup and Restore with AWSTo recover your data in the event of any disaster, you must first have your data periodically backed up from your system to AWS. Ensure that you have an appropriate retention policy for this data. Set up Amazon EC2 instances to replicate or mirror data. "@type": "ImageObject", "name": "Warm Standby Solution in AWS", ", For your dynamic data servers, you can resize them to handle production volumes as needed or add capacity accordingly. "name": "Warm Standby \u2013 Recovery Phase",

For each business service, customers need to establish an acceptable recovery point and time, and then build an appropriate DR solution. DR on Cloud can significantly reduce costs (up to half the costs) as compared to a company maintaining its own redundant data centers. Disaster recovery (DR) is about preparing for and recovering from a disaster. Now when a disaster strikes, EC2 (Elastic Compute Capacity) instances in the Cloud using EBS (Elastic Block Store) coupled with AMIs can access your data from the S3 (Simple Storage Service) buckets to revive your system and keep it going. "description": "Distance between the sites \u2014 Larger distances typically are subject to more latency or jitter. "description": "A company typically decides on an acceptable RTO and RPO based on the financial impact to the business when systems are unavailable. Critical business services are set up and maintained on this infrastructure and tested at regular intervals. 5. In AWS, Availability Zones within a region are well connected, but physically separated. These costs include buying and maintaining servers and data centers, providingsecure and stable connectivity and keeping them secure. Support for repairing, replacing, and refreshing the infrastructure. When a disaster strikes, the rest of the traffic that was pointing to the on premise servers are rerouted to AWS and using auto scaling techniques multiple EC2 instances are deployed to handle full production capacity. For longer-term data storage where retrieval times of several hours are adequate, there is Amazon Glacier for infrequent access, which has the same durability model as Amazon S3. Ensure that appropriate security measures are in place for this data, including encryption and access policies. ", "@context": "http://schema.org", "@type": "ImageObject", When the time comes for recovery, you can rapidly provision a full-scale production environment around the critical core. Key steps for preparation: 1. This technique is the next level of the pilot light, reducing recovery time to almost zero. Infrastructure as a Service (IaaS) Amazon EC2, High Availability Group 08: V c Vnh Nguyn Quang V. "contentUrl": "https://slideplayer.com/slide/12621176/76/images/18/Warm+Standby+%E2%80%93+Recovery+Phase.jpg", For example, when deployed in Multi-AZ mode, Amazon RDS uses synchronous replication to duplicate data in a second Availability Zone. Some applications might have an additional requirement to deploy their components using multiple regions.

IT organizations then plan solutions to provide cost-effective system recovery based on the RPO within the timeline and the service level established by the RTO. "description": "The term pilot light is often used to describe a DR scenario in which a minimal version of an environment is always running in the cloud. 1 NETE4631 Cloud deployment models and migration Lecture Notes #4. All rights reserved. }, 3 ", "name": "Pilot Light for Quick Recovery into AWS", It further decreases the recovery time because some services are always running. Horizontal scaling often is the most cost-effective and scalable approach to add capacity to a system. 4.

The following figure shows data backup options to Amazon S3, from either on-site infrastructure or from AWS. ", sauvegarde At a minimum, the infrastructure that is required to support the duplicate environment should include the following: Facilities to house the infrastructure, including power and cooling. The cost of this scenario is determined by how much production traffic is handled by AWS during normal operation. Change DNS to point at the Amazon EC2 servers. The other option is to use Elastic Load Balancer (ELB) which automatically distributes incoming application traffic across multiple Amazon EC2 instances. 1 Copyright 2011 EMC Corporation. In addition to database systems, this can also be extended to network file systems and data volumes. 1. They provide inexpensive, low-latency network connectivity within the same region. Amazon Glacier and Amazon S3 can be used in conjunction to produce a tiered backup solution. "contentUrl": "https://slideplayer.com/slide/12621176/76/images/7/Traditional+DR+Practices.jpg", In the recovery phase, you pay only for what you use for the duration that the DR environment is required at full scale. By identifying business-critical systems, a customer can fully duplicate these systems on AWS and have them always on. A traditional approach to DR involves different levels of off-site duplication of data and infrastructure. "description": "The following figure shows the preparation phase for a warm standby solution, in which an on-site solution and an AWS solution run side-by-side. Add additional database/data store instances to give the DR site resilience in the data tier; if you are using Amazon RDS, turn on Multi-AZ to improve resilience. 2. Consider automating the provisioning of AWS resources. "@context": "http://schema.org", Cloud Computing Disaster Recovery (DR)Dr. Sanjay P. Ahuja, Ph.D. FIS Distinguished Professor of Computer Science School of Computing, UNF 1 2. 4. The disaster recovery environments location and the source infrastructure should be a significant physical distance apart to ensure that the disaster recovery environment is isolated from faults that could impact the source site. Now when a disaster strikes,EC2(Elastic Compute Capacity) instances in the Cloud usingEBS(Elastic Block Store) coupled with AMIs can access your data from theS3(Simple Storage Service) buckets to revive your system and keep it going. Regularly run these servers, test them, and apply any software updates and configuration changes. DR on Cloud can significantly reduce costs (up to half the costs) as compared to a company maintaining its own redundant data centers. Regularly test the recovery of this data and the restoration of your system. This is a key advantage for DR, where significant infrastructure is needed quickly, but only in the event of a disaster. "name": "Traditional DR Practices", 4. This includes hardware or software failure, a network outage, a power outage, physical damage to a building like fire or flooding, human error, or some other significant event. Backing up of data can be done through various mechanisms and your choice will be based on the RPO (Recovery Point Objective). Available bandwidth. "@type": "ImageObject", 3. { At a minimum, the infrastructure that is required to support the duplicate environment should include the following: Facilities to house the infrastructure, including power and cooling. Add resilience or scale up your database. Enough server capacity to run all mission-critical services, including storage appliances for the supporting data, and servers to run applications and backend services such as user authentication, Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), monitoring, and alerting. 3.

}, 12 Critical business services are set up and maintained on this infrastructure and tested at regular intervals. You can further reduce cost by purchasing Amazon EC2 Reserved Instances for your always on AWS servers. The load balancer can be pre-allocated so that its DNS name is already known and the customer DNS tables point to the load balancer. The disaster recovery environments location and the source infrastructure should be a significant physical distance apart to ensure that the disaster recovery environment is isolated from faults that could impact the source site. Set up your AWS environment to duplicate your production environment. Install and configure any non-AMI based systems, ideally in an automated way. }, 5 You can use AWS Import\/Export to transfer very large data sets by shipping storage devices directly to AWS. }, 16 { Applications deployed on AWS have multi-site capability by means of multiple Availability Zones. This ensures that data is not lost if the primary Availability Zone becomes unavailable. { The other option is to use Elastic Load Balancer (ELB) which automatically distributes incoming application traffic across multiple Amazon EC2 instances. For example, you can add more web servers at peak times. When a disaster strikes, the rest of the traffic that was pointing to the on premise servers are rerouted to AWS and using auto scaling techniques multiple EC2 instances are deployed to handle full production capacity. "@type": "ImageObject", "name": "Recovery Time Objective and Recovery Point Objective", "contentUrl": "https://slideplayer.com/slide/12621176/76/images/21/Multi-Site+Solution+%E2%80%93+Recovery+Phase.jpg", To recover the remainder of the environment around the pilot light, you can start your systems from the AMIs within minutes on the appropriate instance types. { Either manually change the DNS records, or use Amazon Route 53 automated health checks so that all traffic is routed to the AWS environment. Data rate required by your application The data rate should be lower than the available bandwidth. }. "@type": "ImageObject", Run your application using a minimal footprint of Amazon EC2 instances or AWS infrastructure. "@context": "http://schema.org", 5. Create and maintain AMIs. Some applications might have an additional requirement to deploy their components using multiple regions. "@context": "http://schema.org", "contentUrl": "https://slideplayer.com/slide/12621176/76/images/13/Pilot+Light+for+Quick+Recovery+into+AWS.jpg", "contentUrl": "https://slideplayer.com/slide/12621176/76/images/16/Warm+Standby+Solution+in+AWS.jpg", They provide inexpensive, low-latency network connectivity within the same region. For example, if a disaster occurs at 12:00 PM (noon) and the RPO is one hour, the system should recover all data that was in the system before 11:00 AM. It is transferred as network performance and availability allows, and the application continues to write data that might not be fully replicated yet. The term warm standby is used to describe a DR scenario in which a scaled-down version of a fully functional environment is always running in the cloud. For example, if a disaster occurs at 12:00 PM (noon) and the RTO is eight hours, the DR process should restore the business process to the acceptable service level by 8:00 PM. The servers would also be under utilized. Share buttons are a little bit lower. Consider using Auto Scaling to automatically right-size the AWS fleet. This is acceptable in many scenarios, for example, as a backup source or reporting/read-only use cases. The following diagram shows how to quickly restore a system from Amazon S3 backups to Amazon EC2. "contentUrl": "https://slideplayer.com/slide/12621176/76/images/8/Example+Disaster+Recovery+Scenarios+with+AWS.jpg", To provision the remainder of the infrastructure to restore business-critical services, there would be some pre-configured servers bundled as Amazon Machine Images (AMIs), which are ready to be started up at a moments notice (this is the furnace in the analogy). Install and configure any non-AMI based systems, ideally in an automated way. { For example, if a disaster occurs at 12:00 PM (noon) and the RTO is eight hours, the DR process should restore the business process to the acceptable service level by 8:00 PM. Network infrastructure such as firewalls, routers, switches, and load balancers. 5. Key steps for preparation: 1. }, 10 { Once your backup mechanisms are activated you can pre-configure Amazon Machine Images (kind of like a Class while the EC2 instance is the object instantiated from the AMI class) AMIs (operating systems & application software). Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. 2. "width": "1024" EMC RecoverPoint/Cluster Enabler for Microsoft Failover Cluster. "width": "1024" Configure automated failover to re-route traffic away from the affected site. Set up DNS weighting, or similar traffic routing technology, to distribute incoming requests to both sites. However, you can also choose larger Amazon EC2 instance types, and thus scale vertically for applications such as relational databases. ", What happens when you dont have the right DR system! 5. Create and maintain AMIs of key servers where fast recovery is required. With AWS you can maintain a pilot light by configuring and running the most critical core elements of your system in AWS. The cost of this scenario is determined by how much production traffic is handled by AWS during normal operation. Add additional database/data store instances to give the DR site resilience in the data tier; if you are using Amazon RDS, turn on Multi-AZ to improve resilience. When data is replicated to a remote location, these factors need to considered: Distance between the sites Larger distances typically are subject to more latency or jitter. Asynchronous replication. 2. The idea of the pilot light is an analogy that comes from the gas heater. Either manually or by using DNS failover, change the DNS weighting so that all requests are sent to the AWS site. Support for repairing, replacing, and refreshing the infrastructure. For longer-term data storage where retrieval times of several hours are adequate, there is Amazon Glacier for infrequent access, which has the same durability model as Amazon S3. From a networking perspective, any required DNS updates can be done in parallel. If you wish to download it, please recommend it to your friends in any social system. The idea of the pilot light is an analogy that comes from the gas heater. "contentUrl": "https://slideplayer.com/slide/12621176/76/images/1/Cloud+Computing+Disaster+Recovery+%28DR%29.jpg", Amazon Glacier is a low-cost alternative starting from $0.01/GB per month. A warm standby solution extends the pilot light elements and preparation. Configure automated failover to re-route traffic away from the affected site. Any event that has a negative impact on a companys business continuity or finances could be termed a disaster. Either manually change the DNS records, or use Amazon Route 53 automated health checks so that all traffic is routed to the AWS environment. Replication of Data Synchronous replicationData is atomically updated in multiple locations. "@type": "ImageObject", "@type": "ImageObject", For longer-term data storage where retrieval times of several hours are adequate, there is Amazon Glacier for infrequent access, which has the same durability model as Amazon S3. These costs include buying and maintaining servers and data centers, providingsecure and stable connectivity and keeping them secure. Select an appropriate tool or method to back up your data into AWS. All activities in the preparatory stage are similar to a warm standby; except that the AWS backup on the cloud is also used to handle some portions of the user traffic using Route 53, a DNS service that supports weighted routing. }, 9 By identifying business-critical systems, a customer can fully duplicate these systems on AWS and have them always on. This is the critical core of the system (the pilot light) around which all other infrastructure pieces in AWS (the rest of the furnace) can quickly be provisioned to restore the complete system. "name": "Traditional DR Practices", AWS gives you fine-grained control and many building blocks to build the appropriate DR solution, given your DR objectives (RTO and RPO) and budget. }, 18 "width": "1024" Oracle Data Guard Ensuring Disaster Recovery for Enterprise Data. Key steps for preparation: 1. Key steps for recovery: 1. ", "@type": "ImageObject", "width": "1024" In a gas heater, a small flame thats always on can quickly ignite the entire furnace to heat up a house. "width": "1024" "width": "1024" }, 15 Resize existing database/data store instances to process the increased traffic. Multi-Site Solution Recovery PhaseThe following figure shows the change in traffic routing in the event of an on-site disaster. It gives developers and businesses a reliable, cost-effective way to route users to Internet applications. "description": "The following figure shows the change in traffic routing in the event of an on-site disaster. In the case of failure of the production system, the standby environment will be scaled up for production load, and DNS records will be changed to route all traffic to AWS as shown below.

Multi-Site Solution Deployed on AWS and On-SiteThis is the optimum technique in backup and DR and is the next step after warm standby. Amazon S3 is an ideal destination for backup data that might be needed quickly to perform a restore. Horizontal scaling often is the most cost-effective and scalable approach to add capacity to a system. { "description": "In the case of failure of the production system, the standby environment will be scaled up for production load, and DNS records will be changed to route all traffic to AWS as shown below. This ensures that data is not lost if the primary Availability Zone becomes unavailable.

"@context": "http://schema.org", Ensure that appropriate security measures are in place for this data, including encryption and access policies. Applications deployed on AWS have multi-site capability by means of multiple Availability Zones.

Network infrastructure such as firewalls, routers, switches, and load balancers. "@type": "ImageObject", "description": "The following figure shows the use of weighted routing policy of the Amazon Route 53 DNS to route a portion of the traffic to the AWS site. Business Continuity and DR, A Practical Implementation Mich Talebzadeh, Consultant, Deutsche Bank. }, 23 Data is not atomically updated in multiple locations. For example, if a disaster occurs at 12:00 PM (noon) and the RPO is one hour, the system should recover all data that was in the system before 11:00 AM. Recovery Time Objective and Recovery Point ObjectiveA company typically decides on an acceptable RTO and RPO based on the financial impact to the business when systems are unavailable. Change DNS to point at the Amazon EC2 servers. "@context": "http://schema.org", In a gas heater, a small flame thats always on can quickly ignite the entire furnace to heat up a house. ", The AWS services are available on-demand, and you pay only for what you use. ", According to AWS, Disaster recovery is a continual process of analysis and improvement, as business and systems evolve. The database replica can be located remotely, and the replica does not have to be completely synchronized with the primary database server. Suitable capacity to scale the environment. Ensure that you have an appropriate retention policy for this data. AWS Import/Export bypasses the Internet and transfers your data directly onto and off of storage devices by means of the high-speed internal network of Amazon. "description": "To recover your data in the event of any disaster, you must first have your data periodically backed up from your system to AWS. All activities in the preparatory stage are similar to a warm standby; except that the AWS backup on the cloud is also used to handle some portions of the user traffic using Route 53, a DNS service that supports weighted routing. Now when a disaster strikes,EC2(Elastic Compute Capacity) instances in the Cloud usingEBS(Elastic Block Store) coupled with AMIs can access your data from theS3(Simple Storage Service) buckets to revive your system and keep it going. AWS Storage Gateway enables snapshots of your on-premises data volumes to be transparently copied into Amazon S3 for backup. "contentUrl": "https://slideplayer.com/slide/12621176/76/images/14/Pilot+Light+%E2%80%93+Preparation+Phase.jpg", Pilot Light Preparation PhaseThe following figure shows the preparation phase, in which regularly changing data is replicated to the pilot light, the small core around which the full environment will be started in the recovery phase. "width": "1024" The following figure shows the preparation phase, in which regularly changing data is replicated to the pilot light, the small core around which the full environment will be started in the recovery phase. The term warm standby is used to describe a DR scenario in which a scaled-down version of a fully functional environment is always running in the cloud. Data is not atomically updated in multiple locations. 4. 1/17/20141 Leveraging Cloudbursting To Drive Down IT Costs Eric Burgener Senior Vice President, Product Marketing March 9, 2010. "@context": "http://schema.org", In the recovery phase, you pay only for what you use for the duration that the DR environment is required at full scale. Set up DNS weighting, or similar traffic routing technology, to distribute incoming requests to both sites. 2. Traditional DR PracticesContractual agreements with an Internet service provider (ISP) to provide Internet connectivity that can sustain bandwidth utilization for the environment under a full load. Example Disaster Recovery Scenarios with AWSThere are four DR scenarios that highlight the use of AWS. Set up Amazon EC2 instances to replicate or mirror data. The load balancer can be pre-allocated so that its DNS name is already known and the customer DNS tables point to the load balancer. Infrastructure elements for the pilot light itself typically includes database servers, which would replicate data to Amazon EC2 or Amazon RDS. "description": "The following diagram shows how to quickly restore a system from Amazon S3 backups to Amazon EC2. Key steps for recovery: 1. The following figure shows the preparation phase for a warm standby solution, in which an on-site solution and an AWS solution run side-by-side. Infrastructure elements for the pilot light itself typically includes database servers, which would replicate data to Amazon EC2 or Amazon RDS. This is acceptable in many scenarios, for example, as a backup source or reporting/read-only use cases. 1 Copyright 2010 EMC Corporation. Patch and update software and configuration files in line with your live environment. 4. 3. Many database systems support asynchronous data replication.

This puts a dependency on network performance and availability. There are two main approaches for replicating data: synchronous and asynchronous. Security to ensure the physical protection of assets. ", All activities in the preparatory stage are similar to a warm standby; except that the AWS backup on the cloud is also used to handle some portions of the user traffic using Route 53, a DNS service that supports weighted routing. "name": "Multi-Site Solution \u2013 Recovery Phase", You can subsequently create local volumes or Amazon EBS volumes from these snapshots. It is transferred as network performance and availability allows, and the application continues to write data that might not be fully replicated yet. 1. For example, if a disaster occurs at 12:00 PM (noon) and the RPO is one hour, the system should recover all data that was in the system before 11:00 AM. 2. The application on AWS might access data sources in the on-site production system. "@type": "ImageObject", }, 13 Add additional database\/data store instances to give the DR site resilience in the data tier; if you are using Amazon RDS, turn on Multi-AZ to improve resilience. The term pilot light is often used to describe a DR scenario in which a minimal version of an environment is always running in the cloud. These costs include buying and maintaining servers and data centers, providing secure and stable connectivity and keeping them secure. These servers (app and caching servers) can be running on a minimum-sized fleet of Amazon EC2 instances on the smallest sizes possible. In AWS, Availability Zones within a region are well connected, but physically separated. Start your application Amazon EC2 instances from your custom AMIs. However if your data is mostly static with a low frequency ofchanges,you can opt for periodic incremental backup. "contentUrl": "https://slideplayer.com/slide/12621176/76/images/12/Pilot+Light+for+Quick+Recovery+into+AWS.jpg", According to AWS, Disaster recovery is a continual process of analysis and improvement, as business and systems evolve. Contractual agreements with an Internet service provider (ISP) to provide Internet connectivity that can sustain bandwidth utilization for the environment under a full load. When the time comes for recovery, you can rapidly provision a full-scale production environment around the critical core. "name": "Warm Standby \u2013 Preparation Phase", "@type": "ImageObject", With AWS you can maintain a pilot light by configuring and running the most critical core elements of your system in AWS. "@context": "http://schema.org", For example, you can add more web servers at peak times. "name": "Pilot Light for Quick Recovery into AWS", Consider using Auto Scaling to right-size the fleet or accommodate the increased load. "description": "Contractual agreements with an Internet service provider (ISP) to provide Internet connectivity that can sustain bandwidth utilization for the environment under a full load.