Docker taylor swift and protection v06

CONFIDENTIAL | ©2015 Unitrends | www.unitrends.com

Docker, Taylor Swift, and

Protection

Dr. Mark Campbell | [email protected] | @DrMarkCampbell

CTO and CMO, Unitrends

2

Things We’ll Talk About Today

Taylor Swift?

What is a Container?

What is a Docker Container?

Containers vs Hypervisors

Docker vs Containers vs Hypervisors

Protecting Docker Containers

> Hypervisor-Level Protection (Shallow Virtualization)

> Deep Virtualization

> Shallow and Deep Virtualization Together

> How Are Containers Different in Terms of Protection?

> Docker Container Image Protection

> Docker Container Volume Protection

> What Does Unitrends Offer for Docker Now…and Later?

Who We Are

3

What does Taylor Swift have to do

with Docker? Awareness

4

Look at the ramp of Docker versus

VMware ESX and Hyper-V

5

By the way…Taylor Swift versus any

form of virtualization isn’t really close

6

What Is a Container?

Containers are operating system

virtualization technology

Container key benefit is increasing

virtualized instance density

Containers date back to 2000

Notable implementations

> FreeBSD Jails

> Solaris Zones

> OpenVZ and LXC (Linux

Containers)

> Google lmctfy (Let Me Contain

That For You)

7

What Is a Docker Container?

Docker is built upon LXC (Linux

Containers)

Docker core benefit is application

portability

> This is achieved via libcontainer

Docker’s libcontainer appears to be

becoming a de facto standard

Docker’s genius is its ecosystem

8

Containers vs Hypervisors

App App

Bins/Libs

Operating

System

Virtual Machine

Type 2 Hypervisor

Operating System

Hardware

App App

Bins/Libs

Operating

System

Virtual Machine

Type 1 Hypervisor

Hardware

App App

Bins/Libs

Container

Hardware

Operating System

App App

Bins/Libs

Container

Hardware

Operating System

9

Docker vs Containers vs Hypervisors

App App

Bins/Libs

Operating

System

Virtual Machine

Type 2 Hypervisor

Operating System

Hardware

App App

Bins/Libs

Operating

System

Virtual Machine

Type 1 Hypervisor

Hardware

App App

Bins/Libs

Container

Hardware

Operating System

App App

Bins/Libs

Container

Hardware

Operating System

Docker

10

Protecting Docker Containers

Shallow Virtualization: Hypervisor-Level Protection

Deep Virtualization

Container Differences

Docker Image Protection

Docker Volume Protection

11

Shallow Virtualization: Hypervisor-Level Protection

App App

Bins/Libs

Operating

System

Virtual Machine

Type 1 Hypervisor

Hardware

App App

Bins/Libs

Operating

System

Virtual Machine

Shallow Simple Process

1. Get list of all VMs

2. Choose VMs to protect

3. Do a master/full on each

4. Periodically copy all

changed blocks of each

Application, data volume,

and operating system data

is included

12

Deep Virtualization

App App

Bins/Libs

Operating

System

Virtual Machine

Type 2 Hypervisor

Operating System

Hardware

App App

Bins/Libs

Operating

System

Virtual Machine

Type 1 Hypervisor

Hardware

Deep Simple Process

1. Protect applications and

operating systems data

granularly

Specific context-aware data

is included

Shallow Simple Process

1. Get list of all VMs

2. Choose VMs to protect

3. Do a master/full on each

4. Periodically copy all

changed blocks of each

Application, data volume,

and operating system data

is included

13

Shallow and Deep Virtualization Together

14

Container Differences

Containers consist of an

image and optional data

volumes

An image may contain OS

and application components

A container may be a “data

container” (no compute)

A container may use

volumes from another

container

App

Image 1

Volume

1

Operating System

Hardware

App

Image 2

App

Image 3

Volume

2

Volume

2

Container

1

Container

2

Container

3

15

Container Differences (continued)

Application images are

published to repositories; don’t

change frequently

> Public repositories (e.g.,

Docker Hub Registry)

> Private repositories

Production containers must use

data volumes to persist storage

Data volumes are logically

accessed as volume paths

App

Image 1

Volume

1

Operating System

Hardware

App

Image 2

App

Image 3

Volume

2

Volume

2

Container

1

Container

2

Container

3

App

Image 1App

Image 2

App

Image 3

Image Repository

Image Repository Pull

16

Docker Image Protection

Why should you protect Docker

images despite the fact that they

infrequently change?

> You want to protect your

repository

> You want retention history of

your repository

> Repository pulls aren’t

accessible locally

> Repository pulls don’t meet

your RTO (Recovery Time

Objective)

App

Image 1

Volume

1

Operating System

Hardware

App

Image 2

App

Image 3

Volume

2

Volume

2

Container

1

Container

2

Container

3

App

Image 1App

Image 2

App

Image 3

Image Repository

Image Repository Pull

17

Docker Volume Protection

Why should you protect Docker

volumes?

> Because it’s your data

How should Docker volumes be

protected?

> Independently of images for

storage efficacy+ But still need metadata to restore to

images

> Full and incremental backups

> Using compression and

deduplication

> With ability to archive

> With ability to replicate

App

Image 1

Volume

1

Operating System

Hardware

App

Image 2

App

Image 3

Volume

2

Volume

2

Container

1

Container

2

Container

3

App

Image 1App

Image 2

App

Image 3

Image Repository

Image Repository Pull

18

What Does Unitrends Offer for Docker Now…and Later?

Today

> Unitrends offers image-level

protection through KB 1884

> Unitrends offers in-container

protection

Later this year

> Unitrends will offer volume-

level protection

> Unitrends will offer several

other features we can discuss

under NDA

App

Image 1

Volume

1

Operating System

Hardware

App

Image 2

App

Image 3

Volume

2

Volume

2

Container

1

Container

2

Container

3

App

Image 1App

Image 2

App

Image 3

Image Repository

Image Repository Pull

19

Who We Are

20

Unitrends provides radically simple cloud-

empowered all-in-one continuity solutions

that increase IT confidence

21

+1EB Customer data

currently protected

Exabyte

22

About Unitrends

Worldwide

headquarters in

Boston

European

headquarters in

London

400 employees in 6

locations: Boston,

Columbia SC, London,

Madrid, Philadelphia

and Sydney

>13,000 customers

>8,000 registered

partner affiliates

23

Recovery: The Problem

24

Solution Portfolio

Unitrends BoomerangVMware and AWS cloudbursting, migration, and DRaaS

Unitrends Recovery-SeriesCloud-empowered 1TB-100TB hyperconverged heterogeneous

physical backup appliances

Unitrends Enterprise BackupCloud-empowered VMware and Hyper-V hyperconverged

heterogeneous virtual backup appliance

Unitrends CloudMulti-tenant public hybrid cloud supporting heterogeneous storage

and DRaaS of VMware, Hyper-V, and Windows

Unitrends ReliableDRUnified application-level recovery-assurance for VMware and Hyper-V;

integrated in Unitrends Cloud, Recovery-Series, and Enterprise Backup

25

The future of the backup appliance is convergence

26

Awards

Unitrends #1 mid-market PBBA

Unitrends had 10 of top 20 PBBAs

Unitrends #1 virtual software

Beat CommVault and Veeam

Unitrends first year placement in MQ;

Should accelerate right and higher in 2015

27

Try Us Out

Get a Free Trial of Our Virtual Appliance

http://www.unitrends.com/products/download/ueb

Or, if you like to get physical, try an Eval Unit

http://www.unitrends.com/resources/request-evaluation-unit

www.unitrends.com

THANK YOU

CONFIDENTIAL

28

Mark Campbell | [email protected] | @DrMarkCampbell