how to use aws for disaster recovery and close your dr datacenter
TRANSCRIPT
How to Use AWS for Disaster Recovery and Close your DR Datacenter
March 29, 2017
2
Housekeeping
Post your questions here
This session IS being recordedLinks to the recording and presentations will be provided later
To listen using your telephone select the ‘Telephone’ option.
For local numbers click the ‘additional numbers’ link.
You will need to use the Access Code and Audio PIN.
The audio for this webinar is available over VoIP. Just select
the use ‘Mic & Speakers’ option to listen to the webinar
through your computers speakers.
If you CAN NOT hear us, please check your
volume settings.
Webinar Audio1
2
3© 2017 SoftNAS, Inc.
3
Agenda• AWS DR Overview and Benefits• Demo: Build a Hot Standby DR
Environment on AWS• DR Architectures• High-availability on AWS• Q&A
© 2017 SoftNAS, Inc.
AWS DR Overview and Benefits
© 2017 SoftNAS, Inc.
Terminology Business Continuity
Business Continuity ensures an organization's critical business functions continue to operate or recover quickly despite serious incidents.
Disaster RecoveryDisaster Recovery (DR) enables the recovery or continuation of vital technology infrastructure and systems following a natural or human- induced disaster.
Recovery Point Objective Recovery Time ObjectiveRTO is a targeted duration of which a business process must be restored after a disaster or disruption.
RPO is the maximum targeted period in which data might be lost from an IT service due to a major incident.
Keep your Primary Datacenter, but Shift DR to AWS
Primary Datacenter DR Datacenter
Traditional DR
Replication
Main Datacenter
AWS DR
ReplicationAmazon
S3
Import/Export
Amazon EC2
AmazonRoute 53
SoftNAS Cloud
UsersUsers
+ Additional services
DR Datacenter vs. AWS
On-Premises• High cost to build disaster recovery
sites or datacenters (CapEx)• High cost of storage, backup,
archival and retrieval tools, and processes (OpEx)
• Difficult planning, procurement and deployment
• Challenging to verify DR plans• Single level of DR across the
organization
AWS– Low cost upfront investment
(CapEx)– On- demand costs (OpEx)– Consistent experience across AWS
environments– Recovery automation– Separate levels of DR per
application or business unit
Cloud Disaster Recovery• Automated protection and replication of virtual
machines• Remote health monitoring• Customizable recovery plans• No-impact recovery plan testing• Orchestrated recovery when needed• Replication to – and recovery in – AWS
© 2017 SoftNAS, Inc.
DR DatacenterRouters
Firewalls Network
Application Licenses Operating Systems
HypervisorServers
SAN fabricPrimary Storage
Backup Archive
AWSRouters Firewalls Network
Application Licenses
Operating Systems
HypervisorServers
SAN fabricSnapshot Storage
Backup Archive
DR Infrastructure Management
What You
Manage with a
DR Datacenter
What You Manage with
AWS DR
DR Services Mapping
Your Datacenter
Route 53
ELB/Appliance
EC2/Auto
scaling DB
failover nodes
AD failover
nodes
Availability
zones Multi-
region
Disaster Recovery
Data Centers
DNS
Load Balancers
Web/App
Servers
Database
Servers
AD/Authenticati
on
AWS Enterprise Security Standards
© 2017 SoftNAS, Inc.
CertificationsSOC 2
ISO 27001PCI DSS for EC2, S3, EBS, VPC, RDS, ELB,
IAMFISMA Moderate
compliant controlsHIPAA & ITAR
compliant architecture
Physical SecurityDatacenters in
nondescript facilitiesPhysical access
strictly controlledMust pass two-factor authentication at least twice for floor accessPhysical access logged
and audited
HW, SW, NetworkSystematic
change management
Phased updates deployment Safe
storage decommissionAutomated monitoring
and self-auditAdvanced network
protection
DR Architectures
DR Architectures
Backup & Restore
Pilot Light
Hot Standby
Multi- Site
Backup of on- premises data to AWS to use in a DR event
Replicate data and minimal running services into AWS, ready to take over and flare up
Replicate data and services into AWS ready to take over
Replicated and load balancedenvironments that are both activelytaking production traffic
RPO
COST
24 hours
RTO24
hours
$
RPO
RTO
COST
12 hours
4 hours
$$
RPO
COST
1- 4 hours
RTO15
min
$$$
RPO
RTO
COST
<15 min
0- 5 min
$$$$
Business continuitybegins
Un- interrupted Business
continuity
Backup & Restore
Pilot Light
Hot Standby
Multi- Site
S3SoftNAS Cloud
Glacier
EBSVolume
s
Route 53
Direct Connect
VPN
Netw
orki
ng
Stor
age
Multiple Direct Connects
Com
put
e Auto Scaling
ELBEC2
Depl
oym
ent /
M
anag
eme
nt CloudFormation
IAM
Added through the levels of DR
VPC
Backup & Restore Architecture
SoftNAS Cloud
Backup & Restore – How it WorksAdvantages
• Simple to get started• Cost effective (mostly backup
storage)Preparation Phase
• Start SoftNAS Cloud 30 day free trial
• Install and configure SoftNAS Cloud• Describe procedure to restore from
backup on AWS• Know which AMI to use, build
your own as needed• Know how to switch to new
system• Know how to configure the
deployment
In Case of Disaster• Retrieve backups from S3• Bring up required infrastructure
• EC2 instances with prepared AMIs, Load Balancing, etc.
• Restore system from backup• Switch over to the new system
• Adjust DNS records to point to AWS
Objectives• RTO: as long as it takes to bring up
infrastructure and restore system from backups
• RPO: time since last backup
Pilot Light Architecture
Data Replication
ELB
On-premises Active
Production Route 53
Corporate data center
1 TB DataVolume
Web Servers
AWS region
Web Servers
AWSActive
Production
Direct Connect
App Servers
DBServer
App Servers
DBServer 1TB
Data Volume
EC2 (m3.xlarge)$205/Month
EBS (GP2)$100/Month
EC2 (t2.medium)$0/Month
ELB (100GB Data)$0/Month
EC2 (t2.small)$0/Month
ELB (100GB Data)$0/Month
CloudFormation
Pilot Light – How it WorksAdvantages
• Very cost effective (fewer 24/7 resources)
Preparation Phase• Enable replication of all critical
data to AWS• Prepare all required resources for
automatic start• AMIs, Network Settings, Load
Balancing, etc.• Reserved Instances
In Case of Disaster• Automatically bring up resources
around the replicated core data set• Scale the system as needed to
handle current production traffic• Switch over to the new system
• Adjust DNS records to point to AWS
Objectives• RTO: around 4hours• RPO: around 12 hours
Hot Standby Architecture
ELB
On-premises Active
Production Route 53
Corporate data center
1 TB DataVolume
Web Servers
AWS region
Web Servers
AWSActive
Production
App Servers
DBServer
App Servers
DBServer 1TB
Data Volume
EC2 (m3.xlarge)$205/Month
EBS (GP2)$100/Month
EC2 (t2.medium)$41/Month
ELB (100GB Data)$19/Month
EC2 (t2.small)$22/Month
ELB (100GB Data)$19/Month
R53 (1M Query)$4/Month
CloudFormation
Data Replication
Direct Connect
Hot Standby – How it WorksAdvantages
• Handles production workloads well
Preparation Phase• Enable replication of all critical
data to AWS• Prepare all required resources
for automatic start• AMIs, Network Settings,
Load Balancing, etc.• Reserved Instances
In Case of Disaster• Automatically bring up resources
around the replicated core data set• Scale the system as needed to
handle current production traffic• Switch over to the new system
• Adjust DNS records to point to AWS
Objectives• RTO: around 15 minutes• RPO: around 1-4 hours
Multi- site Architecture
Data Replication
ELB
On-premises Active
Production Route 53
Corporate data center
1 TB DataVolume
Web Servers
AWS region
Web Servers
AWSActive
Production
Direct Connect
App Servers
DBServer
App Servers
DBServer 1TB
Data Volume
EC2 (m3.xlarge)$205/Month
EBS (GP2)$100/Month
EC2 (t2.medium)$82/Month
ELB (100GB Data)$19/Month
EC2 (t2.small)$44/Month
ELB (100GB Data)$19/Month
R53 (1M Query)$4/Month
CloudFormation
Multi-site – How it Works– Advantages
• At any moment can take all production load– Preparation
• Fully scaling in/out with production load– In Case of Disaster
• Immediately fail over all production load• Adjust DNS records to point to AWS
– Objectives• RTO: minutes• RPO: minutes
Customer DR ExampleCustomer has a combination of Tier 1, Tier 2, and Tier 3 business applications. They did the following:
Tier 1 AppsRPO & RTO <15 minutes
Multi-site DR
• Critical core elements of system already configured
• EC2 instances running for critical services
• Pre-configured AMIs for Tier-2 apps that can be quickly provisioned upon failure
• Cloud infrastructure load-balanced and configured for automatic failover
• Initial data synchronization using in-house backup software or FTP
• Incremental data replicated / synchronized using cloud NAS
Tier 2 AppsRPO & RTO <4 hours
Pilot Light DR
• EC2 instances for all services running at all times
• In-house and cloud infrastructure load-balanced and configured for auto-failover
• Initial data synchronization using in-house backup software or FTP
• Incremental data replicated / synchronized using cloud NAS
• All data replicated into S3 bucket
• Initial data synchronization using in house backup software or FTP
• Pre-configured AMIs for Tier 1 and Tier 2 apps quickly provisioned upon failure
• Incremental data replicated / synchronized using cloud NAS
• EC2 instances spun-up from objects within S3 buckets
Tier 3 AppsRPO & RTO <8 hours
Backup & Restore
© 2017 SoftNAS, Inc. 24
High-Availability Architecture• SNAP™ HA
– Provides high availability seamless failover across zones– Leverages secure block replication with SoftNAS SnapReplicate
• Recommended: SNAP HA in high-availability mode = 99.999% uptime
© 2017 SoftNAS, Inc. 25
Cross-Zone HA: AWS Elastic IP
© 2017 SoftNAS, Inc. 26
Cross-Zone HA: Private Virtual IP Addresses
Brands You Know Trust SoftNAS
Earn $100 AWS Credit!
First 100 attendees to register
ter.li/zt5un2
© 2017 SoftNAS, Inc.
Try SoftNAS Cloud® Free for 30 Days on AWS
29
Learn More softnas.com/aws
Free Trial (30 Days)softnas.com/tryaws
Contact Us softnas.com/contact
Supportsoftnas.com/helpdesk
softnas.com/tryaws© 2017 SoftNAS, Inc.