Scribd
Upload
5 views2 pages

Disaster Recovery Overview AWS

The document outlines AWS's disaster recovery (DR) procedures, emphasizing the importance of restoring critical systems and data after disruptive events. It details various DR strategies, including backup and restore, pilot light, warm standby, and multi-site options, each catering to different recovery time and data loss objectives. Additionally, it provides steps for implementing and testing a DR solution using AWS services to ensure reliability, security, and cost-effectiveness.

Uploaded by

sgracy29
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views2 pages

Disaster Recovery Overview AWS

The document outlines AWS's disaster recovery (DR) procedures, emphasizing the importance of restoring critical systems and data after disruptive events. It details various DR strategies, including backup and restore, pilot light, warm standby, and multi-site options, each catering to different recovery time and data loss objectives. Additionally, it provides steps for implementing and testing a DR solution using AWS services to ensure reliability, security, and cost-effectiveness.

Uploaded by

sgracy29
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

AWS Execute Disaster Recovery Procedures - OVERVIEW

Disaster recovery (DR) is restoring critical systems and data after a disruptive event, such as a natural
disaster, a cyberattack, or a human error. DR helps minimize the impact of downtime and data loss
on business operations and reputation. AWS provides various services and tools to help you design
and implement a DR strategy that meets your recovery objectives and budget.

Some of the benefits of using AWS for DR are:

• Cost-effectiveness: You only pay for the resources you use and can scale them up or down as
needed.
• Flexibility: You can choose from different DR scenarios, such as backup and restore, pilot
light, warm standby, or multi-site, depending on your recovery time objective (RTO) and
recovery point objective (RPO).
• Reliability: AWS has a global infrastructure with multiple regions and availability zones, which
can provide redundancy and fault tolerance for your DR solution.
• Security: AWS offers various features and services to protect your data and resources from
unauthorized access, such as encryption, identity and access management, firewalls, and
monitoring.

One of the critical steps in DR planning is determining the recovery time objective (RTO) and the
recovery point objective (RPO) for each system or application. RTO is the maximum acceptable time a
system can go offline after a disaster. At the same time, RPO is the maximum permissible amount of
data loss that can occur after a disaster.

Choose a DR scenario that meets your requirements and budget. For example, if you have a low RTO
and RPO, you might opt for a multi-site scenario, running your application in two or more regions
simultaneously. If you have a high RTO and RPO, you might opt for a backup and restore strategy,
where you periodically back up your data to AWS S3 or Glacier and restore it when needed.

Based on these metrics, you can choose one of the following DR architectures on AWS:

• Backup and restore: This is the simplest and most cost-effective option, where you
periodically back up your data to AWS using services such as Amazon S3, Amazon EBS, or
AWS Backup. In case of a disaster, you restore your data from the backup to a new AWS
region or account. This option has a high RTO and RPO and is suitable for non-critical
applications or data that can tolerate long recovery times and significant data loss.
• Pilot light: This option involves keeping a minimal version of your system running on AWS at
all times, such as the core elements of your database. In case of a disaster, you quickly scale
up the resources and launch the remaining components on AWS using pre-configured
templates or automation tools. This option has a low RTO and a high RPO and is suitable for
applications or data that require fast recovery times but can tolerate some data loss.
• Warm standby: This option involves running a scaled-down version of your system on AWS
at all times, such as a smaller database and fewer application servers. In case of a disaster,
you quickly scale up the resources and switch the traffic to AWS using DNS or load balancers.
This option has a low RTO and a low RPO and is suitable for applications or data that require
fast recovery times and minimal data loss.
• Multi-site: This option involves running your system simultaneously on AWS and on-
premises or in another AWS region or account, using synchronous or asynchronous
replication. In a disaster, you switch the traffic to the unaffected site using DNS or load
balancers. This option has the lowest RTO and RPO and the highest cost and complexity. It is
suitable for mission-critical applications or data that require near-zero recovery times and
data loss.

To execute disaster recovery procedures on AWS, you need to follow these general steps:

• Identify the systems and applications that need DR protection and determine their RTO and
RPO requirements.
• Choose the appropriate DR architecture for each system or application based on their RTO
and RPO requirements and your budget.
• Implement the DR architecture using AWS services and tools, such as Amazon EC2, Amazon
S3, Amazon EBS, Amazon RDS, Amazon VPC, AWS CloudFormation, AWS Auto Scaling,
Amazon Route 53, Elastic Load Balancing, AWS Backup, AWS Storage Gateway, AWS
DataSync, AWS Database Migration Service. Other relevant services include AWS
CloudEndure Disaster Recovery to replicate your on-premises or cloud-based servers to AWS
with minimal disruption or AWS Lambda to trigger DR actions based on events or schedules.
• Test your DR solution regularly to ensure it works as expected and meets your SLAs. You can
use AWS CloudFormation StackSets to deploy your DR resources to multiple regions or
accounts for testing purposes, AWS Config to monitor the compliance of your DR resources
with your policies and best practices, or AWS Trusted Advisor to check the health and
performance of your DR solution.
• Monitor and update your DR solution as needed to reflect changes in your applications, data,
or requirements. You can use AWS CloudWatch to collect and analyze metrics and logs from
your DR resources, AWS CloudTrail to track the activity and changes in your DR resources, or
AWS Systems Manager to automate common tasks and apply patches to your DR resources.

You might also like