Disaster Recovery Site on AWS: Minimal Cost Maximum Efficiency discusses setting up disaster recovery sites on AWS for minimal cost and maximum efficiency. Common disaster recovery architectures on AWS include pilot light, where a scaled-down copy of production resources is kept running, and backup and restore, where backups are taken and restored in an outage. Customer case studies demonstrate cost savings of up to 70% for disaster recovery sites on AWS compared to on-premises solutions.
2. What you will learn
•
•
•
•
Why AWS for disaster recovery?
Common DR architectures
– Pilot light architecture
• Demo
• Code walkthrough
– Backup and restore
Customer case studies
Where to go next
3. Conventional Disaster Recovery sites
•
•
•
•
•
•
High cost
Low ROI
Implemented only for most critical systems
Usually scaled down to 50% of production
Systems in a remote region challenging
Costly software licenses based on hardware usage
4. Disaster Recovery site on AWS
•
•
•
•
Unprecedented capabilities to implement DR sites
Easily setup DR sites on different geographic regions
Cut down DR site cost by up to 70%
Substantial savings on software licenses
9. Pilot light architecture
Build resources around
replicated dataset
Keep ‘pilot light’ on by replicating core
databases
Build AWS resources around dataset and
leave in stopped state
10. Pilot light architecture
Build resources around
replicated dataset
Scale resources in AWS in
response to a DR event
Keep ‘pilot light’ on by replicating core
Start up pool of resources in AWS when
databases
events dictate
Build AWS resources around dataset and
Scale up the database instance to handle
leave in stopped state
production capacity
13. Simple DR solution – awsdrdemo.com
Active
Passive
Active
Elastic
Load
Balancing
Scaled down
Standby
Amazon
Route 53
Copy AMI
Web/ App
servers
Web/ App
Server AMI
Auto scaling Group
Oracle
Master
DB
Setup Data Replication
Oracle
Slave DB
Data
Volume
US East (N. Virginia)
US West (N. California)
14. Simple DR solution – awsdrdemo.com
DNS
Failover
Active
Gone
Elastic
Load
Balancing
Web/ App
servers
Active
Active
Elastic
Load
Balancing
Amazon
Route 53
Web/ App
servers
Autoscale
Auto Scaling group
Oracle
Slave DB
Oracle
Master
DB
Data
Volume
US East (N. Virginia)
Scale up
DB
Data
Volume
US West (N. California)
15. Architecture
failover.awsdrdemo.com
awsdrdemo.com
Active
Active ELB:
DRDemoPrimaryELB52152634.us-east1.elb.amazonaws.com
Web Servers:
i-36af5751
AMI Copy
(ami-996634f0)
Web/ App
server
VPC ID - vpc-5f9ef53e
Subnet IDssubnet-440c786c
subnet-289ef549
subnet-2c9ef54d
Primary Database Server:
(i-026aad65)
Private IP
174.168.1.11
Amazon
Route 53
Passive
DR ELB Created on Failover
Failover App Instance:
i-55cfde0e
Elastic IP
54.215.157.25
Webserver
Failover
AMI
App
AMI - Scaled down
Standby
Active Mirroring /
Replication
Primary
Data
US East (N. Virginia)
Volume
Secondary
DB
Data
Volume
US West (N. California)
Web Servers Created on Failover
VPC ID - vpc-a4f2efcc
Subnet IDssubnet-bbf2efd3
subnet-884b01ce
subnet-bef2efd6
Secondary Database Server:
(i-3b266960)
Private IP
174.168.1.11
32. Backup & Restore pattern
Simple to get started
Cost-effective
Easy starting point for exploring the
Very high levels of data durability at
AWS cloud
low price
Low technical barrier to entry
Cost of storing snapshots in
Focus on incorporating cloud into your
Amazon S3
DR strategy, not on complex technical
Archiving possibilities beyond tape
issues related to hot-hot systems
using Amazon Glacier