Learning Objectives: - Learn about options for recovery of on-prem workloads into the cloud - Understand different RTO & RPO options for DR to AWS - Walk through different reference architectures

1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Robbie Wright, Amazon S3 & Amazon
Glacier
Disaster Recovery Options
with AWS

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Confidential | © 2014 Silver Peak Systems, Inc. All Rights Reserved.
Disaster
Recovery
Concepts

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
First steps
Find/Define applications
Business Impact Analysis
Set RPO/RTO

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Time
Recovery Point and Recovery Time Objective

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Recovery point
Time

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Disaster
Recovery point
Data loss
Time

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Disaster
Recovery point
Data loss
Recovery time
Down time
Time

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Disaster Recovery
High Availability Backup Disaster Recovery
Keep your applications
running 24x7
Make sure your
data is safe
Get your applications
and data back after a
major disaster

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS offers four levels of DR support across a
spectrum of complexity and time
Backup &
Restore Pilot light
Warm standby
in AWS
Hot standby
(with multi-site)
 Lower priority use
cases
 Solutions: S3, Storage
Gateway
 Cost: $
 Meeting lower RTO &
RPO requirements
 Core services
 Scale AWS resources in
response to a DR event
 Cost: $$
 Solutions that require
RTO & RPO in
minutes
 Business critical
services
 Cost: $$$
 Auto-failover of your
environment in AWS
 Cost: $$$$
Low High
RPO/RTO:
Hours
RPO/RTO:
10s of Minutes
RPO/RTO:
Minutes
RPO/RTO:
Real-time

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Disaster
Recovery
Approaches

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Storage Partner Solutions
Technology Solutions vetted by the AWS Storage Competency Program
aws.amazon.com/backup-recovery/partner-solutions/ Note: Represents a sample of storage partners
Note: Dell-EMC, IBM and Veritas have solutions and are working towards competency requirements
Backup and RecoveryPrimary Storage Archive BCDR
Solutions that leverage file, block, object, and
streamed data formats as an extension to on-
premises storage
Solutions that leverage Amazon S3 for
durable data backup
Solutions that leverage Amazon Glacier for
durable and cost-effective long-term data
backup
Solutions that utilize AWS to enable
recovery strategies focused on RTO and
RPO requirements

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Backup & Recovery
 Suitable for:
‒ Services that can sustain longer recovery times
‒ Lower priority use cases
 Low cost DR option that leverages existing
investments in:
‒ De-duplication
‒ Compression
‒ WAN acceleration

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Backing up to AWS via Storage Gateway
3 options to write on-premises backups to store in AWS
Customer Premises
File Gateway GlacierS3-IA
Backup
Server
Customer Bucket
Volume
Gateway
iSCSI
Tape
Gateway
Volume Gateway
S3
Glacier
Tape Gateway VTL
Customer Environment
EBS Snapshots
S3
S3
Standard

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Tape Gateway
Virtual tape storage in Amazon S3 and Amazon Glacier with VTL management
Virtual tape storage in S3 and Glacier accessed via tape gateway
Data compressed in-transit and at-rest
Up to 1 PB total tape storage per gateway, unlimited archive capacity
Supports leading backup applications
**3-5 hour tape retrieval from Amazon Glacier
Archived Tapes
stored in
Amazon Glacier
MEDIA
CHANGER
TAPE
DRIVE
Customer Premises
Virtual Tapes
stored in
Amazon S3
Backup
Server
HTTPSiSCSI
Tape
Gateway
Tape
Gateway VM

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
High availability Windows Server storage
Local HA with remote DR
us-west-1
Data Center
Windows
Clients Storage
Gateway VMMicrosoft DFS
HTTPSiSCSI
HTTPSiSCSI
SMB
Storage Gateway Service
us-east-1
Microsoft DFS
HTTPSiSCSI
Storage Gateway Service
us-east-1
us-west-1

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Pilot light

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Pilot Light
 Suitable for:
‒ Meeting lower RTO & RPO requirements
‒ Business critical services
‒ Mid-range cost option for DR
 Mid-range cost option for DR
 Third-party options: CloudEndure, Racemi
and others

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Pilot Light Architecture
Build resources around
replicated dataset
Scale AWS resources in
response to a DR event
 Keep ‘pilot light’ on by replicating
core databases
 Build AWS resources around
dataset and leave in stopped state
 Start up pool of resources in AWS
when events dictate
 Match required production capacity
through auto-scaling policies
Cut over to the system in AWS

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Subordinate
database
server
Pilot light–prep
www.example.com
Data mirroring
replication
Not running
Pilot light system
Reverse
proxy/
caching
server
Data
volume
Application
server
Corporate data center
Reverse
proxy/
caching
server
Application
server
Master
Database
server

21. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Database
server
Pilot light–recovery
www.example.com
Start in minutes
Add additional
capacity,
if needed
Reverse
proxy/
caching
server
Data
volume
Application
server
Corporate data center
Reverse
proxy/
caching
server
Application
server
Master
Database
server

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Warm standby

23. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Warm Standby
 Replication of data and services in the cloud
ensure full failover if needed during a disaster
 Suitable for:
‒ Solutions that require RTO & RPO in minutes
‒ Core business-critical functions
 Higher cost option for DR

24. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Warm standby–prep
Mirroring /replication
Application
data source
cut over
Elastic
load
balancerActive
Not active for
production traffic
Route 53
www.example.com
Scaled down
standbyCorporate data center
Data
volume
Application
server
Subordinate
database
server
Reverse
proxy/
caching
server
AWS Region
Reverse
proxy/
caching
server
Application
server
Master
Database
server

25. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Warm standby–recover
Elastic
load
balancer
Active
Route 53
www.example.com
Scaled-up
production
Corporate data center
Data
volume
Application
server
Database
server
Reverse
proxy/
caching
server
AWS Region
Reverse
proxy/
caching
server
Application
Server
Master
Database
server

26. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Hot site

27. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Multi-Site Hot Standby
 Full replication of your environment running
and ready for a failover during a disaster – it
runs ‘hot’.
 Suitable for:
‒ Solutions that require RTOs & RPOs of zero
‒ Core business-critical functions
‒ Multi-site architecture for automated load-
balancing of traffic to multiple AZs and even
AWS regions
 Higher cost option for DR

28. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Hot site–prep
Mirroring /replication
Application
data source
cut over
Elastic
load
balancerActive
Route 53
www.example.com
Corporate data center
Data
volume
Application
server
Subordinate
database
server
Reverse
proxy/
caching
server
AWS Region
Reverse
proxy/
caching
server
Application
server
Master
Database
server
Active

29. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Hot site–recovery
Elastic
load
balancer
Route 53
www.example.com
Corporate data center
Data
volume
Application
server
Database
server
Reverse
proxy/
caching
server
AWS Region
Reverse
proxy/
caching
server
Application
server
Master
Database
server
Active
Scaled up
for production use

30. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Remember, DR architecture depends on your Business
requirements!
Backup &
Restore Pilot light
Warm standby
in AWS
Hot standby
(with multi-site)
 Lower priority use
cases
 Solutions: S3, Elastic
Block Store
 Cost: $
 Meeting lower RTO &
RPO requirements
 Core services
 Scale AWS resources in
response to a DR event
 Cost: $$
 Solutions that require
RTO & RPO in
minutes
 Business critical
services
 Cost: $$$
 Auto-failover of your
environment in AWS
 Cost: $$$$
Low High
RPO/RTO:
Hours
RPO/RTO:
Minutes
RPO/RTO:
Seconds
RPO/RTO:
Real-time

31. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
DR Web Resources. Visit:
aws.amazon.com/disaster-recovery/
http://media.amazonwebservices.com/AWS_Disaster_Recovery.pdf

32. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Visit: aws.amazon.com/architecture/

33. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Case Studies
The City of Asheville was inspired to re-think its
off-site DR strategy after Hurricane Sandy.
Read more: https://aws.amazon.com/solutions/case-
studies/city-of-asheville/
Haven Power improved their DR strategy with the
AWS Cloud.
Read more: https://aws.amazon.com/solutions/case-
studies/haven-power/

34. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Questions?