Hyper-V ReplicaKristian NeseCTOLumagate

Average # of outages per year ?

A. 1B. 3C. 6D. 25

Average # of outages per year ?

A. 1B. 3C. 6D. 25

Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500

Average # of outages per year ?

A. 1B. 3C. 6D. 25

Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500

Average # of outages per year ?

A. 1B. 3C. 6D. 25

Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500 x 6 = $75,000!

% of SMB respondents who DO NOT have a Disaster Recovery plan?

A. 10B. 15C. 25D. 50

% of SMB respondents who DO NOT have a Disaster Recovery plan?

A. 10B. 15C. 25D. 50!

Those 50% of SMB Disaster Recovery plan is…

Session Objectives and Takeaways

• Relevance and Overview of Hyper-V Replica • Capabilities and Value Proposition• Deployment Considerations

Relevance of Hyper-V Replica

Hyper-V Replica:Availability across datacenter

Site A Site B

Hyper-V & Failover Clustering: Availability within datacenter

Overview of Hyper-V Replica

Affordable Easy to manage Flexible

Inbox Replication DR Scenarios

Application Agnostic Storage Agnostic

Flexible Deployment

Head Office

Branch Office

• Replication between two data centers• Replication between SMB to hoster

Hoster’s Data Center

Customer 1 Customer 2

DEMO

HYPER-V REPLICA – SETUP

Asynchronous Replication

Primary Host

Primary VM

Log File

Log File

Replica Host

Replica VM

• Resiliency from Failures• Retry and resume semantics• Resynchronization

• Seamless handling of VM Mobility• No admin intervention required• Live Migration, Storage Migration and Quick Migration• Within cluster and across cluster

Replication Resiliency

Site A

Site B

VM Mobility

• Pre-requisites: • Primary migration: All primary servers must be authorized• Replica migration: Requires Hyper-V Replica Broker

DR Scenarios

Testing DR plan Site Maintenance

Impending Disaster Sudden Disaster

1. Shutdown primary VM2. Send last log3. Failover Replica VM4. Reverse replicate

• Testing DR or site maintenance or impending disaster• Zero data loss but some downtime • Efficient reverse replication

Site A Site B

Planned Failover

Ongoing replication

Network Configuration on ReplicaVM Connectivity on Replica

Vswitch creation and assignmentVLAN tagging

VM identity in a different subnetInject static IP address Auto assignment via DHCP Preserve IP address via Network Virtualization

VM Name ResolutionUpdate DNS records to reflect new IP address

Primary 10.22.100.XX

Replica15.25.10.XX

Client

Server Name

IP Address

SQLVM 10.22.100.XX

Server Name

IP Address

SQLVM 15.25.10.XX

DEMO

HYPER-V REPLICA – PLANNED FAILOVER

Test Failover

• Non-disruptive testing of workload – zero downtime• Test any recovery point• Pre-configure isolated network

Site A Site B

Test Failover Setup

Primary Server

AD

Exchange

Outlook

Replica AD

Replica Exchang

e

Replica Outlook

ProductionNetwork

ReplicaServer

Test AD

Test Exchang

e

Test Outlook

Test Network

DEMO

HYPER-V REPLICA – TEST FAILOVER

Deployment Considerations

Deployments Customer Segment

Storage Workloads

Hyper-V Replica

SMBHoster

Enterprise

0.5 GB 1 GB 3 GB 5 GB 7 GB 8 GB 10 GB0

4

8

12

Uncompressed data transferred in 24 hrs

Avg

. R

ep

licati

on

Late

ncy (

min

s)

512 Kbps, 20ms la-tency, 1% packet loss

768 Kbps, 20ms latency, 1% packet loss

1.5Mbps, 20ms latency, 1% packet loss

Network CapacityCapacity planning is criticalEstimate rate of data changeEstimate for peak usage and effective network bandwidth

Network Throttling• Use Windows Server 2012 QoS to throttle replication

traffic

• Throttling based on the destination subnet

New-NetQosPolicy “Replication Traffic to 10.0.0.0/8” –DestinationAddress 10.0.0.0/8 –MinBandwidthWeightAction 40

• Throttling based on the destination port

New-NetQosPolicy “Replication Traffic to 8080” –DestinationPort 8080 –ThrottleRateActionBytesPerSecond 100000

Network Utilization

• Replicating multiple VMs in parallel• Higher concurrency leads to resource contention and latency• Lower concurrency leads to underutilizing

• Manage initial replication through scheduling• Manage delta replication

Network bandwidth Ideal number of parallel transfers

1.5 Mbps, 100ms, 1% packet loss

3 (Default)

300 Mbps, 10ms, 1% packet loss 10

• Backup copy to seed Initial Replication• Back-up Primary VM

• Concurrent backup and replication are handled seamlessly• Restore of Primary VM requires resync

• Back-up Replica VM• Replica VM turned off• Backup is on hold when VHD is modified by replication• Restore of replica VM requires resync

Backup Interoperability

• Impact on primary server• Storage space: Proportional to writes in the VM• Storage IOPS on ~ 1.5 times write IOPS

• Impact on replica server• Storage space: Proportional to the write-churn

• Each additional recovery point ~10% of the base VHD size• Storage IOPS: 0.6 times write IOPS to receive and convert

• 3-5 times write IOPS to receive, apply, merge for additional recovery points

• Memory ~50MB per replicating VHD • CPU impact <3%

Server Impact

DEMO

• System Center 2012 SP1 and HVR• Unplanned Failover

In Review: Session Objectives and Takeaways

• Relevance of Hyper-V Replica and when to use it• Complements high availability and migration

• Capabilities and Value Proposition• Inbox solution• Flexible deployment scenarios• Comprehensive replication and failover capabilities

• Deployment Considerations• Network• System Impact• Back-up Inter-op

Q&A