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 ReplicationDR ScenariosApplication AgnosticStorage Agnostic 6. Relevance of Hyper-V Replica Hyper-V & Failover Clustering: Site AHyper-V Replica: Availability across datacenter Site B 7. Flexible DeploymentReplication between two data centers Replication between SMB to hoster 8. New in Hyper-V 2012 R2Extended Replication! 9. Asynchronous Replication 10. Replication Resiliency Resiliency from Failures Retry and resume semantics ResynchronizationSeamless 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 ASite BPre-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 replicationSite ASite B1. 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 networkSite ASite 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 ReplicaServer NameIP AddressSQLVM10.22.100.XX 30. Demo: Alternate Network Config 31. Deployment Considerations 32. Avg. Replication Latency (mins)Network Capacity 15 105 0 123456Uncompressed data transferred in 24 hrs7 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 bandwidthIdeal number of parallel transfers1.5 Mbps, 100ms, 1% packet loss3 (Default)300 Mbps, 10ms, 1% packet loss10 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