tierpoint_mitigate risk with hybrid cloud dr_oct2015

Mitigate Risk with Hybrid DRin the CloudJoe Conlin, Sr. Sales Engineer – October 28, 2015

Copyright© 2015 TierPoint, LLC. All rights reserved.

Troubling Statistics

2

68%of businesses that experience a

disaster and don’t have a DR plan areout of business within one year

60%of survey participants do not have a

fully documented DR plan

Disaster Recovery Preparedness Benchmark Survey, 2014

93%of business that lose their data centerfor 10 days or more due to a disasterfile for bankruptcy within one year

25%of survey participants lost most or all

of a datacenter for hours or days

Disaster Recovery Preparedness Benchmark Survey, 2014


97%

Outages ImpactMission-Critical Services

3

50%

7%

80%Caused by peopleand process issues

Caused by change /configuration /

release integration

Unplanned outagein past 24 months

Respond, recoverwithin 2 hours

Unplanned outages are the responsibility of IT toresolve; but they are essentially business issues

The cost of losing critical applications is more than$5,000 per minute; much higher for some industries


What Hybrid DR Looks Like

4

On-premise privateclouds federated

with public ordedicated cloud

providers

Hosted cloudenvironments, DR

seats

Interconnects to3rd party global

WAN networks viacross connect

Bridging x86 basedrecovery with

other “big iron”platforms

Hybrid DR


Risks Causing Move to Hybrid

5

Geography & weather

Security breaches, DDos and physical threats

Out-of-control capital expenses

Staffing concerns

Demand for fast recovery times


Hybrid DR Benefits

Hybrid DR in the Cloud

6

> Simplifies and speeds backup andrecovery

> Can keep you out of the data centerreal estate business

> Shifts costs from CapEx to OpEx forbetter corporate governance


Hybrid DR Benefits

About Recovery

7

> Portable workloads and automationmake process less complex, faster, morepredictable

> Recovery time and point objectives canbe dialed in based on available capacity

> Failback is the hidden side of DR - cloudsolutions offer consistent failover andfailback



8

CustomerLocation(ProtectedServers)

Windows or LinuxVirtual Machines

PhysicalWindowsServer

Protected Serversstored as a “DormantVMs”• System• Apps• Data

Server Replication

Recovered Windows and LinuxServers

MasterTarget VM

ATOT/D Failover• Promote VMDK

from MasterTarget• Create production

VMs



CustomerLocation(Protected Servers) Shared or Dedicated

Online Backup

Customer Data• VM Configuration• VMDKs (app image and

data)• ESX Configuration• Network Configuration

Vaulting

ATOT/D Failover• Provision servers and

apply VM profile• Hydrate data and

promote VMDKs toprovisioned servers

• Connect to customerSAN/NAS or otherhotsite servers, ifrequired

SAN/NASVTLRecovered Windowsand Linux Servers


Fundamental DR Plan Elements

10

DR Plan

RTOs&

RPOs

PeopleApps


Building a DR Plan

> Focus first on your Applications and People

> Derive RTOs and RPOs (via a business impact analysisor similar process)

> Collect your data (network maps, system inventories)

> Map requirements to infrastructure andtechnologies to best fit those individual needs

11


Case Study

> Ocean State Job Lot Regional retail chain, growing number of stores HQ located 1.25 miles from Narragansett Bay Weather is a key risk factor Did not want to build their own DC Wanted to focus staff on revenue-generating apps

> Results Hybrid cloud and colocation solution DR site located outside of flood risk zones Full case study at TierPoint.com (Resources > Library

> Case Studies)

12

tierpoint_mitigate risk with hybrid cloud dr_oct2015

Technology