1 of 33

DRaaS

Disaster Recovery as a Service�APEX Backup Services

Daniel.Olkowski@dell.com

1

Internal Use - Confidential

2 of 33

Agenda

What is Disaster Recovery as Service?
Architecture
Cost

2

Internal Use - Confidential

3 of 33

What is Disaster Recovery as a Service??

DISASTER RECOVERY AS A SERVICE – APEX BACKUP

3

Internal Use - Confidential

4 of 33

Use Cases

Disaster Recovery as a Service

Disaster Recovery as a Service

Starting on premise environment in cloud in minutes
Failback

Tests
Development
Migrating data
Starting additional resources in Cloud in case of high demands for services

Above are ideal cloud use cases

Incidental usage

4

Internal Use - Confidential

5 of 33

What can we do?

Disaster Recovery as a Service

We can on demand

Recover
Start

VMware Virtual Machines that we have backed up in APEX Backup Services

No need for our own

Hardware
Software

No need for hardware / software installation / setup / configuration

5

Internal Use - Confidential

6 of 33

Why does it make sense?

Disaster Recovery as a Service

Probability of Primary Site exists and is real
Anyhow it is small
Investing in Capex does not make sense

Buildings
Infrastructure – network / cooling / physical security
Hardware
Software

to use it occasionally

APEX Backup Services provides with single small cost

Backup
Disaster Recovery as a Service

6

Internal Use - Confidential

7 of 33

Why does it make sense?

Disaster Recovery as a Service

We can be as far as we want from our Primary Site

US East (N. Virginia)

US West (N. California)

US West (Oregon)

Asia Pacific (Mumbai)

Asia Pacific (Singapore)

Asia Pacific (Sydney)

Asia Pacific (Tokyo)

Canada (Central)

Europe (Frankfurt)

Europe (Ireland)

Europe (London)

Europe (Paris)

South America (Sao Paulo)

AWS GovCloud (US-West)

7

Internal Use - Confidential

8 of 33

Preconfigure failover settings

Disaster Recovery as a Service

VPC
Subnet
Security groups
IP assignment

Failover is:

Simple
One click

8

Internal Use - Confidential

9 of 33

Architecture

DISASTER RECOVERY AS A SERVICE – APEX BACKUP

9

Internal Use - Confidential

10 of 33

Architecture overview

10

of 20

Internal Use - Confidential

11 of 33

Architecture overview

11

of 20

Internal Use - Confidential

12 of 33

Architecture overview

12

of 20

Internal Use - Confidential

13 of 33

Architecture

Disaster Recovery as a Service

We have frequent backups of APEX Backup Services Hybrid
They are already in AWS
We need also in AWS

DRaaS Proxy
S3 storage for latest backup copy (snapshot)

13

Internal Use - Confidential

14 of 33

Architecture overview

We have latest backups of all VMs on S3 storage for DRaaS purposes.

For every VM that we want to have DRaaS:

Latest backup of VM is copied to EBS (Block Storage) to decrypt it

Than VM is copied to S3 to keep it on as cheap Storage as possible

EBS Volume is deleted as it was temp storage only

14

of 20

Internal Use - Confidential

15 of 33

Architecture overview

We have latest backups of all VMs on S3 storage for DRaaS purposes.

This is performed constantly on latest copies for VMs included in DRaaS

15

of 20

Internal Use - Confidential

16 of 33

Architecture overview

The process is controlled by APEX Backup Services proxy

16

of 20

Internal Use - Confidential

17 of 33

Architecture overview

We can define how often we want to have fresh Disaster Recovery copy in AWS environment – how often DRaaS shall grab backup copy and move it to S3 in executable environment

This depends on our RPO.

17

of 20

Internal Use - Confidential

18 of 33

Failover

DISASTER RECOVERY AS A SERVICE – APEX BACKUP

18

Internal Use - Confidential

19 of 33

Admin starts DR from APEX Backup Services console

Automatically AWS Proxy initiates failover

19

of 20

Internal Use - Confidential

20 of 33

S3 snapshot is copied to EBS (Block) volume for every VM in DRaaS plan

20

of 20

Internal Use - Confidential

21 of 33

VM is configured, attached to EBS volume and started

This is for every every VM in DRaaS plan

21

of 20

Internal Use - Confidential

22 of 33

Redirect DNS service to new VMs

22

of 20

Internal Use - Confidential

23 of 33

Orchestration

Failover

Sequence of booting VMs fo fail-over

Web server after databases

Dependencies between EC2s
Own scripts to regulates EC2 boots
We can perform tests in different VPC / subnets

EC2 – Virtual Machine in AWS

23

Internal Use - Confidential

24 of 33

Failback

DISASTER RECOVERY AS A SERVICE – APEX BACKUP

24

Internal Use - Confidential

25 of 33

25

of 20

Internal Use - Confidential

26 of 33

Cost

DISASTER RECOVERY AS A SERVICE – APEX BACKUP

26

Internal Use - Confidential

27 of 33

Cost structure - Traditional Disaster Recovery as a Service

27

of 20

Internal Use - Confidential

28 of 33

Cost structure - Disaster Recovery as a Service

28

of 20

Internal Use - Confidential

29 of 33

Cost structure

Disaster Recovery as a Service

No upfront expenses

We will pay for our infrastructure only when we start our environment in the Cloud

We do not pay for

Hardware / Software
Electricity / Space / Connectivity / Maintenance

Pay as you go monthly fees

VM / Storage of the service

29

Internal Use - Confidential

30 of 33

Cost structure

Disaster Recovery as a Service

VPN connection

May be needed

If VPN is needed

Only used in case we start the enviornment in Cloud
Only than we pay for consumption
AWS requires $36 / month as maintennace cost for the tunnel

Gateway in AWS is free
Connectivity cost is marginal

30

Internal Use - Confidential

31 of 33

Cost structure

Disaster Recovery as a Service

AWS Proxy

Component of DRaaS of APEX Backup Services
Required to manage DRaaS service
One or more required

We need to pay for this VM

Compute
Storage (minimal)

31

Internal Use - Confidential

32 of 33

Cost structure

Disaster Recovery as a Service

S3 Storage with latest backups (snapshots) of our production

32

Internal Use - Confidential

33 of 33

End logo slide

Questions

Daniel.Olkowski@dell.com

33

Internal Use - Confidential