Enabling Disaster Recovery for Hyper-V Workloads Using Hyper-V ReplicaShreesh DubeyPrincipal Group Program ManagerMicrosoft Corporation
VIR302
Average # of outages per year ? A. 1B. 3C. 6D. 25
Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500
Average # of outages per year ? A. 1B. 3C. 6D. 25
Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500
Average # of outages per year ? A. 1B. 3C. 6D. 25
Downtime cost per day ?A. $500B. $3,850C. $7,750D. $12,500 x 6 = $75,000!
Session Objectives and Takeaways
Relevance and Overview of Hyper-V Replica Capabilities and Value PropositionDeployment Considerations
Relevance of Hyper-V Replica
Hyper-V Replica:Availability across datacenter
Site A Site B
Hyper-V & Failover Clustering: Availability within datacenter
Overview of Hyper-V Replica
Affordable
Easy to manage
Flexible
Inbox Replication DR Scenarios
Application Agnostic Storage Agnostic
Flexible Deployment
Head Office
Branch Office
Replication between two data centersReplication between SMB to hoster
Hoster’s Data Center
Customer 1 Customer 2
Resiliency from FailuresRetry and resume semanticsResynchronization
Seamless handling of VM MobilityNo admin intervention requiredLive Migration, Storage Migration and Quick MigrationWithin cluster and across cluster
Replication Resiliency
Site A
Site B
VM Mobility
Pre-requisites: Primary migration: All primary servers must be authorizedReplica migration: Requires Hyper-V Replica Broker
1. Shutdown primary VM2. Send last log3. Failover Replica VM4. Reverse replicate
Testing DR or site maintenance or impending disasterZero data loss but some downtime Efficient reverse replication
Site A
Site B
Planned Failover
Ongoing replication
Network Configuration on Replica
VM Connectivity on ReplicaVswitch creation and assignmentVLAN tagging
VM identity in a different subnetInject static IP address Auto assignment via DHCP Preserve IP address via Network Virtualization
VM Name ResolutionUpdate DNS records to reflect new IP address
Primary 10.22.100.
XX15.25.10.X
X
Client
Replica
Server Name IP Address
SQLVM 10.22.100.XX
Server Name IP Address
SQLVM 15.25.10.XX
Test Failover
Non-disruptive testing of workload – zero downtimeTest any recovery pointPre-configure isolated network
Site A
Site B
Test Failover Demo Setup
Primary Server
AD
Exchange
Outlook
Replica AD
Replica Exchang
e
Replica Outlook
ProductionNetwork
ReplicaServer
Test AD
Test Exchang
e
Test Outlook
Test Network
Deployment Considerations
Deployments Customer Segment
Storage Workloads
Hyper-V Replica
SMBHoster
Enterprise
0.5 GB 1 GB 3 GB 5 GB 7 GB 8 GB 10 GB0
2
4
6
8
10
12
14
Uncompressed data transferred in 24 hrs
Avg
. R
ep
licati
on
Late
ncy (
min
s)
512 Kbps, 20ms latency, 1% packet loss 768 Kbps, 20ms la-
tency, 1% packet loss 1.5Mbps, 20ms
latency, 1% packet loss
Network CapacityCapacity planning is criticalEstimate rate of data changeEstimate for peak usage and effective network bandwidth
Network ThrottlingUse 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
Network Utilization
Replicating multiple VMs in parallelHigher concurrency leads to resource contention and latencyLower concurrency leads to underutilizing
Manage initial replication through schedulingManage 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 copy to seed Initial ReplicationBack-up Primary VM
Concurrent backup and replication are handled seamlesslyRestore of Primary VM requires resync
Back-up Replica VMReplica VM turned offBackup is on hold when VHD is modified by replicationRestore of replica VM requires resync
Backup Interoperability
Impact on primary serverStorage space: Proportional to writes in the VMStorage IOPS on ~ 1.5 times write IOPS
Impact on replica serverStorage 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%
Server Impact
In Review: Session Objectives and Takeaways
Relevance of Hyper-V Replica and when to use itComplements high availability and migration
Capabilities and Value PropositionInbox solutionFlexible deployment scenariosComprehensive replication and failover capabilities
Deployment ConsiderationsNetworkSystem ImpactBack-up Inter-op
Related Content
OrlandoWSV301 Building Hosted Public and Private Clouds Using Windows Server 2012WSV323 Deploying Private Clouds (Lessons Learned from the Windows Server 2012 TAP)
AmsterdamWSV301 Building Hosted Public and Private Clouds Using Windows Server 2012WSV323 Deploying Private Clouds (Lessons Learned from the Windows Server 2012 TAP)
Hands-on Labs • VIR21-HOL Configuring Windows Server 2012 Hyper-V Replica• VIR02-HOL Windows Server 2012 Hyper-V
SIA, WSV, and VIR Track Resources
Talk to our Experts at the TLC
#TE(sessioncode)
DOWNLOAD Windows Server 2012 Release Candidate
microsoft.com/windowsserverHands-On Labs
DOWNLOAD Windows Azure
Windowsazure.com/teched
Resources
Connect. Share. Discuss.
http://northamerica.msteched.com
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
TechNet
Resources for IT Professionals
http://microsoft.com/technet
Resources for Developers
http://microsoft.com/msdn
© 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.