Robust BC/DR No Hypervisor Dependencies

Phil Goodwin, Research Director, Storage Systems and Software

Jennifer Gill, Director, Global Product Marketing

Robust BC/DR – No Hypervisor

Dependencies

•

Speaker Introductions

•

Using hybrid cloud to (finally!) create a BC/DR strategy

–

Infrastructure Landscape

–

Traditional DR

–

XaaS and Hybrid Cloud Challenges

–

IT wish list for BC/DR

–

Deployment considerations and summary

•

Zerto Virtual Replication 4.0

–

Cloud Continuity Platform

–

DR with Public Cloud

–

DR with Private Cloud – VMware vSphere or Microsoft Hyper-V

• Phil Goodwin is a Research Director within IDC’s Storage Systems and Software research practice. He provides detailed insight and analysis on evolving

industry trends, vendor performance, and the impact of new technology adoption. Mr. Goodwin is responsible for producing and delivering timely, in-depth market research with a specific focus on Data Protection, Business Continuity and Disaster Recovery, and Data Availability. Mr. Goodwin takes a holistic view of these markets, and covers risk analysis, service level

requirements and cost/benefit calculations in his research.

• Jennifer Gill, Director, Global Product Marketing, has more than 15 years of high-tech marketing experience with proven expertise in storage, virtualization and disaster recovery/business continuity (DR/BC). At Zerto, Jennifer has

several responsibilities including Technology Partnerships, Analyst Relations, the Customer Reference Program, as well as product messaging and global content strategy. Previously, Jennifer held management positions at EMC and played a key role in VCE. Jennifer has a BS in Biomedical Engineering from

Using hybrid cloud to (finally!) create a BC/DR

strategy

May 28, 2015

Phil Goodwin

Situation Analysis



BC /DR is perhaps the most

underfunded major IT activity

•

The DR line item is often the first to be

thrown overboard under budget pressure



As many as half of all organizations

could not survive as a going concern

after a data center catastrophe



DR testing is conducted infrequently

at best

IDC Research



69.7% of x86 infrastructure is virtualized

•

Growing to 71.7% by 2018



Recent SMB survey

•

61% RTO < 4 hours

•

37% RTO < 2 hours

•

61.7% RPO < 1 hour

•

53% use the cloud now, 35% plan to do so within 12-24 months

Bottom line: Business unit users are becoming increasingly intolerant of downtime and lost data.

Traditional DR Scheme Pros/Cons

Approach Pros Cons

Third Party DR provider subscription

•DR professionals •Hardened data center •Testing facility

•Expensive “insurance policy” •Does nothing for BC

•Difficult to test

•Compatibility issues •Over subscribed

In-house Active/Passive DCs •In-house control

•Exclusive use •BC enablement

•2X costs or constrained SLA •Passive assets sit idle

•More to manage

In-house Active/Active DCs •In-house control

•Exclusive use •HA enablement

•2X+ costs or constrained SLA •Complex management

•Poor asset utilization

Bottom line: Traditional DR schemes are expensive propositions. Organizations are reluctant to double their infrastructure costs for what is, frankly, an unlikely event.

IDC XaaS Definitions



Archive as a Service – Capacity optimized offsite

storage

 May include tape (LTFS)

 May include search/discovery/litigation services



Backup as a Service – Capacity optimized disk

offsite disk repository

 No facility for spinning up servers, etc.



Recovery as a Service – BaaS plus on-demand

compute/network services necessary to recover

and application

 Users must “roll their own” for BC/DR  No real difference for PaaS or IaaS



DR as a Service – RaaS plus added services

around run books, personnel plans and test

plan/execution

Often mis-labeled as DRaaS

Defining workload migration



The ability to move an application stack from one set of

infrastructure to another set

•

Includes across data center and public/private cloud



Hybrid cloud: a composition of both on-premise data center or

private cloud infrastructure integrated with public cloud

infrastructure using technology that allows the seamless passing

of data and/or entire workloads from one to the other

bi-directionally

Hybrid cloud to the rescue?

Benefits Limitations

1. Extends the capabilities of the core data center

2. No large up-front capital cost

3. On-demand compute and storage “pay as you go”

4. Can be used for BC and/or DR 5. DRaaS vendors popping up like

mushrooms after a rain

6. IT organizations can assert as

much or as little control as they like

1. Cloud provider infrastructure can vary and may not be compatible 2. Cloud providers may try to create

lock-in

3. Vendors play fast and loose with the definition of DRaaS

4. Does nothing to solve the people or process parts of DR

5. Moving the entire workload stack can be very complicated.

Bottom line: Hybrid cloud changes the BC/DR game, largely because it changes to cost equation. While an enabler for BC/DR, hybrid cloud alone is not enough.

Challenges of current hybrid cloud DR/BC

approaches



Movement of data and compute resources are often separated



Hypervisor incompatibilities

•

Migration for like-hypervisors only



Incompatible data replication

•

Array-based replication is often vendor-specific



Lack of agility

•

Traditional storage replication does not match the dynamics of VM

migration



Human intervention required

IT BC/DR wish list



No up-front CapEx



Easy to manage and maintain



Easy to test



Transparent compatibility



Migrate the entire workload as an entity



Automated migration/orchestration



On-demand capacity



Point-in-time recovery



No over subscription



Multi-purpose implementation

Leveraging workload migration



Use cases in addition to BC/DR

1.

Test/dev and debug

 Move app to a test bed at a specific point in time

2.

“Burst” performance requirements

 Move workload to the cloud for on-demand or seasonal bursts

3.

Consolidate dissimilar virtual infrastructure

 Mergers/acquisitions

4.

Workload or data archiving

 Store the entire workload, not just the data

Bottom line: Limiting workload migration to a BC/DR function misses much of the value that it can provide.

Deployment considerations



What are the primary use cases for your organization?

•

SLA requirements (RTO, RPO, data retention)?



Data center topology

•

Multiple data centers? ROBOs? Multiple cloud providers? SaaS?



Bandwidth requirements



Security requirements



Regulatory requirements



Business forecast

•

New acquisitions?

•

Rapid growth?

•

Cost control imperatives?

•

Third party integration (i.e., franchisees)?

Private

Public

SaaS Hybrid

Summary



Cloud is becoming a common extension of the IT data center

•

Hybrid cloud is the most common architecture

•

Cloud agility is enabled by virtual computing



BC/DR is a primary use case for hybrid cloud workload migration, but is

only one part of the value



Workload migration gives IT organizations the agility to meet rapidly

changing requirements

•

Opens new opportunities

•

Reduces vendor lock-in



Combining use case value propositions increases ROI and reduces

The Standard for Disaster Recovery

The Standard in BC/DR

200+

Cloud Service

Providers

600+

Channel

Partners

1000+

Enterprise Customers

Today’s Enterprise IT Infrastructure Landscape

Home Grown Apps

Enterprise

IT

On Premise Production Workloads

Today’s Enterprise IT Infrastructure Landscape

Enterprise

IT

Zerto

Cloud Continuity

Platform

Home Grown Apps

On Premise Production Workloads

One Strategic Solution – Cloud Continuity Platform

+200

Hybrid Cloud

DRaaS, Intra-Cloud & Reverse DRaaS

Satellite Offices

Any Distance

Private Cloud

Any Storage Multi-Hypervisor

Public Cloud

DRaaS to AWS

Large EC2

Zerto AWS Architecture

Large EC2 AWS Windows instance Zerto Cloud Appliance Web based DR Mgmt in AWS

Production Site vCenter VM VM VM VRA VM VM VM VRA AWS EC2 EC2 EC2 EC2 EC2 EC2 VPN to VPC VM-Level Replication ZVM ZCA

No downtime no impact installation Zerto Virtual Replication Appliance (VRA) One per source & target cluster hypervisor

Configure VPC connectivity

Zerto Virtual Manager (ZVM) & VRAs DR Management & VM level replication

No recovery EC2 instances Replica VM & Journal in S3 storage Auto disk import to EBS

DRaaS to AWS Overview

Utilizing power, cooling, hardware, licenses Expensive Physical BC/DR Site

Locked into datacenter lease

Server & storage refreshes Unpredictable High CAPEX costs IT budget consumed by DR

Only pay for what you use DRaaS to Public Cloud Flexibility of monthly billing

No cost of Server & storage refreshes Predictable Low OPEX cost IT budget for service improvement

Enterprise Class Virtual Replication

Hypervisor-based

Highly scalable

Compression, throttling, resiliency

Production Site vCenter VM VM VM VRA VM VM VM VRA BC/DR Site Mgmt VM VM VM VRA VM VM VM VRA WAN VM-Level Replication ZVM ZVM Continuous replication RPO = Seconds No snapshots = no impact Software only Install in Minutes No downtime

Save cost & replicate from

Anything to Anything

Enterprise Class Virtual Replication

Virtual Protection Group = Complete Application Protection

Recover Multi-VM applications consistently

Prioritize & meet SLAs

Pre-seeding, reduce initial sync

Virtualization features vMotion, svMotion, HA etc

Production Site Enterprise Applications VM VM VM VM VM VM vDisk vDisk vDisk vDisk

CRM, ERP, SQL, Oracle, SharePoint, Exchange

CRM VPG VM VM VM VM VM VM VM VM VM vDisk vDisk vDisk VM SQL VPG VM VM VM VM VM VM VM VM VM VM vDisk vDisk vDisk vDisk vDisk VM RPO 4 seconds RPO 9 seconds

Continuous Data Protection

Simply re-wind to Any Point in Time

Protection against Logical Failures, not just disasters

Recover from Seconds ago, not the last Backup or Snapshot

Application Consistency and write-order fidelity

Disaster Recovery Automation

Boot order, Re-IP

RTO = Minutes

Scripts & Commit Policy

Production Site vCenter VRA VM VM VM VM VM VM VRA BC/DR Site Mgmt VRA VRA WAN Recovery ZVM ZVM Automated Failback

Replication of Only Changes

AWS failback V2V export

Click to test in isolated network

Non-disruptive failover testing

Not just for DR & Offsite Clone

VM VM VM VM VM VM VM VM VM VM VM VM Failover Test Click to move Migrate in minutes

Seconds of lag, test before move

VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM Move Failback

BC/DR Site SCVMM VM VM VM VRA VM VM VM VRA ZVM v Offsite Backup

Offsite Backup

Backup to Offsite repository

in any site or public cloud

BC/DR site failure protection

Always Recover

VPG backup

3rd_{Copy from replica data}

Daily, Weekly or Monthly schedule

Extend journal protection

Simplicity

HTML5 tablet ready Consistent Mgmt & Control across hypervisors

Hypervisor integrated

Simple to manage

Status, KPIs, Alerts

Ensure compliance DR Reporting Prove recovery capability

Before Zerto

Continuous Data Protection

Offsite Backup

After - One Zerto Software Solution

Offsite Backup Replication

Scalable

Software

24/7 Global

Support

Market

Leader

Strategic

Solution

Protect

Any Cloud

Join the Zerto

Revolution