SREENIDHI INSTITUTE OF SCIENCE AND TECHNOLOGY

DEPARTMENT OF CSE

Internship Title : Planning for Disaster Recovery in

AWS
Domain : AWS Cloud Virtual Internship

Saketh K P S M Hemanth varma N Hemanth Kumar

22311A05FH 22311A05FX
III-I-CSE-H III-I-CSE-H

22311A05FN
III-I-CSE-H
Academic Year: 2024-25
SAMPLE FOOTER TEXT 1
Contents Introduction
•

• Introduction To AWS
• Architectural need
• Disaster planning strategies
• RPO
• RTO
• Disaster recovery patterns
• Output
• Lab Activity Description
• Conclusion
• References
2
Introduction
In this presentation, we discuss about the
recovery of data after a disaster using AWS.
Also the strategies and talk about Recovery
Point Objective(RPO) and Recovery Time
Objective(RTO). We describe four common
patterns for backup and disaster recovery and
how to implement them.

3
Introduction To AWS
Amazon Web Services (AWS) provides scalable, reliable cloud
solutions crucial for disaster management. It offers tools for
data backup, real-time analytics, and recovery, ensuring
business continuity during crises. With services like Amazon S3
for secure data storage, AWS Lambda for automated
responses, and Amazon EC2 for on-demand computing,
organizations can swiftly recover from disruptions. AWS’s
global infrastructure ensures resilience, while tools like AWS
Disaster Recovery help minimize downtime. Additionally, AWS
enables real-time communication and data sharing, supporting
emergency responses and disaster mitigation, making it an
essential platform for managing critical operations during 4
Architectural need
It’s important to put backup and disaster
recovery plans into place. The main
objective is to implement an architecture
that supports their disaster recovery time
objectives, while it also optimizes for cost.
They also agreed that as their revenue
grows, they will be able to afford a solution
that supports a shorter recovery time
objective

5
 Disaster planning strategies
• High availability provides redundancy and fault tolerance. A system is highly
available when it can withstand failure of an individual or multiple components.
Production systems typically have defined uptime requirements.
• Backup is critical to protecting data and ensuring business continuity. However, it can
be a challenge to implement. The pace at which data is generated is growing
exponentially. Meanwhile, the density and durability of local disks are not
experiencing the same growth rate. Even so, it is essential to keep your critical data
backed up, in case of disaster.
• Disaster recovery (DR) is about preparing for and recovering from a disaster. A
disaster is any event that has a negative impact on a company’s business continuity
or finances. Such events include hardware or software failure, a network outage, a
power outage, or physical damage to a building
6
Recovery Point Objective
Recovery point objective (RPO) is the maximum acceptable amount
of data loss, measured in time.
Example RPO: The business can recover from losing (at most) the
last 8 hours of data.
To calculate RPO, first determine how much data loss is acceptable,
according to your BCP. Then, figure out how quickly that data loss
might occur, as a time measurement.
8 hours or fewer RPO
Time
[ data loss ]

Last backup Disaster strikes

7
Recovery Time Objective
Recovery time objective (RTO) is the maximum acceptable amount of time after disaster
strikes that a business process can remain out of commission.
Example RTO: The application can be unavailable for a maximum of 1 hour.

RPO 1 hour RTO

Time
[ data loss ] [ down time ]

Last backup Disaster strikes Applications and

data recovered
8
Plan for disaster recovery
• Use features such as S3 Cross-Region Replication, EBS volume
snapshots, and Amazon RDS snapshots to protect data
• Use networking features (such as Route 53 failover and Elastic Load
Balancing) to improve application availability
• Use automation services (such as AWS CloudFormation) as part of
your DR strategy to quickly deploy duplicate environments when
needed
Region
2
Region
1

Storage Compute Networking Database Deployment

orchestratio
n

9
Disaster recovery patterns
Four disaster recovery patterns
▪ Backup and restore
▪ Pilot light
▪ Warm standby
▪ Multi-site
Each pattern is suited to a different combination of:
▪ Recovery point objective
▪ Recovery time objective
▪ Cost-effectiveness

10
CONT..
• Common disaster recovery patterns on AWS include backup and restore,
pilot light, warm standby, and multi-site
• Backup and restore is the most cost effective approach. However, it has
the highest RTO.
• Multi-site provides the fastest RTO. However, it costs the most because
it provides a fully running production-ready duplicate.
• AWS Storage Gateway provides three interfaces—file gateway, volume
gateway, and tape gateway—for data backup and recovery between
on-premises and the AWS Cloud.

11
OUTPUT
Output of various functionalities in our application are shown over here along with the
description
Task-1 Reviewing the lab architecture
The primary S3 bucket is created in the us-east-2 (Ohio) Region. Data from the Linux host is
copied to
the primary S3 bucket. This bucket can also be called the source. The secondary S3 bucket is
created in the us-west-2 (Oregon) Region. This secondary bucket is the target
for the cross-Region replication policy. It can also be called the destination.
Task-2 Creating the primary and secondary S3 Buckets.
In this task, we will be creating two buckets named First and Second buckets in two different
regions. Primary in US east-2 and Second in US west-2. We also enable the versioning.

14
Task-3 Enabling cross-region replication
In this task, we enable versioning on them and create a replication policy. Then we upload a
file in the
first region and the same file should appear in the second region.

15
Task-4 Configuring the file gateway and creating an NFS file share
In this task, you will deploy the File Gateway appliance as an Amazon Elastic Compute Cloud
(Amazon
EC2) instance. You will then configure a cache disk, select an S3 bucket to synchronize your
on-premises
files to, and select an IAM policy to use. Finally, you will create an NFS file share on the File
Gateway.

16
Task-5 Mounting the file share to the linux instance and migrating the
data
Before you can migrate data to the NFS share that you created, you must first mount the
share. In this task, you will mount the NFS share on a Linux server, then copy data to the
share.

17
Task-6 Verifying that the data is
migrated
You have finished configuring the gateway and copying data into the NFS share. Now, you will
verify
that the configuration works as intended

18
CONCLUSION
▪ Disaster recovery planning is a crucial aspect of any organization's overall
business continuity
▪ strategy. It involves identifying potential threats to the organization's IT
infrastructure and
▪ developing strategies to prevent or mitigate those threats, as well as plans
for how to recover from
▪ disruptions or failures that do occur. AWS (Amazon Web Services) offers a
range of disaster
▪ recovery solutions that can help organizations of all sizes to build resilient
and effective disaster
▪ wide range of services, scalability, flexibility, and global presence. By
leveraging these
▪ capabilities, organizations can build effective disaster recovery plans that
help ensure the
▪ continuity of their business operations
REFERENCES
▪ [1] Herbert Schildt, The Complete Reference Java2 Fifth
Edition, Tata McGraw-Hill Edition 2002.
▪ [2] Grady Booch, James Rumbaugh, Ivar Jacobson. The
Unified Modeling Language User Guide. Addison-Wesley,
Reading, Mass., 1999.
▪ [3] www.coderanch.com
▪ [4] www.java.sun.com
▪ [5] www.w3schools.com
▪ [6] www.wikipedia.org
Any Queries?
THANK YOU

22