The business continuity aspects of cloud infrastructure

Welcome at “Business Continuity in the cloud era”

Sponsored by:

www.weolcan.eu . twitter.com/weolcan . Business Continuity in the Cloud Era 14-okt-16 2

About:

@BartMVeldhuis

[email protected]

blog.weolcan.eu

Bart M. Veldhuis• (Certified) Cloud Architect – Weolcan

• Founder Cloud Architect Alliance


Two sides of the story

Cloud as a solution for

Business Continuity

The Business Continuity

issues with cloud


IT INFRASTRUCTURE

WORKSPACEBUSINESS PROCESSES

Scope: IT infrastructure


Different types of events

SEVERITY OF DISASTER

Operational events Blue Moon events Epic events

Even

t ty

pe

Continuity by Design

Exit Strategy

Engineer for portabilityMeasu

res

misconfigurations

control plane failures

component failures

storms

power outages

natural disaster

commercial opportunity

failure to contract

bankruptcy


Continuity by designOperational events

Auto-scaling

BA

Multi-zone

loadbalancing

Self-healing

architecture


Setting up Auto scaling

Identify the

constraining

resources

Find a way to track

constraining resource

Configure alarms and

policies to trigger the

right scaling actions

1

2

3


Scalable Application Tiering

Web Tier Application Tier DB Tier

Current

Compute

Capacity

Capacity added

only when

needed

User



Auto-scaling

BA

Multi-zone

loadbalancing

Self-healing

architecture


Multi-zone loadbalancing

CloudWatch


High Availability across multiple zones



Auto-scaling

BA

Multi-zone

loadbalancing

Self-healing

architecture


Five layers of self-healing infrastructure

Network & datacenter

Virtual Machine & OS

Middleware

Application & data

consistency

Secu

rity

Changes (patches, application upgrades,

configuration changes etc.) are only made by

modifying a versioned service definition and

updating running services instances to the new

definition version.

Policy based

Continuous Delivery

Multi-zone Auto scaling

& load balancing

Automated Configuration

management

Automated Configuration

managementEvent Monitoring &

Reacting


Chaos Kong

Inspector monkey

Latency monkey

Janitor monkey

Conformity monkey

Chaos Gorilla

Chaos monkey

Doctor monkey


Chaos monkey

Can simulate:

• Instance failure

• CPU burn

• Null route (network loss)

• Network corruption

• Network latency

• Disk burn (fill the root partition)

• Detach disk


Backup and DR

scenarios

AA

Multi-region

loadbalancing

Continuity by designBlue Moon events


Multi-region loadbalancing


Backup and DR

scenarios

AA

Multi-zone

loadbalancing

Continuity by designBlue Moon events


It’s all about…RPO & RTO

02:00

Last backup

21:00

Service restored

RPO: 10 hours RTO: 9 hours

Disaster strikes!

12:00

RPO: Recovery Point Objective

RTO: Recovery Time Objective


Backup and DR scenarios for IaaS

1 Daily backup

BACKUP STANDBY

No standby

RPO/RTO

24h/96h

2

Frequent backups

(6x/day)

Reserved cloud

capacity04h/24h

3

Continuous Data

ProtectionCold standby 01h/04h

4

Active/Active

cloud designActive 0h/0h


Different types of events

SEVERITY OF DISASTER

Operational events Blue Moon events Epic events

Even

t ty

pe

Continuity by Design

Exit Strategy

Engineer for portabilityMeasu

res


What to do in case of an epic event?


Netflix goes down…


Exit Strategy and Engineer for portabilityEpic events

Achieve portabilityExit Strategy


IaaS: Zero RPO/RTO setup multi-cloud

Global

Load

Balancer

50%

50%App

OS

App

OS

App

OS

App

OS

Application Data

?

Zero downtime / Zero data loss


IaaS: Zero RPO/RTO setup: Data

• Database scale: if there are

only few joins in the queries,

try NOSql.

• Cache: do not touch database

if you can.

• Async: implement this where

possible.

App

OS

App

OS

App

OS

App

OS

DataApplication

M

S

Zero downtime / Zero data loss


IaaS: Zero RPO/RTO setup Multi cloud

Global

Load

Balancer

DNS

failover

App

OS

App

OS

ELB

ELB

Azure

EU-W

AWS

EU-C

DB

DB

DB

DB

Elastic

scaleFailover

replica

…

App

OS

App

OS

…

MongoDB

replica set

Read only

replica

(near) Zero downtime / Zero data loss


SaaS Exit Strategy

New contact


Exit Strategy and Engineer for portabilityEpic events

Achieve portabilityExit Strategy


Container portability


Container portability for developers


Container portability for IT Ops & BC


Achieve portability with a CMP


What’s on the agenda for tomorrow?

Key takeaway:

– Operational events and Blue Moon events require ‘continuity by design’

– Epic events require upfront planning and strategy

Tomorrow:

• Utilize container technology where possible to improve portability

• Use a multi cloud strategy to enable application mobility

• Read our research on cloud management portals

Internet

The business continuity aspects of cloud infrastructure