Recovery As A Service:

Should you move your Disaster

Recovery to the cloud?

Steve Stavridis Product Marketing Manager - APACsteve.stavridis@netiq.comTwitter: @sstavridis

2

Agenda

1. Intro to Disaster Recovery (DR)2. Virtual Disaster Recovery3. Taking Disaster Recovery to the Cloud4. Recovery as a Service (RaaS) Options5. How NetIQ enables RaaS?

3

Introduction to Disaster Recovery

4

Definition: Server Workload

Server workload:

• the contents of a server, including the operating system, applications and data

5

What is Workload Protection?

Workload protection means:

1. Backup of entire server workloads,

2. Recovery of workloads to virtual machines during an outage, and

3. Restore of workloads to their original production locations after the outage.

6

Key Disaster Recovery Concepts

RPO: Recovery Point Objective

•A measure of maximum acceptable data loss in terms of time (minutes, hours, days).

RTO: Recovery Time Objective

•The target maximum allowable time to recover from an outage.

Availability tiers: 99.9%, 99.99%, Five 9’s, etc.

7

Key Disaster Recovery Concepts:

Availability Maximum Allowable Downtime per Year

Maximum Allowable Downtime per Month

Cost Products TypicalRPO/RTO

90% (“one nine”) 36.5 days 72 hours

95% 18.25 days 36 hours 12-24 hours

99% (“two nines”) 3.65 days 7.2 hours

99.5% 1.83 days 3.6 hours 15 minutes to4 hours

99.9% (“three nines”) 8.76 hours 43.2 minutes

99.99% (“four nines”) 52.56 minutes 4.32 minutes <5 minutes

99.999% (“five nines”) 5.26 minutes 25.9 seconds

??

Downtime and Availability

8

Traditional Disaster Recovery

Best Worst RPO/RTO

Cost

Offsite ReplicationExpensive; requires a secondary site, redundant hardware (which is idle / under-utilized most of the time)

Local ReplicationOnly good for individual server failure. No protection against site failures.

Vaulting (tape, imaging)Recovery can take days or weeks. Difficult to test.

$

$$$$

Virtual Disaster Recovery

9

The Benefits of Virtual Disaster

Recovery

10

Get Back to Business As Usual Faster

Recovery workload runs

on virtual infrastructure

Failback to dissimilar hardware

Failback with sync to repaired hardware

Internal web server

Repaired Email server

Virtual recovery(remote site)

New web server

11

Trust Your Plans

Rapidly test recovery

workloads

Testing logged for reporting

and compliance

Isolated testing of recovery workloads

Internal web server

Email server

Virtual recovery(remote site)

12

Maintain Control

Demonstrate policy

compliance

Actionable alerts

Failure notification

Internal web server

Email server

Virtual recovery(remote site)

Smart phone

13

Protect All Your Workloads

.Net Application server

LAMP server

Virtual recovery(remote site)

File-based replication

Block-based replication

Windows or Linux

Physical or Virtual

UniversalSolution

14

Taking Disaster Recovery to the

Cloud

15

Cloud-Based Disaster Recovery Delivery

Do-It-Yourself: Configure & manage your own solution using public cloud resources

Disaster Recovery-as-a-Service: Prepackaged pay-as-you-go recovery services to the cloud with specified RPO & RTO SLAs

Cloud-to-Cloud Disaster Recovery: Failover from one cloud environment to another

Source: Forrester (March 2012)

16

Storage as a Service

Fixed per-gigabyte cost

Off-site cloud-based storage

Scale up or down on demand

Service provider handles hardware maintenance, backups

Data only, not workloadsStatic storage can’t run

server workloads If a local outage occurs,

data needs to be copied to recovery environment first

Advantages

Disadvantages

17

Recovery as a Service (RaaS)

Fixed per-gigabyte costOff-site cloud-based

storageScale up or down on

demandService provider

handles hardware maintenance, backups

Protect whole workloads, not just data

Replicate to the cloud, recover and run in the cloud

Live restore back to repaired data center

Advantages

RaaS = Storage as a Service + IaaS

18

Cloud Based Workload RecoveryThe benefits of offsite disaster recovery

at a fraction of the priceOffsite Replication Cloud Recovery

Recovery Minutes-Hours Minutes-Hours

Cost High:• Disaster Recovery site

purchase / lease• Redundant hardware• Software licenses• Setup & monitoring

Fixed monthly price

Maintenance

Hardware upgrades, maintenance contracts

None (done on the MSP side)

Flexibility New workloads need to wait for hardware orders(or keep extra idle hardware)

Scale up or down on demand

19

RaaS vs. Traditional Disaster Recovery

Best Worst RPO/RTO

Cost

$

$$$$

Offsite Protection

Local Protection

Vaulting

RaaS

20

Recovery As A Service Options

21

Private/Hybrid RaaS

• Dedicated backup hardware at service provider premise

• Scale by adding hardware

• Hardware owned, managed, maintained by customer or service provider

• Replicate workloads directly to offsite facility

• Run recovery workloads in dedicated environment

22

Public RaaS

Shared backup hardware at service provider premise

Scale using service provider’s resource pool

Hardware owned, managed, maintained by service provider

Replicate workloads directly to offsite facility

Run recovery workloads in shared environment

23

Cloud-Based DR Resources & Service Providers

Amazon Web Services

Microsoft Windows Azure

Rackspace

Carpathia Hosting

Microsoft Windows Azure / Geminaire

RackSpace

CA

Vodacom

Bluefire

Hosting.com

Infoplex

Do-It-Yourself DR as a Service

24

How NetIQ enables RaaS?

25

Software based workload protection for Windows/Linux workloads

NetIQ PlateSpin Protect

Backup to virtual machines

Incrementalreplication

Easy to testOne-click

failover

Physicalservers

Virtualhosts

Bladeservers

Image archives

Workload decoupledfrom hardware

26

Protects up to 25 workloads

PlateSpin Forge includes:• Storage• Replication software• Hypervisor

Plug-in & protect solution for:

• Medium enterprises• Branch use for large enterprises

World’s first disaster recovery hardware appliance with virtualization

NetIQ PlateSpin ForgeAll in one Disaster Recovery appliance for

Windows/Linux workloads

27

Should you move your DR to the Cloud?Review your existing DR plan•How well does it map to the RTO/RPO requirements for servers/applications?

Rethink how you are doing DR today• A good starting place to consider RaaS:

• The “other” or 80% category (under-insured servers)

•Start small with RaaS• Choose a few servers and test to see if it makes sense

Building DR as a service offerings?•NetIQ can help

Visit our booth

28

Thank You!

Check out our FREE eBook:5 Things You Need to Know Today About

Disaster Recovery Planning

http://bit.ly/5DRSecrets