Hybrid DR in the Cloud - Harford SIM 2015

The Dream“Send it to the cloud!”• Recover to someone

else’s infrastructure• Only pay for what you

use, when you use it!

The Harsh Reality• Operational Impact

o Who will be providing the daily care and feeding of the DR solution?

• Consistencyo Configuration Drifto Does your IT staff need to now

make changes in 2 places for every move in production?

• Costso Is the solution a Ferrari? Ford?

Fiero?o What does it actually cost to

declare? Do you know?

The Challenge: Complexity

Lots of VMs… Lots of storage… Intricate WAN

topology…Physical appliances…Mainframes…Users need access to

input data…

Goals for this TalkLearn common BCP pitfallsStrategies to focus your continuity

planning Streamline your needs analysisMap tools and techniques to meet

those needs best

Why listen to me?• Solutions Architect at TierPoint• I design managed DR and IaaS solutions every

day• I talk to all walks of IT, across many verticals

o People who have implemented their own solutionso What’s working? What’s not?o Where’s the mind share?

Common Mistakes in Business Continuity

Planning

6 Common Blunders1. Picking a product or solution before defining

requirements fully2. Designing and pricing solutions before talking to

your internal stakeholders3. Designing for the “check-box” rather than

function4. Neglecting to test regularly5. Neglecting to test fail-back6. Settling for less because of past experiences

Boring….“I just spun up 10 AWS instances while you talked. I’m in the cloud already!”

• You feel like you’ve just made PROGRESS…

• …but how does it address your project’s Success Criteria?

Your DR/BCP Journey Starts Here

Solution Stage

Plan

Fundamental Drivers of IT BCP

Solution

RTOs &

RPOs

PeopleApps

Confer with Internal

Stakeholders

Needs Analysis Process

Conduct BIA

Define RTOs/RPOs

Establish Distance

Requirements

What’s the 1-3 Year IT Roadmap?

Your Needs

BIA Worksheet

Source

What are your priorities?

How up to date must the data be? (RPO) How quickly must it be made available? (RTO) Can employees/clients access the data? How near or far must this be from [critical site] ? What operational overhead does this create for my

team? How does the cost of DR align with changes to

production? Is it predictable? Can I live with a subset of production running at

declaration time? Does DR need to have full performance capabilities of

production?

Collect and Aggregate Your Data

Solution Stage

Plan Collect

Aggregate Your Data

System Inventor

yNetwork Diagram

Data Flow

Diagram

Network Utilizatio

nBackup Metrics

Key People

Mapping Needs To a Solution

Solution Stage

Plan Collect Map

Solution Approach1. Easy Wins – native replication or clustering2. RTOs & RPOs3. VMs – what can be protected as a portable unit?4. Physicals

1. Are any pending virtualization?2. Does it support recovering into a VM?3. Does it require a matching physical system?

5. Networking1. What carriers are required?2. What does the data change rate look like?

6. “Where are the eyeballs?”1. Is workspace needed to ensure consistent data flow?

7. Security 1. What frameworks must be adhered to?

RTO/RPO Technology Drivers

Configure hardware (p or v)

Install OS

Configure OS

Install backup agent

Start recovery

RestoreVM

Poweron VM

Backup & Recovery

24+ hr RTO; 24 hr RPO

< 1-4 hr RTO; ~0-15min RPOReplication

Load Balanced

High Availability ~0 hr RTO, ~0 hr RPO

Solution Map

DR Responsibility Matrix

Process Client ProviderDR Declaration PrimaryReplication Health PrimaryBackup Success PrimaryDR Testing Primary AssistDR Runbook Assist PrimaryDR Infrastructure Primary

Bringing it all together

Hybrid Cloud DRInfrastructure Continuity Approach

• Colocation• Cloud

o Privateo Public

• Managed Hosting• Workspace Recovery

• High-Availability• Replication

o VMo OSo SAN

• Backup and Recovery

Summary1.Focus first on your Applications

and People2.Derive RTOs and RPOs 3.Collect your data4.Map requirements to

infrastructure and technologies to best fit those individual needs

[email protected]

@joe_conlin