Hyper-V Replica: adding a new defense layer to your disaster recovery plan…Mike ResselerEvangelist Veeam Software@mikeresseler | @veeam

Cost

Overview

Relevance & Capabilities

Deployment Considerations

PowerShell

Tips

Agenda

Overview

Inbox Replication DR Scenarios

Application Agnostic Storage Agnostic

Relevance of Hyper-V Replica

Hyper-V Replica:Availability across datacenter

Site A Site B

Hyper-V & Failover Clustering:

Flexible Deployment

Replication between two data centersReplication between SMB to hoster

New in Hyper-V 2012 R2

Extended Replication!

Asynchronous Replication

Replication Resiliency

Resiliency from FailuresRetry and resume semanticsResynchronization

Seamless handling of VM MobilityNo admin intervention requiredLive Migration, Storage Migration and Quick MigrationWithin cluster and across cluster

Linux Support!• File-System Consistent snapshots

• IP address injection

Demo: Setting up Replica on a host

Firewall Rule

PowerShellSet-VMReplicationServer -ReplicationEnabled $true -AllowedAuthenticationType Integrated -IntegratedAuthenticationPort 80 -DefaultStorageLocation“D:\Example” -ReplicationAllowedFromAnyServer $true

Demo: Replicating our first VM

PowerShell$ReplicaServer = “HyperV02.md.local”

$RecoveryPort = 80

$PrimaryVM1 = “TestVM”

$PrimaryServer = “HyperV01.md.local”

Set-VMReplication -VMName $PrimaryVM1 -ReplicaServerName$ReplicaServer -ReplicaServerPort $RecoveryPort -AuthenticationType Integrated -CompressionEnabled $true -RecoveryHistory 0

Start-VMInitialReplication –VMName $PrimaryVM1

VM Mobility

Site A Site B

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

DR Scenarios

Planned Failover

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• Started on Primary VM, ended on Replica VM

• No duplicate VM is created

• Timeframe: depends on you

• Recommed frequency: 6 months

• Replication: Continues, reversed mode

• Data Loss: No

• Down Time: Yes (Planned)

Demo: Planned Failover

Test Failover

Non-disruptive testing of workload – zero downtimeTest any recovery pointPre-configure isolated network

Site A Site B

Test Failover Demo Setup

Test FailOver• Started Replica VM

• Duplicate VM is created

• Timeframe: Short

• Recommended frequency: once a month

• Replication: Continues

• Data Loss: No

• Down Time: No

Demo: Test Failover

Failover• When there is an issue

• Replica uses Remote WMI to test if primary is stillrunning (to prevent split-brain)

• Previous PIT if recovery history is used

• If failover is OK, do a complete to merge

FailOver• Started Replica VM

• No duplicate VM is created

• Timeframe: depends

• Recommed frequency: never

• Replication: Stopped

• Data Loss: Possible

• Down Time: Yes

Demo: Failover

Network Configuration on Replica

Server Name IP Address

SQLVM 10.22.100.XX

Deployment Considerations

Network Capacity

0

5

10

15

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

. Re

plic

atio

n L

ate

ncy

(m

ins)

Uncompressed data transferred in 24 hrs

Network Throttling• Use Windows Server 2012 QoS to throttle replication traffic

• Throttling based on the destination subnet

• Throttling based on the destination port

- Throttling based on Application Name

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 Interoperability

• 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

Server Impact• 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:

•

• Memory ~50MB per replicating VHD

• CPU impact <3%

PowerShell• Use PowerShell to manage and automate your replica’s

• Get-command –Module Hyper-V | where {$_.Name –like“*replication*”}

• Get-command –Module Hyper-V | where {$_.Name – like“*failover*”}

Tips• Use bandwidth control!

• Firewall!

• Cluster: Replica Broker role

• Traffic encrypted or not?

• Which vhd(x)?

• Watch for resynchronization!

Capacity Planner• http://www.microsoft.com/en-

us/download/details.aspx?id=39057

Out-of-Band IR• Create Replica on Primary Site

• Choose “Send initial copy using external media”

• Move over data

• Import initial replica

Out-of-Band IR - PowerShell• Enable-VMReplication –VMName TestVM –ReplicaServerName

HyperV02.md.local –ReplicaServerPort 80 –AuthenticationTypeKerberos

• Start-VMInitialReplication –VMName TestVM –DestinationPathF:\VirtualMachineData\

• Import-VMInitialReplication –VMName TestVM -Path D:\VirtualMachineData\ TestVM_A60B7520-724D-4708-8C09-56F6438930D9

Out-of-Band Demo

Saving Disk Space• Use Dynamic disks at the Replica Side

• Enable replication from the customer to the hosting provider using online IR or out-of-band IR.

• The hosting provider waits for the IR to complete.

• The hosting provider can then pause the replication at any time on the Replica server – this will prevent HRL log apply on the disk while it is being converted.

• The hosting provider can then convert the disk from fixed to dynamic using the Edit Disk and Convert option

• The hosting provider then replaces the fixed disk with the dynamic disk at the same path and with the same name.

• The hosting provider resumes replication on the Replica site.

• Convert-VHD –Path c:\FixedDisk.vhdx –DestinationPath f:\FixedDisk.vhdx –VHDTypeDynamic

Online Resize supported?• No need for resync

• No need to delete and reenable

• But you need to do it on both sides manually

• However: Failover older recovery points…

Upgrading to R2• First Upgrade Replica Servers

• Or migrate to new 2012 R2 server

• Then your primary server

Deduplication on Replica server• Without recovery points… No problem

• With recovery points:

• Slower… 5 to 7 times…

• 15 seconds can be a problem… 5 minutes maybe…

• Solution:

• Defragment volume (once every 3 days at least)

• Increase the dedup policy to 1 day instead of 3

Best Practices Analyzer

Best Practices Analyzer37 A Replica server must be configured to accept replication requests 38 Replica servers should be configured to identify specific primary servers authorized to send replication traffic 39 Compression is recommended for replication traffic 40 Configure guest operating systems for VSS-based backups to enable application-consistent snapshots for Hyper-V Replica 41 Integration services must be installed before primary or Replica virtual machines can use an alternate IP address after a failover 42 Authorization entries should have distinct tags for primary servers with virtual machines that are not part of the same security group. 43 To participate in replication, servers in failover clusters must have a Hyper-V Replica Broker configured 44 Certificate-based authentication is recommended for replication. 45 Virtual hard disks with paging files should be excluded from replication 46 Configure a policy to throttle the replication traffic on the network 47 Configure the Failover TCP/IP settings that you want the Replica virtual machine to use in the event of a failover 48 Resynchronization of replication should be scheduled for off-peak hours 49 Certificate-based authentication is configured, but the specified certificate is not installed on the Replica server or failover cluster nodes 50 Replication is paused for one or more virtual machines on this server 51 Test failover should be attempted after initial replication is complete 52 Test failovers should be carried out at least monthly to verify that failover will succeed and that virtual machine workloads will operate as expected after failover 53 VHDX-format virtual hard disks are recommended for virtual machines that have recovery history enabled in replication settings 54 Recovery snapshots should be removed after failover

PowerShell• Invoke-BpaModel -ModelId Microsoft/Windows/Hyper-V

• Get-BpaResult -ModelId Microsoft/Windows/Hyper-V

• Get-BpaResult -ModelId Microsoft/Windows/Hyper-V -Filter Noncompliant

Site Recovery

Cust

ome

Microsoft Azure Site Recovery

MicrCust

DR OrchestrationDR Orchestration

Target: Microsoft Azure

for Windows Server 2012+ Hyper-V

Extensible Data Channel

SCVMM

&

DRP

SCVMM

&

DRP

Orchestration and Replication: InMage Scout

Microsoft Azure Site Recovery

Primary Site

InMage Scout

Orchestration and Replication: Hyper-V Replica, SQL AlwaysOn

Microsoft Azure Site Recovery

Primary Site

Hyper-V

On-premises to On-premises protection (Site-to-Site)

Orchestrated Disaster Recovery

Microsoft Azure Site Recovery

Orchestration Channel

Replication channels:

Hyper-V Replica, SQL AlwaysOn,

SAN

Primary Site

Hyper-V

Recovery Site

Hyper-V

Microsoft Azure Site Recovery

Orchestration and Replication

channel: InMage Scout

Primary Site

VMware / Physical

Recovery Site

InMageScout

InMageScout

Key features include:

Automated VM protection and replication

Remote health monitoring

Near zero RPO

No-impact recovery plan testing

Customizable recovery plans

Minimal RTO – few minutes to hours

Orchestrated recovery when needed

Replicate to – and recover in – Azure

Heterogeneous physical and virtual support

On-premises to Azure protection (Site-to-Azure)

VMware / Physical

VMware / Physical

COMING SOON!

Download InMage Scout

Possibilities

• On-Premises VMM Site to Azure (Hyper-V Replica)

• On-Premises to On-Premises VMM Site (Hyper-V Replica)

• On-Premises to On-Premises VMM Site (SAN Replication)

• On-Premises to On-Premises VMware Site protection

• On-Premises to Azure Hyper-V Site protection

Additional information• http://www.veeam.com/wp-hyper-v-replica-

depth.html

Thank Youwww.systemcenteruniverse.asia

…for updated content and NEWS