Backup-and-Recovery Procedures decribed in AWS

This will Describe the Backup and Recovery Procedures in AWS

1. AWS
Backup and Recovery

2. Question
Which backup and recovery components do you
work with?
A.Off-site backup storage
B.Colocation facilities
C.Tape retrievals
D.On-premises backup
E.All of the above
2

3. Module overview
•Business requests
•Disaster planning
•AWS Backup
•Recovery strategies
•Present solutions
•Knowledge check
•Capstone lab: Build an AWS multi-tier architecture
3

4. Business
Requirements
Chief Technology
Officer
The chief technology officer has the following
questions:
•What strategies can we use to protect ourselves in the
event of a disaster?
•How can we centralize and automate our backup
strategy?
•Which disaster recovery strategy minimizes downtime
but is also cost effective?
4

5. Disaster planning
“What strategies can we use to protect ourselves in the event of a
disaster?”
5

6. Disaster recovery plan failure
Testing
•Lack of testing
Resources
•Complex recovery path
•Lack of sufficient
resources
?
?
!
Oct 2010
!
Planning
•Outdated plans
•Changes not factored
6

7. Availability concepts
High Availability
Minimize downtime for
your application.
Fault Tolerance
Ensure built-in
redundancy.
Backup
Make sure your data
is recoverable.
Disaster Recovery
Get your applications and
data back after a major
disaster.
7

8. Failover and Regions
•Plan for
instance
failover.
•Plan for
Availability
Zone failover.
•Plan for
Regional
failover.
Compute
Storage
Database
Compute
Storage
Database
Region 1 Region 2
8

9. Recovery Point Objective (RPO) and Recovery Time Objective (RTO)
Time
RPO
Minimize data loss
How often does data need to be
backed up?
Example
The business can recover from losing (at
most) the last 12 hours of data.
Disaster
RTO
Minimize downtime
How long can the application be
unavailable?
Example
The application can be unavailable for a
maximum of 1 hour.
9

10. Essential AWS services and features for DR
Regions
Storage Compute Networking Database Deployment
orchestration
10

11. Duplicate your storage
Amazon S3
Cross-Region Replication
Amazon S3 Glacier
•Stores data in Regional
vaults.
•Updates inventory daily.
Amazon EBS
•Create point-in-time volume
snapshots.
•Copy snapshots across
Regions and accounts.
AWS Snow Family
Transfer large volumes
(>10 TB) of data faster
than high-speed internet.
AWS DataSync
Sync files from on-
premises or in-cloud file
systems to Amazon EFS.
11

12. Configuring AMIs for recovery
Obtain and boot
new server
instances or
containers within
minutes.
Amazon Elastic Compute
Cloud (Amazon EC2)
Auto Scaling group
EC2 instanceEC2 instanceEC2 instance
Custom AMIs
Amazon Elastic Container
Service (Amazon ECS)
Container Container Container
Container
images
12

13. Failover network design
Amazon
Route 53
Traffic distribution and
failover
Elastic Load
Balancing (ELB)
Load balancing, health
checks, and failover
Amazon Virtual
Private Cloud
(Amazon VPC)
Extended on-premises
network topology
AWS Direct
Connect
Highly-resilient
dedicated network
connection between
on-premises
infrastructure and
Amazon VPC
13

14. Database backup and replicas
Amazon Relational
Database Service
(Amazon RDS)
•Take a snapshot of data and save it in a separate Region.
•Use Multi-AZ cluster deployment to build a resilient DR strategy using
standby instances and read replicas.
•Retain automated backups.
Amazon
DynamoDB
•Back up full tables in seconds.
•Use point-in-time-recovery to continuously back up tables for up to 35 days.
•Initiate backups with a single click in the console or a single API call.
•Use global tables for fast local performance for globally distributed apps.
14

15. Templates and scripts
AWS
CloudFormation
Use templates to quickly deploy collections of
resources as needed.
Scripts
Use scripts to automate the provisioning of
infrastructure in the cloud.
15

16. AWS Backup
“How can we centralize and automate our backup strategy?”
16

17. AWS Backup
A fully managed
backup service:
•Centralized
and
automated
data
protection
•Backs up
across AWS
resources
AWS Backup
Amazon EC2
DynamoDB Amazon Aurora Amazon RDS
Amazon EFSAmazon EBS FSx for
Windows File
Server
FSx for
Lustre
AWS Storage
Gateway
17

18. AWS Backup benefits
Simplicity
Policy-based and
tag-based backup
solution
Automated backup
scheduling
Compliance
Centralized backup
activity monitoring and
logs
Backup access policies
Encrypted backups
Control costs
Automated management
of backup retention
No added cost for
orchestration
18

19. Understanding how AWS Backup works
You implement your backup strategy with AWS Backup by creating AWS Backup plans.
1. Create AWS Backup plan
•Schedule
•Lifecycle
•Vault
•Tags for the backups
2. Assign resources
Select the resources to use this
plan:
•Assigned tags
•Resource IDs
Specify IAM role
3. Manage and monitor backups
•AWS Backup automatically
runs the backup plan
•Centrally manage backups
•Centrally monitor backup
activity
Works with AWS Organizations to manage backup policies across AWS accounts
19

20. Recovery strategies
“Which disaster recovery strategy minimizes downtime but is also cost
effective?”
22

21. Recovery strategies
Recovery
Strategies
Backup and restore
Pilot light
Fully working low-capacity standby
Multi-site active/active
23

22. Backup and restore example
AWS Cloud
Amazon S3
Amazon S3
Glacier
Remote
server
/mybucket
Amazon S3
Standard-IA
Lifecycle
policy
Backup
Remote
server
Restore
AWS DR Region
EC2 Instance
AWS Cloud
Amazon S3
/mybucket
24

23. Pilot light example (1 of 2)
Very cost-
effective (uses
fewer 24/7
resources)
DB secondary
Web server
User or system
Route 53
hosted zone
App server
Web
server
App
server
Data replication
DB primary
AWS Cloud
Production Recovery
Not
running
25

24. Pilot light example (2 of 2)
•Bring up
resources
around the
replicated core
data set.
•Scale as
needed to
handle current
production
traffic.
•Switch to the
new system by
adjusting DNS
records to
point to AWS.
Web server App server
DB secondary
AWS Cloud
Production Recovery
User or system
Route 53
hosted zone
Web
server
App
server
DB primary
Starts in
minutes
26

25. Fully working low-capacity standby (1 of 2)
•Ready for
production
traffic
•Cannot handle
full load
without scaling
•Low-cost
option that
prevents
downtime
Production Recovery
User or system
Route 53
hosted zone
DB secondary
AWS Cloud
Auto Scaling groupAuto Scaling group
App serverWeb server
DB primary
Web
server
App
server
Data replication
Running
at low
capacity
27

26. Fully working low-capacity standby (2 of 2)
•Immediately
fail over the
most critical
production
load
•Adjust DNS
records to
point to AWS
•Auto-scale the
system to
handle full
production
load
Production Recovery
User or system
Route 53
hosted zone
DB secondary
AWS Cloud
Auto Scaling groupAuto Scaling group
App serverWeb server
DB primary
Web
server
App
server
Scaling
out to full
capacity
28

27. Multi-site active/active (1 of 2)
•Ready to take
the full
production
load
•Similar to low-
capacity
standby
•Scale in or out
in response to
the production
load
App serverWeb server
Web
Server
User or system
Route 53
hosted zone
DB secondary
AWS Cloud
Auto Scaling groupAuto Scaling group
DB primary
Web
server
App
server
Full
capacity
Data replication
Production A Production B
29

28. Multi-site active/active (2 of 2)
•RTO: As long
as it takes to
fail over
•RPO: Depends
on replication
type App serverWeb server
User or system
Route 53
hosted zone
DB secondary
AWS Cloud
Auto Scaling groupAuto Scaling group
DB primary
Web
server
App
server
Full
capacity
Production A Production B
30

29. Comparing common DR practices on AWS
Low HighCost
Backup and restore
RPO-RTO:
Hours
•Lowest priority use
cases
•Solutions: Amazon
S3, Storage Gateway
Pilot light
RPO-RTO:
10s of minutes
•Lower RTO and RPO
requirements
•Core services
•Scale AWS resources in
response to a DR event
Fully working low-
capacity standby
RPO-RTO:
minutes
•Higher priority solutions
require RTO and RPO in
minutes
•Business-critical services
Multi-site
active/active
RPO-RTO:
Real-time
•Highest priority
•Auto-failover of your
environment in AWS
to a running
duplicate
31

30. Review
32

31. Present
solutions
Chief Technology
Officer
Consider how you would answer the following:
•What strategies can we use to protect ourselves in the
event of a disaster?
•How can we centralize and automate our backup
strategy?
•Which disaster recovery strategy minimizes downtime
but is also cost effective?
33

32. Module review
In this module, you learned about:
✓Disaster planning
✓AWS Backup
✓Recovery strategies
Next, you will review:
Knowledge check
Capstone lab introduction
34

33. Knowledge check

34. Knowledge check question 1
Which disaster recovery model offers an RTO in minutes at the lowest cost?
AFully working low-capacity standby
BPilot light
CBackup and restore
DMulti-site active/active
36

35. Knowledge check question 1 and answer
Which disaster recovery model offers an RTO in minutes at the lowest cost?
AFully working low-capacity standby
B
correct
Pilot light
CBackup and restore
DMulti-site active/active
37

36. Knowledge check question 2
Which metrics define how often data must be backed up?
ARTO
BRPO
CAvailable storage
DAmount of data
38

37. Knowledge check question 2 and answer
Which metric defines how often data must be backed up?
ARTO
B
correct
RPO
CAvailable storage
DAmount of data
39

38. Knowledge check question 3
Which of the following are features of AWS Backup? (Select THREE.)
AEncrypted backups
BWorks across every AWS service
CWorks across multiple services
DAutomated failover to read replicas
EIncremental backups
FAutomated machine conversion
40

39. Knowledge check question 3 and answers
Which of the following are features of AWS Backup? (Select THREE.)
A correctEncrypted backups
BWorks across every AWS service
C correctWorks across multiple services
DAutomated failover to read replicas
E correctIncremental backups
FAutomated machine conversion
41

40. Knowledge check question 4
What is the best way to make an existing Amazon RDS DB instance highly available and minimize your RTO?
ARun a secondary copy of your DB instance in another Region.
BRun a Multi-AZ DB instance in the same Region.
CCreate a read replica in another Region.
DCreate a read replica in the same Region.
42

41. Knowledge check question 4 and answer
What is the best way to make an existing Amazon RDS DB instance highly available and minimize your RTO?
ARun a secondary copy of your DB instance in another Region.
B correctRun a Multi-AZ DB instance in the same Region.
CCreate a read replica in another Region.
DCreate a read replica in the same Region.
43

42. Lab
Build an AWS multi-tier architecture

43. Summary
•Review and analyze architectural solutions
based on project data, best practices, and the
Well-Architected Framework.
•Design the architecture in a lab, without
specific guidance.
45

44. Lab navigation
High-level
instructions
(challenge)
Detailed
instructions
46

45. Capstone architecture
App subnet
App subnet
VPC
Availability Zone
Public subnet Database
subnet
NAT gateway
Aurora replica
Availability Zone
Public subnet Database
subnet
NAT gateway
Aurora primary
DB instance
Amazon EFS
Internet
gateway
App servers
App servers
Auto Scaling
group
Region
EFS mount
target
EFS mount
target
Application
Load Balancer
47

46. Lab tasks
Task 6: Create the application servers by configuring an Auto Scaling group and a scaling policy.
Task 5: Create a launch template using CloudFormation.
Task 4: Create an Application Load Balancer.
Task 3: Create an Amazon EFS file system.
Task 2: Create an Amazon RDS database.
Task 1: Review and run a preconfigured CloudFormation template.
48