Deploying a Disaster Recovery Site on AWS: Minimal Cost with Maximum Efficiency
Deploying a Disaster Recovery Site on AWS: Minimal Cost with Maximum Efficiency
-
Upload
amazon-web-services -
Category
Technology
-
view
1.297 -
download
1
Transcript of Deploying a Disaster Recovery Site on AWS: Minimal Cost with Maximum Efficiency
© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Brad Dispensa, Sr. Solutions Architect – WWPS
April 19, 2016
Deploying a Disaster Recovery Site
on AWS
Minimal Cost with Maximum Efficiency
What do I expect you to know?
• 300-level talk
• Have some prior experience with AWS
• Understand/know basic terms, like Amazon EBS, Amazon S3, and
Amazon EC2
"I get it and want to learn more."
• Sessions will dive deeper into the topic. Presenters assume the
audience is familiar with the topic but may or may not have direct
experience implementing a similar solution. Code may be shared but
will not be the primary focus of the session.
We are historians…even if you don’t know it.
"Shut up, shut up! I am
busy…”- Jack Phillips, RMS Titanic telegraph operator
Recovery point
DisasterRecovery point
Data loss
"SOS, SOS,CQD,CQD
MGY. We are sinking
fast - passengers are
being put into boats..
MGY”- Titanic last radio call
DisasterRecovery point Recovery time
Data lossDown time
Lessons learned?Failure is not one thing…
Disaster recovery as
an eventaka watch this...
Pi
MQ-7
AWS cloudCorporate data center
AWS
Lambda
AWS
CloudFormationAmazon
Kinesis
Amazon
Route 53
AWS cloud
Corporate data center
CloudFormation
Amazon
Route 53
Auto Scaling group
Availability Zone #1
Security group
security group
Root volume
Data volume
EC2 instance
Web app
server
What did it cost?
MQ-7 R-PI 2 Route 53 S3
$10/sensor $42 $0.53/zone $ 0.03/GB
Service Cost
S3 bootstrap
script repo
$.03
Hardware $52
Route 53 DNS $0.53
Total $52.56
How can I do this?
What are we planning for?
Techniques for disaster
recovery
Pilot light
Subordinate
database
server
Pilot light–prepwww.example.com
Data mirroring replication
Not running
Pilot light system
Reverse
proxy/
caching
server
Datavolume
Application
server
Corporate data center
Reverse proxy/ caching server
Application server
MasterDatabase
server
Database
server
Pilot light–recoverywww.example.com
Start in minutes
Add additional
capacity,
if needed
Reverse
proxy/
caching
server
Datavolume
Application
server
Corporate data center
Reverse proxy/ caching server
Application server
MasterDatabase
server
Warm standby
Warm standby–prep
Mirroring /replication
Application data source
cut over
Elastic load
balancerActiveNot active for
production traffic
Route 53
www.example.com
Scaled down
standbyCorporate data center
Datavolume
Applicationserver
Subordinatedatabase
server
Reverse proxy/ caching server
AWS region
Reverse proxy/ caching server
Application server
MasterDatabase
server
Warm standby–recover
Elastic load
balancerActive
Route 53
www.example.com
Scaled-up
production
Corporate data center
Datavolume
Applicationserver
Databaseserver
Reverse proxy/ caching server
AWS region
Reverse proxy/ caching server
Application Server
MasterDatabase
server
Hot site
Hot site–prep
Mirroring /replication
Application data source
cut over
Elastic load
balancerActiveRoute 53
www.example.com
Corporate data center
Datavolume
Applicationserver
Subordinate database
server
Reverse proxy/ caching server
AWS region
Reverse proxy/ caching server
Application server
MasterDatabase
server
Active
Hot site–recovery
Elastic load
balancerRoute 53
www.example.com
Corporate data center
Datavolume
Applicationserver
Databaseserver
Reverse proxy/ caching server
AWS region
Reverse proxy/ caching server
Application server
MasterDatabase
server
Active
Scaled up
for production
use
Use case 1 DR for entry-level users
AWS CLI-based backup
$ 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
What does it look like?
Remote location
S3 Amazon
Glacier
S3 bucket
/mybucket
S3
STANDARD_IA
1
2
What did it cost?
S3
STANDARD_IA
S3 Amazon Glacier
$ 0.0125/GB $ 0.03/GB $ 0.007/GB
Service Cost
S3 10 GB images $.30
S3–IA 100 GB of data $1.25
Amazon Glacier–1 TB archives $7.00
Total $8.55/mo
Use case 2Large data archive needs and failover
Large data set
AWS cloud
AWS Import/Export
Snowball
Corporate data center
NGS
On-premises
compute /cluster
Sequence dataPhysical media
Flowcell-ID
AWS CLI
Amazon Glacier
1 3
AWS
Import/Export
Snowball
or
2
Large data set
AWS cloud
Corporate data center
NGS
On-premises
Compute / cluster
AWS
Storage GatewayVirtual server
Amazon S3
ISCI
Cached
volume
1
2
Large data set–Recovery
AWS cloud
AWS Import/Export
Corporate data center
NGS
On-premises
Compute / cluster
Sequence data
Flowcell-ID
Amazon Glacier
1
Physical media
AWS
Import/Export
Snowball
or
Large data set–Recovery
AWS cloud
Corporate data center
NGS
On-premises
compute/cluster
AWS
Storage GatewayVirtual server
S3
ISCI
Cached
volume
2
1
What did it cost?
S3 Import/Export Amazon Glacier
$ 0.03/GB $2.49 per data-loading hour + $80
per storage device
$ 0.007/GB
Service Cost
S3 10 TB $300
Import/Export 1 PB** - Variable
Amazon Glacier archive 1 PB $7,000
Total $7,300/mo
**Factors include drive type, amount of drive.
Use case 3 Onsite virtualization replication,
backup, and failover
Corporate data center AWS cloud
Storage
Gateway
S3
iSCSI from
Storage
Gateway to
ESX Hosts
Storage
Gateway
cached volume
to S3
VMFS
VMware ESX VMware ESXi
Replication
Appliance
Onsite VM replication/convert
Corporate data center AWS cloud
Storage
Gateway
S3
iSCSI from
AWS Storage
Gateway to
ESX Hosts
Storage Gateway
cached volume
to S3
VMFS
VMware ESX VMware ESXi
Replication
Appliance
AMI
EBS
VM
Import
Onsite VM replication/convert
What did it cost?
S3 Storage Gateway
$ 0.03/GB $125.00
Service Cost
Storage Gateway archive (32 TB) $960
Storage Gateway VM cost $125
Total $1,085/mo
Use case 4 Multisite replication and failover
Corporate data center
AWS
Direct Connect
VPN
us-east-1
us-west-2
Server
Server
Availability Zone Availability Zone
Failback
Server
Multisite failover
Corporate data center
Direct Connect
VPN
us-east-1
us-west-2
Server
Failback
AWS
CloudFormation
Server
Availability Zone Availability Zone
Server
Multisite failover
AWS cloudCorporate data center
Route 53
Docker servers
www.example.com
DatabaseAmazon RDS
Data mirroring replication
Storage
Gateway
Container failover
Snapshot
S3
Amazon ECS
AWS cloudCorporate data center
Route 53
www.example.com
RDS
Amazon
ECS
cluster
Container failover
EBS
Data /
code
repo
S3
What did it cost? (30 days)–Remote site
VPC VPN EC2 *
(m4.xlarge)
1 Gb
Direct Connect
EBS Region data
transfer fee
$ 0.05
/Hour
$ 0.252 $ 0.30/Hour $ 0.10/GB $ 0.02/GB
Service Cost
1 GB Direct Connect $216
VPN Fallback Connection $36
(2) EC2 instances $362.88
(2) EBS 60 GB volumes $12
(1) AMI copy to us-west-2 $1.20
Total $628.08*us-west-2, Amazon Linux AMI
What did it cost? (30 days)–Docker
Storage
Gateway
EC2 Route 53 RDS EBS Elastic Load
Balancing
$ 125.00 $0.252/
Hour
$0.53/
Zone
$0.185/
Hour
$0.10/GB $0.025/Hour
Service Cost
Storage Gateway $125
Route 53 DNS $0.53
Elastic Load Balancing $18
RDS (MySQL) db.m3.large $133.20
(3) ECS cluster nodes m4.xlarge + (3) 30 GB EBS $553.32
Total $821.05/mo
Use case 5 Knowledge worker DR site
Workspaces
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
Workspaces
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
What did it cost? – 30 Days
Workspaces(Standard)
EC2 *
(m4.xlarge)
EBS
(GP SSD)
S3 VPC VPN
$ 35 /
Workspace
$ 0.504 / Hour $ 0.10 $ 0.03 / GB $ 0.05 / Hour
Service Cost
Workspaces for 25 users $875
(2) AD EC2 + 100GB EBS $725.76
VPC VPN $36
S3 file backups (500GB) $15
(1) Share point W/ 2TB EBS $563.88
Total $2215.64/Mo*us-west-2, Windows standard
Use case 6Untethered IT
Mobile console
Ability to recover when
you’re mobile.
Conclusion
Lessons from history
Plan for more than just what
you expect to happen.
Lessons from history
Test your execution plan
before you think you can
implement it.
Lessons from history
Knowledge is critical. Know
how to interpret an alarm on
events.
So how easy can I make this?
“Alexa, fail over my data center”
#Alexafailover
Remember to complete
your evaluations!