Disaster Recovery with AWS: Tiered Approaches to Balance Cost with Recovery Objectives - ENT322 - re:Invent 2017

© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS re:Invent
Disaster Recovery with AWS
T i e r e d A p p r o a c h e s t o B a l a n c e C o s t w i t h R e c o v e r y O b j e c t i v e s
E N T 3 2 2
N o v e m b e r 2 9 , 2 0 1 7

What to expect from this session
• 300 level session
• Iteration of previous re:Invent talks
• How to leverage AWS for disaster recovery scenarios
• Examples
• Cost information
• Special demo

History does not repeat itself
but it does rhyme
– Mark Twain

1986-04-26 01:23:04
Begin experiment...

Recovery point

Panic
Systems are not normal
Manually interpret signals and intervene

Disaster
Recovery point
Data loss

“There must be an
incredible amount of
radiation here. We'll be
lucky if we're all still
alive in the morning.”
– Anatoli Zakharov, Fire Station 2 Chernobyl

Disaster
Recovery point Recovery time
Data loss
Down time

And yet…

• Unplanned event causes
coolant failure
• Uncontrolled fuel rod triggers
meltdown event
• Uncontrolled release of steam
triggers explosion
• Generator present, but failure
occurs
• Unplanned event causes
coolant failure
• Uncontrolled fuel rod triggers
meltdown event
• Uncontrolled release of steam
triggers explosion
• Generator present, but failure
occurs
C h e r n o b y lF u k u s h i m a D a i i c h i
Shared failures

Lessons learned?
Failure is not one thing

What are we really planning for?

Techniques:
Common disaster recovery
methods

Pilot light

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

Database
server
Pilot light—recovery
www.example.com
Start in minutes
Add additional
capacity,
if needed
Reverse
proxy/
caching
server
Data
volume
Application
server
Reverse
proxy/
caching
server
Application
server
Master
Database
server

Warm standby

Warm standby—prep
Mirroring/replication
Application
data source
cut over
Elastic
load
balancerActive
Not active for
production traffic
Amazon
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

Warm standby—recover
Elastic
load
balancer
Active
Route 53
www.example.com
Scaled-up
production
Data
volume
Application
server
Database
server
Reverse
proxy/
caching
server
AWS Region
Reverse
proxy/
caching
server
Application
Server
Master
Database
server

Hot site

Hot site—prep
Mirroring/replication
Application
data source
cut over
Elastic
load
balancerActive
Route 53
www.example.com
Data
volume
Application
server
Subordinate
database
server
Reverse
proxy/
caching
server
AWS Region
Reverse
proxy/
caching
server
Application
server
Master
Database
server
Active

Hot site—recovery
Elastic
load
balancer
Route 53
www.example.com
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

Disaster recovery is not just
backups

Use case 1
Basic backup and recovery use case

$ aws s3 sync /backups s3://mybucket
;Back up and sync the backup folder
$ aws s3 sync /backups s3://mybucket --delete
;Like the preceding, but now delete files not present
$ aws s3 sync /backups s3://mybucket --delete –storage-
class STANDARD_IA
;Like the preceding, but now leverages Infrequent access
AWS CLI-based backup, manual DR failover

What does it look like?
S3 Amazon
Glacier
S3 bucket
Remote location
/mybucket
S3
STANDARD_IA
1
2
Lifecycle
policy

What does a recovery look like?
Failover Remote location
2
AWS DR Region
Amazon
EC2
S3 Amazon
Glacier
S3 bucket
/mybucket
S3
STANDARD_IA
1
Lifecycle
policy

What would it cost?
S3
STANDARD_IA
S3 Amazon Glacier
$ 0.0125/GB $ 0.023/GB $ 0.004/GB
Service Cost
S3 10 GB images $0.23
S3–IA 100 GB of data $1.25
Amazon Glacier–1 TB archives $4.10
Total $5.58/mo
Shown: us-east-1

Use case 2
Large data archive and recovery

Large data set
AWS cloud
NGS
On-premises
compute /cluster
Sequence data
Flowcell-ID
Amazon Glacier
2 3
AWS
Snowball device
AWS CLI
1
AWS Snowball

Large data set
AWS cloud
NGS
On-premises
Compute / cluster
Virtual server
ISCSI
Cached
volume
1
2
virtual tape
library
AWS
Storage Gateway
Amazon
Glacier
Amazon
S3
AWS
Storage Gateway Amazon
S3

Large data set
NGS
On-premises
Compute / cluster
File
Gateway
NFS
AWS cloud - US-
West-2
Amazon
S3
S3
bucket
Lifecycle
policy
AWS cloud US-
East-1
Amazon
S3
S3
bucket
File Gateway VM

Large data set—recovery
AWS DR Region
Sequence data
Flowcell-ID
Amazon Glacier
Corporate DR facility
Server infrastructure
1
AWS Snowball
S3 VPC endpoint
AWS DR Region
2
Amazon
EC2

AWS DR Region
NGS
On-premises
Compute/cluster
AWS
Storage Gateway
Virtual server
ISCSI
Cached
volume
1
Amazon
Glacier
Amazon
S3
instance
2
AWS DR Region
EBS
snapshot
virtual tape
library
AWS DR Region
instance
AMI
Amazon EBS

AWS DR Region
Amazon S3
S3 bucket
NGS
On-premises
Compute/cluster
File
Gateway
AWS DR Region
Amazon
EC2
1
2
3
S3 endpoint
NFS
File Gateway VM

What did it cost? — scenario gateways
File Storage Volume Storage VTL - Archived
$ 0.023/GB $0.023/GB $ 0.004/GB
Service Cost
File Gateway—10 TB $235.40
Storage Gateway—32 TB $736
Storage Gateway VTL—250TB $1,000
Total $1,971.4/mo
Shown: US-West-2

What did it cost? — scenario Snowball
S3 Snowball -edge Amazon Glacier
$ 0.023/GB $300/100TB $ 0.004/GB
Service Cost
AWS SnowBall * 10 $3,000.00
Amazon Glacier archive 1 PB $4,194.31
Total $ 7,194.31
$4,194.31 /mo
Shown: US-West-2

Massive data move

Use case 3
Onsite virtualization replication,
backup, and failover

Corporate data center AWS cloud
Storage
Gateway
iSCSI from
Storage
Gateway to
ESX Hosts
VMFS
VMware ESX VMware ESXi
Replication
Appliance
Onsite VM replication/convert
Stored
volume

Corporate data center AWS cloud
iSCSI from
AWS Storage
Gateway to
ESX Hosts
VMFS
VMware ESX VMware ESXi
AMI
EBS
VM
Import
Onsite VM replication/convert – recovery
Storage
Gateway
Stored
volume
Amazon
S3
Replication
Appliance

What did it cost?
S3 Storage Gateway
$ 0.023/GB $0.00
Service Cost
Storage Gateway archive (32 TB) $753.67
Storage Gateway VM cost $0
Total $753.67/mo
Shown: US-West-2

VMware Cloud on AWS

Deploy and consume native AWS services
Customer VPC VMware Cloud VPC
Customer Data Center
AWS Direct
Connect
VMware Cloud
Endpoints
VPC subnet VPC subnet
VPC subnet
Private Managed
AWS ServicesCustomer Instances
vSphere Environment
VMware
Endpoints
Non-vSphere Environment
ESXi
ESXi
Amazon EC2
Internet
Private
VIF
Public
VIF
Regional AWS Services
AWS
Lambda
Amazon
S3
Amazon
CloudFront
Etc…

Use case 3a
High availability windows server
storage

Data center SMB server with SGW backend
SMB hosted onsite, blocks stored durably in Amazon S3
Private Datacenter
Storage
Gateway VM
us-west-2
Storage
Gateway
Volume
Windows
Clients
Windows Server
HTTPSiSCSISMB

High availability Windows server storage
Local HA with remote DR
us-east-1
Data Center
Windows
Clients Storage
Gateway VMMicrosoft DFS
HTTPSiSCSI
HTTPSiSCSI
SMB
Storage Gateway Service
us-west-1
Microsoft DFS
HTTPSiSCSI
Storage Gateway Service

Use case 4
Multisite replication and failover

AWS
Direct Connect
VPN
us-east-1
us-west-2
Server
Server
Availability Zone Availability Zone
Failback
Server
Multisite failover
customer
gateway
users Equinix DA1

Direct Connect
VPN
us-east-1
us-west-2
Failback
AWS
CloudFormation
Server
Availability Zone Availability Zone
Server
Multisite failover
Server
users
customer
gateway
Equinix DA1

What did it cost? (30 days)—remote site
VPC VPN EC2 *
(m4.xlarge)
1 Gb
Direct Connect
EBS Region data
transfer fee
$ 0.05/hr $ 0.20/hr $ 0.30/hr $ 0.10/GB $ 0.02/GB
Service Cost
1 GB Direct Connect $219.60
VPN Fallback Connection $36
(2) EC2 instances $292.80
(2) EBS 60 GB volumes $12
(1) AMI copy to us-west-2 $1.20
Total $561.60
*US-West-2, Amazon Linux AMI

Use case 5
Knowledge worker DR site

Workspaces for worker DR
Customer VPC
Active
Directory
Corp servers
Direct Connect
or VPN
Customer
corporate
network
Customer AD
RO/Replica
EC2
corporate
servers
MFA (RADIUS) (Optional)
Archives
S3

Internet
Users
Standalone
Network
Customer VPC
AD
RO / Replica
Public AWS
endpoint
Streaming
Gateway
9
Amazon WorkSpaces
(network entry point)
Amazon EC2
corporate
servers
Customer
corporate network
Amazon S3
Workspaces for worker DR

What did it cost? — 30 Days
Workspaces
(Standard)
EC2 *
(m4.xlarge)
EBS
(GP SSD)
S3 VPC VPN
$ 35 /
Workspace
$ 0.20 / Hour $ 0.10 $ 0.023 / GB $ 0.05 / Hour
Service Cost
Workspaces for 25 users $875
(2) AD EC2 + 100GB EBS $312.80
VPC VPN $36
S3 file backups (500GB) $11.50
(1) Share point W/ 2TB EBS $346.40
Total $1,581.70/Mo
Shown: US-West-2, Windows Standard AMI

Use case 6
Compliance DR site

C5 [Germany]
Cyber Essentials Plus [UK]
DoD SRG
FedRAMP
FIPS
IRAP [Australia]
ISO 9001
ISO 27001
ISO 27017
ISO 27018
MLPS Level 3 [China]
MTCS [Singapore]
PCI DSS Level 1
SEC Rule 17-a-4(f)
SOC 1
SOC 2
SOC 3
DNB [Netherlands]
EAR
EU Model Clauses
FERPA
GLBA
HIPAA
HITECH
IRS 1075
ITAR
My Number Act [Japan]
U.K. DPA - 1988
VPAT / Section 508
EU Data Protection Directive
Privacy Act [Australia]
Privacy Act [New Zealand]
PDPA - 2010 [Malaysia]
PDPA - 2012 [Singapore]
PIPEDA [Canada]
Spanish DPA Authorization
CIS
CJIS
CLIA
CMS EDGE
CMSR
CSA
EU-US Privacy Shield
FISC
FISMA
G-Cloud [UK]
GxP (FDA CFR 21 Part 11)
ICREA
IT Grundschutz [Germany]
MITA 3.0
MPAA
NIST
PHR
Uptime Institute Tiers
UK Cloud Security Principles
Certifications/
attestations
Laws, regulations,
and, privacy
Alignments/
frameworks
AWS assurance programs

Compliance enabled failover
Server
users
disk
database
tape storage
Primary
Government

Compliance enabled failover
Server
users
disk
database
tape storage
Primary
Government
us-west-2
Server
Availability Zone
Disk
Database Backup
Users
AWS Artifact

Cloud lightning round!!!

Use case 7a
All in on AWS: Amazon EC2 snapshot
trick

”I want to copy my EC2
instance data via EBS
snapshot...”

..but not lose data.

amzn.to/2nAz7n6

Leverage the power of Amazon EC2 Systems
Manager
#!/bin/bash
mysql -u backup -h localhost -e 'FLUSH TABLES WITH READ LOCK;’
sync
for target in $(findmnt -nlo TARGET -t ext4); do fsfreeze -f $target; done
instance=`curl -s http://169.254.169.254/latest/meta-data/instance-id` region=`curl -s
169.254.169.254/latest/meta-data/placement/availability-zone` region=${region::-1} volumes=`aws
ec2 describe-instance-attribute --instance-id $instance --attribute blockDeviceMapping --output
text --query BlockDeviceMappings[*].Ebs.VolumeId --region $region`
for volume in $(echo $volumes | tr " " "n") do aws ec2 create-snapshot --volume-id $volume --
description 'Consistent snapshot of MySQL on Amazon Linux' --region $region > /dev/null 2>&1
done
for target in $(findmnt -nlo TARGET -t ext4);
do fsfreeze -u $target; done
mysql -u backup -h localhost -e 'UNLOCK TABLES;'
Amazon EC2
Systems Manager

Use case 7b
All in on AWS: EC2 instance crashed!

Amazon EC2
Auto Recovery
Set your failed check threshold
Choose 1-minute period
and statistic minimum
Choose recover action
Metric = StatusCheckFailed_System

Amazon EC2
Auto Reboot
Choose reboot action
Metric = StatusCheckFailed_Instance

Use case 7c
All in on AWS: Amazon S3 data loss!

“I’m worried about losing data from S3!”
• Amazon S3 is built for 11 9’s of durability
• If you store 10,000 objects, you can on average expect to
incur a loss of a single object once every 10,000,000 years.
• Amazon S3 supports cross region replication
• Amazon S3 supports versioning
• Amazon S3 supports MFA delete
• IAM roles can also be used to limit access to S3
Amazon
S3

Use case 7d
All in on AWS: RDS replication – Failover

RDS Database
• RDS automatic backup/snapshots
• RDS supports cross region read replicas for MySQL,
PostgreSQL, Aurora DB, or MariaDB
Amazon
RDS

Use case 7e
All in on AWS: AWS Database Migration
Service

DBMS:
• Continuous or one time DB replication to EC2 or RDS
• Leverage DBMS to replicate your database to AWS or
even change your schema from one engine to another
AWS DMS

What about third party
support?

Amazon BC/DR partner ecosystem (sample)
• Solutions that utilize AWS to enable recovery strategies
• Focused on RTO and RPO requirements
• Full suite of both cold and warm BC/DR solutions

Malibu Boats/CloudEndure case study
Challenges
• Prevent downtime, which would shut down
factories and be very costly
• Achieve near-zero RPO and RTO
• Ability to recover to previous points in time
• Multi-regional resilience in order to prevent
weather-related outages
• Failback to primary data center without disruption
or data loss
“[We] quickly noticed that the performance of the
server on the AWS environment was at least
twice as fast as it was on our current data center
environment, using the same hardware
specifications, the same memory, and CPU,
which was quite eye-opening, and helped us to
move forward our plans to a fuller presence in
AWS and the cloud.”
-Greg Ward, VP of IS & Technology
Why AWS, CloudEndure, and Rackspace
• Fast recovery, near-zero RPO and RTO
• Cost of cold-standby with performance
of warm-standby
• Multiple checkpoints for point-in-time recovery
• Automated failback to source machines
• Unlimited, non-disruptive DR testing

Putting it all together

Lessons from history
Plan for more than just what
you expect to happen

Test your execution plan
before you think you can
implement it

Knowledge is critical. Know
how to interpret an alarm on
events.

Words of advice
People generally don’t do well under pressure
• Automate as much as you can
• Table top exercises can really help you understand
roles and responsibility
• Not all services have to require the same RTO/RPO
• Seriously, automate as much as you can ahead of time
• If you don’t have a run book, it’s time to make one
• If you have one, have you tested it?

So, one more thing…

#alexa-failover
When automation automated itself

Remember to complete
your evaluations!

Thank you!

Disaster Recovery with AWS: Tiered Approaches to Balance Cost with Recovery Objectives - ENT322 - re:Invent 2017

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Disaster Recovery with AWS: Tiered Approaches to Balance Cost with Recovery Objectives - ENT322 - re:Invent 2017

Similar to Disaster Recovery with AWS: Tiered Approaches to Balance Cost with Recovery Objectives - ENT322 - re:Invent 2017 (20)

More from Amazon Web Services

More from Amazon Web Services (20)

Disaster Recovery with AWS: Tiered Approaches to Balance Cost with Recovery Objectives - ENT322 - re:Invent 2017