Download presentation
Presentation is loading. Please wait.
Published byMyrtle Powell Modified over 9 years ago
2
Complete VM Mobility Across the Datacenter Server Virtualization Hyper-V 2012 Live Migrate VM and Storage to Clusters Live Migrate VM and Storage Between Clusters You can move a VM anywhere in your datacenter with zero downtime! Running VMs can be added to the cluster Running VMs can be removed from the cluster Running VMs can be added to the cluster Running VMs can be removed from the cluster Live Migrate VM and Storage to Stand- Alone Server TechNet
3
Live Migration Share Nothing Server VirtualizationServer Virtualization Hyper-V 2012 TechNet
4
Complete VM Mobility Across the Datacenter Server Virtualization Hyper-V 2012 You can move a VM anywhere in your datacenter with zero downtime! There are two authentication protocols CredSSP or Kerberos There are two authentication protocols CredSSP or Kerberos Running VMs can be added to the cluster Running VMs can be removed from the cluster Running VMs can be added to the cluster Running VMs can be removed from the cluster TechNet
5
Live Migration within Cluster Server VirtualizationServer Virtualization Hyper-V 2012 TechNet
6
Dynamic Switch Ports By default, every vSwitch is placed in the default Primordial pool for the Ethernet resource pool Dynamic Switch Port functionality allows a VM to request to connect to one or more virtual switches in a poll of virtual switches Primordial pool vEthernet (Public)vEthernet (DMZ) Public poolDMZ pool vEthernet (Public)vEthernet (DMZ) Resource pool configuration using PowerShell (New-VMResourcePool) Two-part process 1. Create the Ethernet resource pool 2. Add the vSwitch to the resource pool Note: Properly configured Ethernet resource pools on Hyper-V hosts should allow for a proper automatic connection when a VM migrates because the virtual machine network configuration is now part of the virtual machine configuration Server Virtualization Hyper-V 2012
7
TechNet
8
Hyper-V Replica Benefits Server Virtualization Hyper-V 2012 Fail over your production workloads to a Replica servers at a secondary location with minimal downtime Hyper-V Replica provides the option to restore virtualized workloads to a point in time Hyper-V Replica enables Infrastructure as a Service (IaaS) for hosting providers that host dedicated virtual servers for their customers Hyper-V Replica server and storage hardware at each site do not have to be identical Provides APIs that enable IT vendors to build enterprise disaster recovery solutions (Windows Azure Hyper-V Recovery Manager) TechNet
9
High Level Architecture Server Virtualization Hyper-V 2012 Primary VM Replica VM VHD Logfile (.hrl) VHD Logfile (.hrl) Site ASite B
10
Hyper-V Replica Overview Server Virtualization Hyper-V 2012
11
Hyper-V Replica Types TYPE 1 Every 5 Minutes Changes are sent to replica server and are merged on the Replica VM. New Log is created TYPE 2 Every 1 hour a VM Snapshot is created on the Replica Server Number of snapshots can be configured but not the interval Oldest snapshot merged with the parent TYPE 3 VSS Snapshot at desired interval on Primary VM VM Snapshot Every 1 Hour Every 5 Minutes Every 5 Minutes.HRL Every 5 Minutes.HRL Desired Interval VM Snapshot Every 1 Hour Server Virtualization Hyper-V 2012 TechNet
12
Hyper-V Replica Considerations No AD Domain required unless Failover Cluster is involved Additional security configuring Authorization Tag Firewall rules should be configured http or https Mutual Authentication (AD) or Certificates QoS for Replica traffic should be considered Replica network can NOT be specified Server Virtualization Hyper-V 2012 TechNet
13
Server Virtualization Hyper-V 2012 TechNet
14
Server Virtualization Hyper-V 2012 TechNet
15
Server Virtualization Hyper-V 2012 Primary 10.22.100.XX 15.25.10.XX Client Replica TechNet
16
Server Virtualization Hyper-V 2012 Primary VM IP Addressing IPV4 Address: 192.168.0.1 Subnet mask: 255.255.255.0 Default GW: 192.168.0.100 Preferred DNS: 192.168.0.254 Alternate DNS: 192.168.0.253 Replica VM IP Addressing IPV4 Address: 10.0.0.1 Subnet mask: 255.0.0.0 Default GW: 10.0.0.100 Preferred DNS: 10.0.0.254 Alternate DNS: 10.0.0.253 Considerations Should be configured after Replica VM creation Failback IP should be configured on Primary VM as well ICs Required TechNet
17
Server Virtualization Hyper-V 2012 Primary Server AD Exchange Outlook Replica AD Replica Exchange Replica Outlook Production Network Replica Server Test AD Test Exchange Test Outlook Test Network TechNet
18
Server Virtualization Hyper-V 2012 TechNet 1.5Mbps, 20ms latency, 1% packet loss
19
Server Virtualization Hyper-V 2012 TechNet
20
Server Virtualization Hyper-V 2012 TechNet
21
21 Critical Replica paused on the Replica VM Primary unable to send the replica to the replica server > 6 hours initial replication required Warning >20% of replication cycles have been missed in a monitoring More than an hour has elapsed since the last sent replica (on the primary VM) or the last received replica (on the replica VM) If Initial Replication has not been completed If Failover has been initiated, but reverse replication has not been initiated If the primary VM’s replication is paused Normal Less than or equal to 20% of the replication cycles are missed The last synchronization point was less than an hour The average latency is less than or equal to 5 minutes Microsoft Server Virtualization Hyper-V 2012
22
TechNet
23
Server Virtualization Hyper-V 2012 TechNet
24
Server Virtualization Hyper-V 2012 TechNet
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.