1

DISASTER RECOVERY: ONE SIZE DOES NOT FIT

ALL

• This webinar is being recorded and an on-demand version will be available at the same URL at the conclusion of the webinar

• Please submit questions via the button on the upper left of the viewer• If we don’t get to your question during the

webinar, we will follow up with you via email• Download related resources via the

“Attachments” button above the viewing panel• On Twitter? Join the conversation: #DR,

#DisasterRecovery, @HOSTINGdotcom

2

HOUSEKEEPING

3

• Why are we here?• To understand how the cloud has

fundamentally changed DR• To discuss common approaches to DR in

the cloud• To learn about the use-cases that are

the best fit for each

WELCOME!

4

• Who is this guy anyway?• Darrell Hyde – CTO, HOSTING• 18-year veteran of the managed hosting

industry• Survivor of many disasters• Learner of many lessons• Passionate believer in continuous

testing

WELCOME!

5

MY FIRST DISASTER

• September 1999, Hurricane Floyd• Category 4 storm• Winds up to 155

mph• $4.5B in damages• 57 deaths• 2.6 million

displaced

6

• Working for a local ISP in Delaware• Office and colo facility located next to

a river known to flood• No backup power• Customer servers located on the first

floor• Telco demarc in an old shed behind

the building

MY FIRST DISASTER

7

• Guess what happened next…• Building flooded• Power lost• Servers under water• Telco demarc fried• Techs scrambling in the dark to move

equipment upstairs

MY FIRST DISASTER

8

• What did I learn from this experience?• Location, location, location• It’s not if, it’s when• Only as strong as your weakest link• If it happened once, count on it

happening again

MY FIRST DISASTER

9

MY FIRST DISASTER

10

WHY DO BAD THINGS HAPPEN TO GOOD APPLICATIONS?

• Top 5 risks to application availability*:• Human Error• Network Failure• Cloud Provider Downtime• External Threats• Application Scalability Limitations

TOP RISKS TO AVAILABILITY

* 2015 Public Cloud Disaster Recovery Survey

SOME SCARY FACTS

Disaster Recovery Journal

80% Of U.S. Companies

Lack a DR plan

50% Of SMBs Worldwide

Have no Recovery PlanSymantec 2011 SMB Disaster Preparedness Survey

Global 72% Of SMBs WorldwideWith a Plan Have Never Tested It

Symantec 2011 SMB Disaster Preparedness Survey Global

PRACTICE MAKES PERFECT

40% Fear Disruption

To CustomersSymantec 2009 Disaster Recovery Survey 27% Fear

Disruption

To Sales and RevenueSymantec 2009 Disaster Recovery Survey

48% Lack The Resources

To Test RegularlySymantec 2009 Disaster Recovery Survey

14

• DR testing should not…• Negatively impact customers• Negatively impact employees• Negatively impact revenue• Be an excuse to drink with your

coworkers on the weekend

THERE HAS TO BE A BETTER WAY

15

MODERN APPROACHES TO DR

16

• Hypervisor-based replication (HBR)

• App-native replication• Active / active application

architecture

MODERN APPROACHES TO DR

17

• Stands for Hypervisor-Based Replication• Gained mass popularity over last 5 years• Alternative to EMC RecoverPoint et al.• Popular implementations:• VMware Site Recovery Manager (SRM)• Zerto• PHD Virtual (acquired by Unitrends, 2013)

• Not a fit for all workloads

HBR IN A NUTSHELL

18

• Pros:• Hardware, storage, and OS-agnostic• Centralized management• RPO-adherence monitoring

• Cons:• Application unaware• Unable to replicate non-local storage

HBR IN A NUTSHELL

19

• App-Native Replication• SQL server

• Clustering• Log shipping• AlwaysOn

• MySQL• Master / slave replication• Native clustering (NDB)• DRBD• Continuent

HBR ALTERNATIVES

20

• App-Native Replication• Pros:• Guarantees application consistent data at

time of disaster• Aggressive RPO

• Cons:• Requires active infrastructure at recovery

site• Centralized management varies

HBR ALTERNATIVES

21

• Storage Replication• NetApp SnapMirror• Nimble Data Protection• EMC VNX Replicator

HBR ALTERNATIVES

22

• Storage Replication• Pros:

• Can be either app-aware or agnostic• Management centralized and abstracted• Often includes encryption and WAN optimization

• Cons:• Often a paid license (newer vendors trending

away from this• Requires large capex investment and live

infrastructure at recovery site

HBR ALTERNATIVES

23

• Active / Active Deployment• Leverage GSLB (DNS-based multisite

load balancing) or IP anycast• Application served from multiple

locations / regions / clouds• Typically requires low-latency

interconnect for replication

HBR ALTERNATIVES

24

• Active / Active Deployment• Pros:

• Complete protection from localized outages• Ability to protect from vendor lock-in by leveraging

multiple providers• Ability to place content geographically “closer” to regional

consumers• Cons:

• Very complex; requires fine grained understanding of dependencies and failure cases

• Can lead to excess infrastructure costs to support production scale in each location

HBR ALTERNATIVES

25

• DR plans should be tested regularly• Not all workloads are a fit for HBR• Native-app replication can be more

predictable, but may complicate management

• Let the business requirements drive the technology, not the other way around

• One size does not fit all

WHAT DID WE LEARN?

26

Q&ADarrell Hyde | CTO | @darrellhyde

For more information about HOSTING Disaster Recovery Planning™, please contact HOSTING at 888.894.4678.