1 / 32

Enabling Disaster Recovery for Hyper-V Workloads Using Hyper-V Replica

VIR321. Enabling Disaster Recovery for Hyper-V Workloads Using Hyper-V Replica. Benjamin Armstrong Senior Program Manager Lead. Average # of outages per year ? . 1 3 6 25. Average # of outages per year ? . 1 3 6 25. Downtime cost per day ?. $500 $ 3 ,850 $7,750 $12,500.

badu
Download Presentation

Enabling Disaster Recovery for Hyper-V Workloads Using Hyper-V Replica

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VIR321 Enabling Disaster Recovery for Hyper-V Workloads Using Hyper-V Replica Benjamin Armstrong Senior Program Manager Lead

  2. Average # of outages per year ? • 1 • 3 • 6 • 25

  3. Average # of outages per year ? • 1 • 3 • 6 • 25 Downtime cost per day ? • $500 • $3,850 • $7,750 • $12,500

  4. Average # of outages per year ? • 1 • 3 • 6 • 25 Downtime cost per day ? • $500 • $3,850 • $7,750 • $12,500

  5. Average # of outages per year ? • 1 • 3 • 6 • 25 Downtime cost per day ? • $500 • $3,850 • $7,750 • $12,500 x 6 = $75,000!

  6. % of SMB respondents who DO NOT have a Disaster Recovery plan? • 10 • 15 • 25 • 50

  7. % of SMB respondents who DO NOT have a Disaster Recovery plan? • 10 • 15 • 25 • 50!

  8. Those 50% of SMB Disaster Recovery plan is…

  9. Overview of Hyper-V Replica DR Scenarios Inbox Replication Application Agnostic Storage Agnostic • Easy to manage • Flexible • Affordable

  10. Flexible Deployment Hoster’s Data Center • Replication between two data centers • Replication between SMB to hoster Branch Office Head Office Customer 2 Customer 1

  11. Flexible deployment Stand-alone to Stand-alone (Domain joined or Workgroup) Stand-alone to Cluster Cluster to Stand-alone Cluster to Cluster

  12. demo Replication Capabilities

  13. High level architecture Primary VM Replica VM VHD VHD Log file (.hrl) Log file (.hrl) MyLondon.contoso.com MySeattle.contoso.com

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

  15. Hyper-V Replica in clustered setup Failover Clustering: Availability within datacenter • Hyper-V Replica: Availability across datacenter Site A Site B

  16. Seamless Virtual Machine Migration MySeattle-1 MySeattle-2 MyLondon-1 MySeattle-3 MyLondon-2 MyLondon-3 MySeattle.contoso.com MyLondon.contoso.com

  17. Seamless Virtual Machine Migration MySeattle-1 MySeattle-2 MyLondon-1 MyLondon-2 MySeattle-3 Hyper-V Replica Broker MyLondon-3 MySeattle.contoso.com MyLondon.contoso.com

  18. DR Scenarios Site Maintenance Testing DR plan Impending Disaster Sudden Disaster

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

  20. Network Configuration on Replica Replica Primary 10.22.100.XX • VM Connectivity on Replica • Vswitch creation and assignment • VLAN tagging • VM identity in a different subnet • Inject static IP address • Auto assignment via DHCP • Preserve IP address via Network Virtualization • VM Name Resolution • Update DNS records to reflect new IP address 15.25.10.XX Client

  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. demo Test Failover

  24. Deployment Considerations SMB Hoster Enterprise Deployments Customer Segment Hyper-V Replica Storage Workloads

  25. Network Capacity • Capacity planning is critical • Estimate rate of data change • Estimate for peak usage and effective network bandwidth 1.5Mbps, 20ms latency, 1% packet loss

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

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

  30. Related Content VIR312: What's New in Windows Server 2012 Hyper-V, Part 1 VIR315: What's New in Windows Server 2012 Hyper-V, Part 2 VIR314: WS2012 Hyper-V Live Migration and Live Storage Migration VIR413: Hyper-V Performance, Scale & Architecture Changes Find Me Later At @VirtualPCGuy

  31. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related