1. Mike Resseler
Using Hyper-V replica in your
environment. A new defense layer
in your Disaster Recovery Plan…
EMEA Microsoft Evangelist Veeam
Software
@MikeResseler

2. Introduction

3. Cost

4. Agenda

5. Overview
Inbox Replication
DR Scenarios
Application Agnostic
Storage Agnostic

6. Relevance of Hyper-V Replica
Hyper-V & Failover Clustering:
Site A
Hyper-V Replica:
Availability across datacenter
Site B

7. Flexible Deployment
Replication between two data centers
Replication between SMB to hoster

8. New in Hyper-V 2012 R2
Extended Replication!

9. Asynchronous Replication

10. Replication Resiliency
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

11. Linux Support!
• File-System Consistent snapshots
• IP address injection

12. Demo: Setting up Replica on a host

13. Firewall Rule

14. PowerShell
Set-VMReplicationServer -ReplicationEnabled
$true -AllowedAuthenticationType Integrated IntegratedAuthenticationPort 80 DefaultStorageLocation “D:Example” ReplicationAllowedFromAnyServer $true

15. Demo: Replicating our first VM

16. 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

17. VM Mobility
Site A
Site B
Pre-requisites:
Primary migration: All primary servers must be authorized
Replica migration: Requires Hyper-V Replica Broker

18. DR Scenarios

19. Planned Failover
• Testing DR or site maintenance or impending disaster
• Zero data loss but some downtime
• Efficient reverse replication
Site A
Site B
1.
2.
3.
4.
Shutdown primary VM
Send last log
Failover Replica VM
Reverse replicate

20. 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)

21. Demo: Planned Failover

22. Test Failover
Non-disruptive testing of workload – zero downtime
Test any recovery point
Pre-configure isolated network
Site A
Site B

23. Test Failover Demo Setup

24. Test FailOver
•
•
•
•
•
•
•
Started Replica VM
Duplicate VM is created
Timeframe: Short
Recommed frequency: once a month
Replication: Continues
Data Loss: No
Down Time: No

25. Demo: Test Failover

26. Failover
• When there is an issue
• Replica uses Remote WMI to test if primary is
still running (to prevent split-brain)
• Previous PIT if recovery history is used
• If failover is OK, do a complete to merge

27. FailOver
•
•
•
•
•
•
•
Started Replica VM
No duplicate VM is created
Timeframe: depends
Recommed frequency: never
Replication: Stopped
Data Loss: Possible
Down Time: Yes

28. Demo: Failover

29. Network Configuration on Replica
Server Name
IP Address
SQLVM
10.22.100.XX

30. Demo: Alternate Network Config

31. Deployment Considerations

32. Avg. Replication Latency
(mins)
Network Capacity
15
10
5
0
1
2
3
4
5
6
Uncompressed data transferred in 24 hrs
7

33. 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

34. 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

35. 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

36. 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%

37. 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*”}

38. Demo: Monitoring & PowerShell

39. Tips
•
•
•
•
•
•
Use bandwidth control!
Firewall!
Cluster: Replica Broker role
Traffic encrypted or not?
Which vhd(x)?
Watch for resynchronization!

40. Capacity Planner
• http://www.microsoft.com/enus/download/details.aspx?id=39057
• Only works on Windows Server 2012… not R2

41. Out-of-Band IR
• Create Replica on Primary Site
• Choose “Send initial copy using external
media”
• Move over data
• Import initial replica

42. Out-of-Band IR - PowerShell
• Enable-VMReplication –VMName TestVM –
ReplicaServerName HyperV02.md.local –
ReplicaServerPort 80 –AuthenticationType
Kerberos
• Start-VMInitialReplication –VMName TestVM –
DestinationPath F:VirtualMachineData
• Import-VMInitialReplication –VMName TestVM Path D:VirtualMachineData TestVM_A60B7520724D-4708-8C09-56F6438930D9

43. Out-of-Band Demo

44. 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 –
VHDType Dynamic

45. 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…

46. Upgrading to R2
• First Upgrade Replica Servers
• Or migrate to new 2012 R2 server
• Then your primary server

47. 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

48. Best Practices Analyzer

49. Best Practices Analyzer
37 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

50. PowerShell
• Invoke-BpaModel -ModelId
Microsoft/Windows/Hyper-V
• Get-BpaResult -ModelId Microsoft/Windows/Hyper-V
• Get-BpaResult -ModelId Microsoft/Windows/Hyper-V Filter Noncompliant

51. Hyper-V Recovery Manager

52. Please evaluate the session
before you leave
