In the event of a disaster, you need to be able to recover lost data quickly to ensure business continuity. For critical applications, keeping your time to recover and data loss to a minimum and optimizing your overall capital expense can be challenging. This session presents AWS features and services along with disaster recovery architectures that you can leverage when building highly available and disaster-resilient strategies.
8. 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. 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
12. 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. 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. 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. 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
17. 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
18. 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. 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. 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
23. 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
26. 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
27. 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. 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
30. DR Web Resources. Visit:
aws.amazon.com/disaster-recovery/
http://media.amazonwebservices.com/AWS_Disaster_Recovery.pdf
32. 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/