1.
Journey Through the Cloud
ianmas@amazon.com
@IanMmmm
Ian Massingham — Technical Evangelist
Disaster Recovery

2.
Journey Through the Cloud
Learn from the journeys taken by other AWS customers
Discover best practices that you can use to bootstrap your projects
Common use cases and adoption models for the AWS Cloud
1
2
3

3.
Disaster Recovery
Explore and learn about AWS with a ‘non-production’ use case
Phase systems into ‘live’ DR use with reduced risk
Benefit from lower costs & only pay for what you use
Gain the ability to test DR procedures more frequently
Invoke DR whilst testing DR procedures if necessary

4.
Agenda
Why AWS for disaster recovery?
AWS services that are relevant for DR use-cases
Common DR architectures
Customer case studies and examples
Resources to learn more

5.
Using AWS for DR Provision
https://aws.amazon.com/solutions/case-studies/sunpower/

6.
Business & Technical Drivers for DR in the Cloud
▶︎ Minimise costs
▶︎ Reduce on-premises infrastructure
▶︎ Consolidate sites
▶︎ Remove ageing technonologies

7.
DR & Business Continuity
DR forms part of a wider set of policies & controls
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

8.
I T ’ S N O T B I N A R Y

9.
DR & Business Continuity
Recovery Time Objective
(RTO)
Recovery Point Objective
(RPO)
How quickly I need this service to be recovered
1 minute? 15 minutes? 1 hour? 4 hours? 1 day?
How much data loss can be tolerated?
Zero data loss? 15 minutes out of date?
Each application or service will have specific requirements

10.
DR & Business Continuity
Customerfacing
transactionalwebapplication
Internalcollaborationsystem
Dailyscheduledprocesses
&systems
Backendreportingsystem
&
database
Applications can be placed on a spectrum of complexity…
Rebuild when required
from offsite backup
Run hot-hot configuration
with auto-failover

11.
The Utility, On-Demand Data Centre
Primary Site
Routers
Firewalls
Network
Application Licenses
Operating Systems
Hypervisor
Servers
SAN fabric
Primary Storage
Backup
Archive
Secondary Site
Routers
Firewalls
Network
Application Licenses
Operating Systems
Hypervisor
Servers
SAN fabric
Primary Storage
Backup
Archive

12.
The Utility, On-Demand Data Centre
Primary Site
Routers
Firewalls
Network
Application Licenses
Operating Systems
Hypervisor
Servers
SAN fabric
Primary Storage
Backup
Archive
AWS Region
Routers
Firewalls
Network
Application Licenses
Operating Systems
Hypervisor
Servers
SAN fabric
Snapshot Storage
Backup
Archive

13.
The Utility, On-Demand Data Centre
Primary Site
Routers
Firewalls
Network
Application Licenses
Operating Systems
Hypervisor
Servers
SAN fabric
Primary Storage
Backup
Archive
AWS Region
Routers
Firewalls
Network
Application Licenses
Operating Systems
Hypervisor
Servers
SAN fabric
Snapshot Storage
Backup
Archive
Secondary
site costs

14.
11 regions
28 availability zones
51 edge locations
AWS Global Footprint
https://aws.amazon.com/about-aws/global-infrastructure/

15.
AWS security
approach
Size of AWS
security team
Visibility into
usage & resources
Increasing your Security Posture in the Cloud
https://aws.amazon.com/security

16.
Broad Accreditations & Certifications
https://aws.amazon.com/compliance

17.
Partner ecosystem Customer ecosystem Everyone benefits
Security Benefits from Community Network Effect

18.
RELEVANT AWS SERVICES

19.
Object Storage & Transfer Services
Amazon S3 AWS Import/Export AWS Storage Gateway

20.
AWS Import/Export Disk
AWS Import/Export Disk
https://aws.amazon.com/importexport/disk/details/
Accelerates moving large amounts of data
Uses portable storage devices for transport
Often faster than internet transfer for large data sets
Supported regions:
US East (N. Virginia), US West (Oregon), US West
(Northern California), EU (Ireland), and Asia Pacific
(Singapore)

21.
AWS Import/Export Snowball
https://aws.amazon.com/importexport/
A single Snowball appliance can transport up to 50 terabytes of data

22.
Using AWS Storage Services for DR
Amazon S3 & Amazon Elastic Block Store
Simple Storage Service
Highly scalable object storage
1 byte to 5TB in size
99.999999999% durability
Elastic Block Store
High performance block storage device
Volumes from 1GB to 16TB in size
Snapshot/cloning functionalities

23.
Networking & Connectivity Services
AWS Direct Connect
Amazon Virtual
Private Cloud (VPC)
Amazon Route 53

24.
Connecting to AWS
VPN Connectio
VPN Connection
Amazon VPCYour premises/network
AWS Resources
VPC VPN
Gateway
VPN Connection
Customer
Gateway
Your Resources
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpn-connections.html

25.
Connecting to AWS
Direct Connect
Amazon VPCYour premises/network
AWS Resources
Direct Connect
Your Resources
https://aws.amazon.com/directconnect/

26.
Foundation Services
Amazon EC2
Amazon Relational
Database Service (RDS)
Amazon Elastic Block
Storage (EBS)

27.
COMMON ARCHITECTURES
FOR DISASTER RECOVERY

28.
Common Architectures for Disaster Recovery
4 Main Patterns
Backup & Restore Pilot light
Warm standby in AWS Multi-site solution
AWS & on-premises

29.
Common Architectures for Disaster Recovery
We’ll focus on two, starting with Backup & Restore
Backup & Restore Pilot light
Warm standby in AWS Multi-site solution
AWS & on-premises

30.
Store backup data in the AWS Cloud

31.
Store AMIs for server operating system images

32.
Recover servers during DR testing or invocation

33.
Backup & Restore Pattern
Advantages from starting here…
Simple to get started
Easy starting point for exploring the AWS cloud
Low technical barrier to entry
Focus on incorporating cloud into your DR
strategy, not on complex technical issues
related to hot-hot systems
Cost effective
Very high levels of data durability at low price
Cost of storing snapshots in S3
Archiving possibilities beyond tape using Glacier

34.
Backup & Restore Pattern
Getting started…
Take backups of
configuration
state & data
Store Backups
in Amazon S3
Move to long term
archive in Glacier

35.
Backup & Restore Pattern
Options…
Gateway Backup Appliance Direct Access to Amazon S3
AWS Storage
Gateway

36.
Amazon S3
Standard
Standard - Infrequent Access
Glacier
https://aws.amazon.com/s3/

37.
Amazon S3
Standard - Infrequent Access
https://aws.amazon.com/s3/storage-classes/

38.
Amazon Glacier
https://aws.amazon.com/glacier/

39.
Amazon Glacier
Durable
Designed for 99.999999999%
durability of archives
Cost Effective
Write-once, read-never. Cost effective for long
term storage. Pay for accessing data
https://aws.amazon.com/glacier/

40.
Logs
accessible from S3
logs
Expiry
time

41.
logs
✗
Objects expire
and are deleted
Logs
accessible from S3
Expiry
time

42.
Txns
Object transition to
Glacier invoked
Logs logs
✗
Objects expire
and are deleted
accessible from S3
accessible from S3
ExpiryTransition
time

43.
Restoration of object
requested for x hrs
Logs logs
✗
Objects expire
and are deleted
accessible from S3
accessible from S3
Txns
ExpiryTransition
Object transition to
Glacier invoked
time

44.
time
3-5hrs
Object held in S3
RRS for x hrs
ExpiryTransition
Logs logs
✗
Objects expire
and are deleted
accessible from S3
accessible from S3
Txns
Object transition to
Glacier invoked
Restoration of object
requested for x hrs

45.
Storage Gateway
Corporate Data Center Elastic Data
Center
AWS Storage
Gateway
AWS Storage
Gateway installed
on-premise to
synchronize local
volumes
https://aws.amazon.com/storagegateway/

46.
Storage Gateway
Corporate Data Center Elastic Data
Center
AWS Storage
Gateway
Local volumes
created under
Storage Gateway

47.
Storage Gateway
Corporate Data Center Elastic Data
Center
AWS Storage
Gateway
Usable with on-
premise servers
via iSCSI interface

48.
Storage Gateway
Corporate Data Center Elastic Data
Center
AWS Storage
Gateway
Primary on-
premise volumes
snapshotted,
compressed and
stored in Amazon
S3

49.
✕
Storage Gateway
Corporate Data Center Elastic Data
Center
AWS Storage
Gateway
✕

50.
Storage Gateway
Corporate Data Center Elastic Data
Center
AWS Storage
Gateway
Snapshot
pulled from S3
to restore local
volume

51.
Storage Gateway
Corporate Data Center Elastic Data
Center
AWS Storage
Gateway
Snapshot
pulled from S3
to create cloud
instance
backed by
Volume

52.
Gateway stored
volumes
Data stored locally
Asynchronous backup
EBS snapshots
iSCSI local interface
Up to 16TB volumes
Up to 12 volumes
Gateway cached
volumes
Data stored in S3
Recently read data cached
Low latency
iSCSI local interface
Up to 32TB volumes
Up to 32 volumes

53.
AWS Storage Gateway
Gateway-Virtual Tape Library (VTL)
http://docs.aws.amazon.com/storagegateway/latest/userguide/Requirements.html#requirements-backup-sw-for-vtl

54.
Storage appliances & backup management

55.
RDS & Oracle RMAN
https://d0.awsstatic.com/whitepapers/strategies-for-migrating-oracle-database-to-aws.pdf

56.
Common Architectures for Disaster Recovery
Next, let’s take a look at the Pilot Light pattern
Backup & Restore Pilot light
Warm standby in AWS Multi-site solution
AWS & on-premises

57.
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

58.
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

59.
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

60.
Stopped instances
Pilot Light

61.
Running instances
Pilot Light

62.
RESOURCES YOU CAN USE
TO LEARN MORE

63.
aws.amazon.com/disaster-recovery/

64.
AWS Disaster Recovery White Paper
Amazon Web Services – Using AWS for Disaster Recovery October2014
Page 1 of 22
Using Amazon Web Services for Disaster Recovery
October 2014
Glen Robinson, Attila Narin, and Chris Elleman
Amazon Web Services – Using AWS for Disaster Recovery October2014
Page 2 of 22
Contents
Introduction...............................................................................................................................................................3
Recovery Time Objective and Recovery Point Objective ................................................................................................4
Traditional DR Investment Practices ............................................................................................................................4
AWS Services and Features Essential for Disaster Recovery...........................................................................................5
Example Disaster Recovery Scenarioswith AWS...........................................................................................................9
Backup and Restore ................................................................................................................................................9
Pilot Light for Quick Recovery into AWS .................................................................................................................11
Warm Standby Solution in AWS.............................................................................................................................14
Multi-Site Solution Deployed on AWS and On-Site..................................................................................................16
AWS Production to an AWS DR Solution Using Multiple AWS Regions......................................................................18
Replication of Data...................................................................................................................................................18
Failing Back from a Disaster.......................................................................................................................................19
Improving Your DR Plan ............................................................................................................................................20
Software Licensing and DR........................................................................................................................................21
Conclusion ...............................................................................................................................................................21
Further Reading........................................................................................................................................................22
Document Revisions.................................................................................................................................................22
Amazon Web Services – Using AWS for Disaster Recovery October2014
Page 14 of 22
Warm Standby Solutionin AWS
The term warmstandby isusedtodescribe aDR scenario inwhicha scaled-downversionof afullyfunctional
environmentisalwaysrunninginthe cloud. A warmstandbysolutionextendsthe pilotlightelementsandpreparation.It
furtherdecreasesthe recoverytime because some servicesare alwaysrunning.Byidentifyingyourbusiness-critical
systems,you canfullyduplicate thesesystemsonAWSandhave themalwayson.
These serverscanbe runningon a minimum-sizedfleetof AmazonEC2instancesonthe smallestsizespossible.This
solutionisnotscaledtotake a full-productionload,butitisfullyfunctional.It canbe usedfornon-productionwork,
such as testing,qualityassurance,andinternal use.
In a disaster,the systemisscaledupquicklytohandle the productionload.InAWS,thiscanbe done by addingmore
instancestothe loadbalancerand by resizingthe small capacityserverstorunonlargerAmazonEC2 instance types.As
statedinthe precedingsection,horizontal scalingispreferredoververtical scaling.
Preparation phase
The followingfigure showsthe preparationphase forawarm standbysolution,inwhichanon-site solution andanAWS
solutionrunside-by-side.
Figure 6: ThePreparation Phaseofthe Warm Standby Scenario.
Amazon Web Services – Using AWS for Disaster Recovery October2014
Page 16 of 22
Multi-Site Solution Deployedon AWS and On-Site
A multi-site solutionrunsinAWSaswell ason your existingon-site infrastructure,inanactive-active configuration.The
data replicationmethodthatyouemploywill be determinedbythe recovery pointthatyouchoose. Formore
information aboutrecoverypointoptions,seethe RecoveryTime Objective andRecoveryPointObjectivesectioninthis
whitepaper.
In additiontorecoverypointoptions,thereare variousreplicationmethods, suchassynchronousandasynchronous
methods. Formore information,seethe Replicationof Datasectioninthiswhitepaper.
You can use a DNSservice thatsupportsweightedrouting,suchas AmazonRoute 53, to route productiontrafficto
differentsites thatdeliverthe same applicationorservice.A proportionof trafficwill gotoyour infrastructure inAWS,
and the remainderwill gotoyouron-site infrastructure.
In an on-site disastersituation,youcanadjustthe DNSweightingandsendall traffictothe AWS servers.The capacityof
the AWS service canbe rapidlyincreasedtohandle the full productionload. Youcanuse AmazonEC2 AutoScalingto
automate thisprocess.Youmightneedsome applicationlogictodetectthe failure of the primarydatabase servicesand
cut overto the parallel database servicesrunninginAWS.
The cost of thisscenarioisdeterminedbyhowmuchproductiontrafficishandledbyAWSduring normal operation.In
the recoveryphase,youpay only for whatyouuse forthe durationthat the DR environmentisrequiredatfull scale.You
can furtherreduce costby purchasing AmazonEC2 ReservedInstancesforyour“alwayson”AWSservers.
Preparation phase
The followingfigure showshow youcanuse the weightedroutingpolicy of the AmazonRoute 53 DNS to route a portion
of yourtrafficto the AWS site.The applicationonAWSmightaccessdata sourcesinthe on-site productionsystem.Data
isreplicatedormirroredto the AWSinfrastructure.
Figure 8: ThePreparation PhaseoftheMulti-SiteScenario.
http://media.amazonwebservices.com/AWS_Disaster_Recovery.pdf

65.
aws.amazon.com/vpc
aws.amazon.com/directconnect
aws.amazon.com/s3
aws.amazon.com/glacier
aws.amazon.com/storagegateway

66.
AWS re:Invent 2015 | (STG304) Deploying a Disaster Recovery Site on AWS
https://www.youtube.com/watch?v=bXrGUlgbl-s&list=PLhr1KZpdzukdTMmq1gkXs7g6WIIXtL5r9&index=15

67.
aws.amazon.com/architecture/

68.
Certification
aws.amazon.com/certification
Self-Paced Labs
aws.amazon.com/training/
self-paced-labs
Try products, gain new skills, and
get hands-on practice working
with AWS technologies
aws.amazon.com/training
Training
Validate your proven skills and
expertise with the AWS platform
Build technical expertise to
design and operate scalable,
efficient applications on AWS
AWS Training & Certification

69.
Follow
us
for m
ore
events
&
w
ebinars
@AWScloud for Global AWS News & Announcements
@AWS_UKI for local AWS events & news
@IanMmmm
Ian Massingham — Technical Evangelist