8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
1/48
Disaster Recovery using AWSArchitecture Blueprints
Harish Ganesan
Co founder & CTO
8KMileswww.twitter.com/harish11ghttp://www.linkedin.com/in/harishganesan
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
2/48
Explore various ways of architecting Disaster
recovery using Amazon cloud (AWS)
Sample architecture element contains Managed
DNS servers , Load Balancers and Data
replicators
Failover , Scalability , Load Balancing ,
Monitoring ,Back up/Recovery and High
Availability is factored in the architecture Blue
prints
Introduction
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
3/48
Blue print1 :Both Main Site and Disaster
recovery site in AWS Cloud
Blue print2 : Main site in AWS cloud andDisaster recovery site in Traditional customer
data center
Blue print3 : Main site in customer data center
and Disaster recovery site in AWS cloud
DR Architecture blueprints using AWS
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
4/48
AWS Security groups
AWS Elastic Load balancing
AWS Auto Scaling
AWS EC2 & EBS AWS CloudWatch
AWS Elastic IP
AWS S3
List of AWS used in DR Blue prints
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
5/48
Managed DNS
LAMP (or) LAMJ stack
MySQL Master- Master replication
SOLr Search servers Schedulers and Back ground programs
List of Other Architectural components used
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
6/48
Blue Print 1 : Main and DR website in AWS
Main web site is hostedin AWS USA east region
Disaster Recovery (DR)web site is hosted in
AWS Europe region
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
7/48
Blue Print 1 : Main and DR website in AWS
Main website inAWS Cloud
Disaster Recoverywebsite in AWSCloud
AWS USA east region
AWS Europe region
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
8/48
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
9/48
Main website(MWS) hosted in AWS USA east
Disaster recovery website(DRW) hosted in AWS
Europe
Managed DNS passes the web requests to Main
website under normal circumstances
AWS Elastic Load Balancer of MWS passes the
request to appropriate web/app servers
Web / App servers are Amazon EC2 instances
configured with AWS EBS
Web / App servers are enabled with Boot from EBS
Blue Print 1 : Architecture Explanation
Continued
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
10/48
Web/App servers are configured with AWS
auto scaling ( Min 2 and Max 20)
MySQL Data base servers are configured in
Master-Master replication mode
MySQL M-M replication inside Main site
(MWS)
MySQL M-M replication between Main and DR
site ( Asynchronous mode)
MySQL Servers are Amazon EC2 instances with
AWS EBS ( Both Main and DR site)
Blue Print 1 : Architecture Explanation
Continued
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
11/48
MySQL servers are manually scaled in Main site
Main website (MWS) is monitored using AWS
CloudWatch
An exact replica of Main website infrastructure
can be run as DR website in AWS Europe
Web/App servers in DR website can be
configured with AWS auto scaling ( Min 1 and
Max 10)
In event of failure , managed DNS will pass the
requests to DR website in Europe
Blue Print 1 : Architecture Explanation
Continued
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
12/48
Disaster recovery (DR) website can take over the
requests seamlessly from the main website in
this architecture
DR website can also auto scale its capacity
depending upon the load , in short it can handle
whatever the main site is architected for
Once the Main site is up, the Managed DNS will
pass the web requests and DR website can
Shrink down automatically to minimum capacity
Blue Print 1 : Architecture Explanation
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
13/48
Inter regional DR for High Availability
DR site can act immediately in event of Main
site failure
DR site is designed to handle same load as the
Main site
No compromises on the DR site with respect to
Scalability, Security , Monitoring and Stability
Elastic: DR site can expand and Shrink according
to load like Main site
Cost effective and Highly available architecture
Blue Print 1 : Positives
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
14/48
Complete Dependency on AWS cloud
Technical intricacies in moving EBS volumes , S3
snapshots , AMIs between AWS USA and Europe
regions
Migration cost of moving both Main and DR site
to the AWS Cloud
Impacts on existing customer data center
contracts
Impact of typical cloud problems like Slow IO,
privacy and regulations apply here
Blue Print 1 : Negatives
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
15/48
Blue Print 1 : Architectural Objectives
Objectives Main site DR site
Elastic Load balancing
Auto Scaling
Failover
High Availability
Monitoring
Management
Replication inside a region
Replication across regions
Security Backups
Recovery
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
16/48
Elastic Block Storage (EBS)
Amazon Elastic Block Store (EBS) provides block level
storage volumes for use with Amazon EC2 instances.
Amazon EBS is particularly suited for applications
that require a database, file system, or access to rawblock level storage.
Our Use case :Application executables ,
configurations , Data base files and OS are installed
in the AWS EBS in this reference architecture .
Solution Components : EC2 and EBS
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
17/48
Simple Storage Service (S3)
Amazon S3 provides a simple web services interface
that can be used to store and retrieve any amount of
data, at any time, from anywhere on the web.
Our Use case : The application data files that areuploaded , AWS EBS snapshots are stored in S3.
Solution Components : AWS S3
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
18/48
Elastic Load Balancer (ELB)
Elastic Load Balancing automatically distributes
incoming application traffic across multiple Amazon
EC2 instances.
Elastic Load Balancing detects unhealthy instanceswithin a pool and automatically reroutes traffic to
healthy instances until the unhealthy instances have
been restored.
Our Use case : Load Distributed among Servers
located in Multiple AZ and Dynamically Auto Scaled
EC2 instances
Solution Components : AWS ELB
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
19/48
Auto Scaling
Auto Scaling allows you to automatically scale your
Amazon EC2 capacity up or down according to
conditions you define.
Auto Scaling is particularly well suited forapplications that experience hourly, daily, or weekly
variability in usage.
Our Use case : EC2 Server instances dynamically
Scaled up and Down depending upon the Load using
the Auto scaling
Solution Components : AWS Auto Scaling
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
20/48
AWS CloudWatch
Amazon CloudWatch enables you to monitor your
Amazon web services in real-time.
Amazon CloudWatch helps us to access up-to-the-
minute statistics, graphs, and set alarms for ourmetric data.
Our Use case : EC2 servers , EBS , ELB are monitored
and alerts are sent using AWS CloudWatch
Solution Components : AWS CloudWatch
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
21/48
Managed DNS
a solution that can monitor the health of multiple
endpoints or websites and automatically failover at
DNS level in case of a failure at the primary website
Our Use case : Used for transparent switch betweenMain and Disaster recovery website during failures
Solution Components : Managed DNS
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
22/48
MySQL Replication
MySQL will be setup in Master Master replication
mode
M-M setup offers failover inside data center as well
as across Data centers Data Replication will be done asynchronously
Our Use case : Data is replicated between Main and
DR website MySQL database using Master-Masterreplication
Solution Components : MySQL replication
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
23/48
Blue Print 2 : Main site in AWS
Main web site is hostedin AWS USA east region
Disaster Recovery (DR)
web site is hosted in USAWest in a Traditional
data center
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
24/48
Blue Print 2 : Main site in AWS
Main website inAWS Cloud
DR website inTraditional data
center
AWS USA east
Traditional Data center- USAWest
Blue Print 2: Main site in AWS DR site in Traditional DC
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
25/48
MySQL
Master
AWS Auto scaling / AWS Elastic Load
Balancer
ELB redirects incoming requests tosame Web / APP server based onSession Sticky Algorithm
Blue Print 2: Main site in AWS DR site in Traditional DC
MySQL
Master
CL
O
U
D
W
A
T
C
H
D
Master
Master Datareplication
MySQL Master Master Datareplication
Main Site - AWS USA
Region
GEO IP / Directional DNS Servers
GEO IP / Directional DNS Servers directs the user requests toMain site in AWS USA region. In case of Disaster in Main site,the web requests are directed to DR site in USA West
1
3
2
EC2
EBS
Elastic IPWeb/App Servers
MySQL
Master
Manual scaling / Load Balancer
MySQL
Master
M
O
N
I
T
OR
S
Web/App Servers
D
DR Site Traditional DC in
USA west
Search Servers
Schedulers/BG
Search Servers
Schedulers/BG
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
26/48
Main website(MWS) hosted in AWS USA east
DR website(DRW) hosted in Traditional data
center in USA West
Managed DNS passes the web requests to Main
website under normal circumstances
AWS Elastic Load Balancer of MWS passes the
request to appropriate web/app servers
Web / App servers are enabled with Boot from
EBS in Main site
Blue Print 2 : Architecture Explanation
Continued
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
27/48
Web/App servers are configured with AWS
auto scaling ( Min 2 and Max 20) in Main site
MySQL Data base servers are configured in
Master-Master replication mode
MySQL M-M replication inside Main site
(MWS)
MySQL M-M replication between Main and DR
site ( Asynchronous mode)
MySQL Servers are Amazon EC2 instances with
AWS EBS in Main site
Blue Print 2 : Architecture Explanation
Continued
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
28/48
MySQL Servers are virtualized instances
configured with Network storage in DR site
MySQL servers are manually scaled in both sites
Main website (MWS) is monitored using AWS
CloudWatch
DR website will be monitored using Traditional
data center tools
Web/App servers in DR website runs on minimal
capacities
Blue Print 2 : Architecture Explanation
Continued
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
29/48
In event of failure , managed DNS will pass the
requests to DR website in USA West
DR website can take over the requests
seamlessly from the main website
DR website cannot scale its capacity depending
upon the load , since it is runs on a minimal non
elastic capacity it cannot handle similar loads of
Main site
Blue Print 2 : Architecture Explanation
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
30/48
DR site MAY act immediately in event of Main
site failure (depending upon hot /warm/cold DR
strategies)
Leverage the existing infra contracts with
Traditional data center provider
Cloud adoption and migration in phases (first
main site followed by DR site)
Main Site handles load and DR site is a low cost
Stop gap alternative during failures
Partial dependency on AWS
Blue Print 2 : Positives
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
31/48
Very complicated architecture for management
2 types of monitoring , provisioning, backup
,Security etc , In short 2 different infrastructure
architectures has to be maintained by the sys
admins Can turn in to a maintenance nightmare if not
administered well
DR site cannot handle and sustain the loads of
Main site .
Cannot guarantee High availability
Cost ineffective on the Sys Administration front
Blue Print 2 : Negatives
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
32/48
Blue Print 2 : Architectural Objectives
Objectives Main site DR site
Elastic Load balancing X
Auto Scaling X
Failover
High Availability X
Monitoring
Management
Replication inside a region
Replication across regions
Security Backups
Recovery
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
33/48
Blue Print 3 : DR site in AWS
Main web site is hosted
in Traditional Data center
in USA east region
Disaster Recovery (DR)
web site is hosted inAWS USA West Region
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
34/48
Blue Print 3 : DR site in AWS
DR website in AWSCloud
Main website inTraditional data
center
AWS USA west
Traditional Data center- USAeast
Blue Print 3: DR site in AWS Main site in Traditional DC
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
35/48
MySQL
Master
AWS Auto scaling / AWS Elastic Load
Balancer
ELB redirects incoming requests tosame Web / APP server based onSession Sticky Algorithm
Blue Print 3: DR site in AWS Main site in Traditional DC
MySQL
Master
CL
O
U
D
W
AT
C
H
D
Master
Master Datareplication
MySQL Master Master Datareplication
DR Site - AWS USA west
Region
GEO IP / Directional DNS Servers
GEO IP / Directional DNS Servers directs the user requests toMain site in USA east region. In case of Disaster in Main site,the web requests are directed to DR site in AWS USA Westregion
1
3
2
EC2
EBS
Elastic IPWeb/App Servers
MySQL
Master
Manual scaling / Load Balancer
MySQL
Master
M
O
N
I
T
OR
S
Web/App Servers
D
Main Site Traditional DC in
USA east
Search Servers
Schedulers/BG
Search Servers
Schedulers/BG
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
36/48
Main website(MWS) hosted in USA east in
Traditional Data center
DR website(DRW) hosted in AWS USA west
region
Managed DNS passes the web requests to Main
website under normal circumstances
Load Balancer of Main site passes the request to
appropriate web/app servers
Blue Print 3 : Architecture Explanation
Continued
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
37/48
Web/App servers are configured with Manual
scaling in Main site
MySQL Data base servers are configured in
Master-Master replication mode
MySQL M-M replication inside Main site
(MWS)
MySQL M-M replication between Main and DR
site ( Asynchronous mode)
Blue Print 3 : Architecture Explanation
Continued
l i hi l i
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
38/48
MySQL servers are manually scaled in both sites
DR website (MWS) is monitored using AWS
CloudWatch
Main website will be monitored using
Traditional data center tools
Web/App servers in Main website runs on
minimal capacities
Blue Print 3 : Architecture Explanation
Continued
l i 3 hi l i
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
39/48
In event of failure , managed DNS will pass the
requests to DR website in USA West
DR website can take over the requests
seamlessly from the main website
DR website running in AWS UAS west can easily
scale its capacity depending upon the load
Blue Print 3 : Architecture Explanation
Bl P i 3 P i i
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
40/48
DR site can act immediately in event of Main site
failure Leverage the existing infra contracts with
Traditional data center provider
Cloud adoption and migration in phases (first DRsite followed by Main site)
Main Site handles predictable load and Elastic DR
site will act as Stop gap alternative during failures Partial dependency on AWS
Cost effective
Blue Print 3 : Positives
Bl P i 3 N i
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
41/48
Very complicated architecture for management
2 types of monitoring , provisioning, backup
,Security etc , In short 2 different infrastructure
architectures has to be maintained by the sys
admins
Can turn in to a maintenance nightmare if not
administered well
Cannot guarantee High availability
Cost ineffective on the Sys Administration front
Blue Print 3 : Negatives
Bl P i t 3 A hit t l Obj ti
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
42/48
Blue Print 3 : Architectural Objectives
Objectives Main site DR site
Elastic Load balancing X
Auto Scaling X
Failover
High Availability
Monitoring
Management
Replication inside a region
Replication across regions
Security Backups
Recovery
DR A hit t bl i t it bilit
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
43/48
Blue print1 :Both Main Site and Disaster recovery
site in AWS Cloud Suitable for web applications , Mobile apps , social and
gaming websites
Unpredictable load bursts , growing companies Blue print2 : Main site in AWS cloud and Disaster
recovery site in Traditional customer data center
Enterprises web applications, online Media companiesetc which already have 1-2 years contracts signed with
traditional data centers
Fairly predictable or On & Off workload bursts
DR Architecture blueprints suitability
DR A hit t bl i t it bilit
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
44/48
Blue print3 : Main site in customer data center and
Disaster recovery site in AWS cloud Suitable for applications with predictable loads
SMB companies which already have 1-2 years contracts
signed with traditional data centers
DR Architecture blueprints suitability
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
45/48
Which is the right Cloud based disasterrecovery strategy for me?
Leave it to the experts we will
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
46/48
Cloud Architecture Consulting
Cloud MigrationCloud Application Development
Leave it to the experts , we willsolve this
Cloud Implementation
Cloud Adoption Strategy
Let's get the job done
Why 8KMiles ?
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
47/48
Amazon Systems Integrator Migrated 350+ servers for start-ups, small businesses and
Enterprises
In-depth understanding of Cloud infrastructure services
Why 8KMiles ?
8/7/2019 Disaster Recovery using Amazon Web Services (AWS)
48/48
All you need is an idea and the cloud will execute it for you.(Structure 2010event)
- Dr Werner Vogels , CTO of Amazon on 8KMiles
For more details on how 8KMiles Cloud Consulting can help
your business , contact
http://cloudblog.8kmiles.com
http://cloud.8kmiles.com
http://www.livestream.com/gigaomtv/video?clipId=pla_0aa31b29-9dd0-44a9-9a13-f2958bb81cec&utm_source=lslibrary&utm_medium=ui-thumbhttp://www.livestream.com/gigaomtv/video?clipId=pla_0aa31b29-9dd0-44a9-9a13-f2958bb81cec&utm_source=lslibrary&utm_medium=ui-thumbTop Related