NIC 2013 - Hyper-V Replica

1,613 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,613
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
39
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

NIC 2013 - Hyper-V Replica

  1. 1. Hyper-V ReplicaKristian NeseCTOLumagate
  2. 2. Average # of outages per year ?A. 1B. 3C. 6D. 25
  3. 3. Average # of outages per year ?A. 1B. 3C. 6D. 25Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500
  4. 4. Average # of outages per year ?A. 1B. 3C. 6D. 25Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500
  5. 5. Average # of outages per year ?A. 1B. 3C. 6D. 25Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500 x 6 = $75,000!
  6. 6. % of SMB respondents who DO NOT have aDisaster Recovery plan?A. 10B. 15C. 25D. 50
  7. 7. % of SMB respondents who DO NOT have aDisaster Recovery plan?A. 10B. 15C. 25D. 50!
  8. 8. Those 50% of SMB Disaster Recoveryplan is…
  9. 9. Session Objectives and Takeaways• Relevance and Overview of Hyper-V Replica• Capabilities and Value Proposition• Deployment Considerations
  10. 10. Relevance of Hyper-V Replica Hyper-V & Failover Clustering: Hyper-V Replica: Availability across datacenter Site A Site B
  11. 11. Overview of Hyper-V Replica Affordable Easy to manage Flexible
  12. 12. Flexible Deployment• Replication between two data centers• Replication between SMB to hoster
  13. 13. DEMO
  14. 14. Asynchronous Replication
  15. 15. 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
  16. 16. VM Mobility Site Site A B • Pre-requisites: • Primary migration: All primary servers must be authorized • Replica migration: Requires Hyper-V Replica Broker
  17. 17. DR Scenarios
  18. 18. Planned Failover • Testing DR or site maintenance or impending disaster • Zero data loss but some downtime • Efficient reverse replication 1. Shutdown primary VM Site A Site B 2. Send last log 3. Failover Replica VM 4. Reverse replicate
  19. 19. Network Configuration on ReplicaVM Connectivity on Replica Primary Replica Vswitch creation and assignment 10.22.100.XX 15.25.10.XX VLAN taggingVM identity in a different subnet Inject static IP address Auto assignment via DHCP Preserve IP address via Network Virtualization ClientVM Name Resolution Server IP Address Update DNS records to reflect new IP address Name SQLVM 15.25.10.XX 10.22.100.X X
  20. 20. DEMO
  21. 21. Test Failover • Non-disruptive testing of workload – zero downtime • Test any recovery point • Pre-configure isolated network Site A Site B
  22. 22. Test Failover Setup
  23. 23. DEMO
  24. 24. Deployment Considerations
  25. 25. Network Capacity Capacity planning is critical Estimate rate of data change Estimate for peak usage and effective network bandwidth 15 Avg. Replication Latency (mins) 10 5 0 0.5 GB 1 GB 3 GB 5 GB 7 GB 8 GB 10 GB Uncompressed data transferred in 24 hrs
  26. 26. 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
  27. 27. 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 3 (Default) loss 300 Mbps, 10ms, 1% packet 10 loss
  28. 28. 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
  29. 29. 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%
  30. 30. DEMO
  31. 31. In Review: Session Objectives andTakeaways• 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
  32. 32. Q&A

×