© 2014 VMware Inc. All rights reserved.

BC/DR Strategy with VMware

VMware vForum, 2014 Andrea Teobaldi Systems Engineer @teob77

What’s on the agenda? •  Defining the problem

•  Definitions

•  VMware technologies that provide BC and DR

–  vSphere HA and FT

–  vSphere App HA

–  vSphere Data Protection / Advanced

–  vSphere Replication

–  vCenter Site Recovery Manager (SRM)

•  vCloud Hybrid Service - Disaster Recovery

IT Business Continuity

Is It a Real Problem?

What’s the Difference?

Disaster Avoidance

Disaster Recovery

Planned vs. Unplanned

Disaster Recovery vs. Business Continuity Example: Tuesday, August 23, 2011 at 1:51 PM EDT - Magnitude 5.8 earthquake near Mineral, Virginia

Disaster recovery required? No

Interruption to business?

YES!

Fault Tolerance vs. High Availability •  Fault tolerance

–  Ability to recover from component loss –  Example: Hard drive failure

•  High availability

Uptime percentage in one year Downtime in one year 99 3.65 days 99.9 8.76 hours 99.99 52 minutes 99.999 “five nines” 5 minutes

X

Quickly define…

Work Recovery Time (WRT) Determines the maximum tolerable amount of time that is needed to verify the system and/or data integrity

Recovery Time Objective (RTO) How long it should take to recover

Recovery Point Objective (RPO) Amount of data loss that can be incurred

Maximum Tolerable Downtime (MTD) Downtime that can occur before significant loss is incurred Examples: Financial, reputation

vSphere HA – Keep In Mind…

•  RTO – measured in minutes (not seconds)

•  Requires shared storage

•  Best practices

–  Use admission control – percentage policy

–  Test post-failure performance with host maintenance mode

–  Isolation response – leave powered on

–  Network and storage redundancy

vSphere Fault Tolerance (FT)

•  Zero recovery time, data loss

–  Host hardware failure only

–  Does not protect against OS and application failure

•  Works fine with HA, App HA

•  Why not FT?

–  Resource requirements – does workload really need it?

–  VM has multiple CPUs

–  No VM snapshots – backups require agent

Making an Application Service Highly Available

vSphere HA Cluster

vFabric Hyperic Virtual Appliance

vSphere App HA Virtual Appliance

Hyperic Agents Running in VMs

vCenter Server

vSphere vSphere vSphere vSphere

VMware vFabric™ tc Server

vSphere App HA New

Policy-based

Protect off-the-shelf apps

Data Protection (Backup and Restore) •  Agents? No Agents? – Both!

–  No agents for majority of workloads – keep it simple –  Agents for certain apps

•  vSphere Data Protection (VDP) Advanced –  Backup and recovery for VMware, from VMware –  Based on proven, mature EMC Avamar™ –  Agent-less VM backup and restore –  Agents for granular tier-1 application protection

VDP Advanced – Keep In Mind…

•  Uses VADP – VM snapshots, CBT

•  Utilizes Windows VSS in VMware Tools

•  Works fine with HA, not with FT

•  RDM – virtual yes, physical no

•  Is it DR?

–  Maybe – depends on RTO, RPO

–  Needs replication offsite, right?

VDP Advanced – Best Practice…

•  Prepopulate DNS, always use FQDN

•  Manage VM snapshots

•  Avoid deploying to slow storage

•  Do not power-off, always shut down gracefully

•  Do not schedule backups during maintenance window

vSphere Replication – DR •  Native tool built into the platform •  Per-VM hypervisor replication, managed in VC

Selectable RPO from 15 min up

to 24 hours

Selectable destination

datastore (Disk-type agnostic)

New Feature – Retain Historical Replicas

vSphere

VR Agent

After recovery, use the snapshot manager to revert to earlier points

Retention of multiple points in time allows reversion to

earlier known good states

vSphere Replication – Interoperability

§  Fault tolerance – Doesn’t work with VR •  FT conflicts at the

vSCSI disk filter level.

§  VDP • Mostly no problem!

•  If using VSS… ensure you are using 5.5!!

§  HA, vMotion, DRS

§  Storage vMotion and Storage DRS • Now supported!

vSphere Replication – Best Practices •  RPO

–  Only what is necessary! –  Just because you can…

•  RTO –  Don’t set one! No testing, no automation, manual process.

•  VSS – Only if necessary!

•  What about bandwidth? –  Very hard to determine, do a local loopback first… http://blogs.vmware.com/vsphere/2014/04/vsphere-replication-capacity-planning-appliance.html

•  RDMs? Don’t use them. If you must, use virtual compatible. •  Don’t mix ABR and VR!

SRM

•  A Disaster Recovery engine •  A tool that uses externally replicated data (VR or

array based) to speed the RTO of a BCP •  A product that allows for DR to be tested, automated,

planned, repeatable and customizable

What is it?

•  A replication engine •  A tool for systems that need near-instant RPO •  A disaster avoidance stretched cluster

What is it not?

Key Components of SRM

Replication

vCenter Server

SRM Server

§ One vCenter Server (Windows or VCVA) per site, same versions

§ One SRM Server per

site, same versions

§  vSphere hosts, recommend same versions per site (pre vSphere 5.x only if using array replication)

vSphere Essentials Plus and higher editions supported

vCenter Server

SRM Replication Options

•  SRM can utilize BOTH array based AND vSphere Replication

•  SRM will “see” existing standalone vSphere Replication protected VMs

•  SRM can install vSphere Replication from scratch if needed

Hub LUN 2

Web

Multi-tier App

DB

App

vSphere Replication

Storage-based Replication

LUN 1

Web

DB

App

Multi-tier App

Recovery Workflows

•  User defined recovery plan •  Minimize errors

Failover Automation

•  Isolated test environment •  Increase confidence in DR process

Non-disruptive Failover Testing

•  Zero data loss •  Operational migration

Planned Migration

•  Re-protect VM’s, migrate back

Failback Automation

SRM Interoperability

•  Works with VR –and- ABR

•  Backups, VADP or other are fine

•  HA is no problem at all

•  vMotion and DRS are fine

•  Storage vMotion and Storage DRS – Sort of… –  Replication Dependent

•  FT is “yellow” –  Array replicated only and the

FT status is not recovered

•  Web vs vSphere Client

vCloud Hybrid Service - Disaster Recovery

VMware vSphere

VMware vCenter Server

vSphere Replication

Site A (Primary)

Servers

vCHS, Site B (Recovery)

US East Region

UK London

1Dependent on available bandwidth

Simple and secure asynchronous replication and failover for vSphere

•  Warm standby capacity on vCHS •  Self-service protection, failover and

failback workflows per VM •  15 min1 – 24 hr. recovery point

objective (RPO) •  4 hours or less recovery time

objective (RTO) •  Initial data seeding by shipping a disk •  Includes:

•  2x 7-day DR tests per year •  30 days of recovered VM run time

25

Disaster Recovery – New Core Class of Service

Minimum size: 10GHz vCPU 20GB vRAM

Starts at 1 TB

10 Mbps allocated 2 Public IPs 2 Tests*

Term Lengths: 1m, 12m, 24m, 36m subscriptions

Dedicated Cloud Instance

Virtual Private Cloud Instance

vCloud Hybrid Service Standard Servicer Tiers

New Instance Type as DR Service Tier

DR-VDC Instance

Disaster Recovery Add-On Options

Standard  Storage,  Support,  Bandwidth  

Compute  (subscrip8on)  

Compute    (one  8me)  

IP  Address  

Offline  Data  Transfer  

Direct  Connect  

Addi8onal  Failover  test  

VMware vCloud Hybrid Service – Disaster Recovery

vSphere Provides The Best Foundation For Disaster Recovery in the Cloud

Encapsulation: Simple Application Protection •  Entire system – including application, OS, and data – is stored

as virtual machine files •  Entire system can be protected with data protection tools

Hardware-Independence: Flexible Infrastructure •  Eliminate the need for SAN or array-based replication •  Enable consistent recovery throughout data center lifecycle

changes

Hybrid Aware: Seamless Integration with vCHS •  Reduced costs by leveraging the cloud for DR •  Scale your protection capacity to meet variable demand

28

Fully integrated with vSphere Web Client

Consistent management and operational best practices…

•  Single interface and common management

•  Designed to integrate with vCloud Hybrid Service

•  Doesn’t require “console hopping”

29

Disaster Recovery System Requirements

Primary Data Center

•  VMware vSphere 5.0 or above –  vSphere Essentials Plus –  vSphere Standard –  vSphere Enterprise –  vSphere Enterprise Plus

•  VMware vCenter 5.1 or above –  Includes vSphere Web Client

•  vSphere Replication Appliance 5.6 –  1:1 mapping with vCenter*

•  Public internet connectivity

vCloud Hybrid Service

•  DR subscription

CONFIDENTIAL 30

(DR Virtual Data Center instance)

CONFIDENTIAL 31

Questions?

GRAZIE !

Ricordatevi i feedback !

Vi aspettiamo ai DEMO POINT !