Changes

Jump to: navigation, search

An Overview of Hyper-V Live Migration

2,059 bytes added, 17:09, 23 September 2009
no edit summary
- Hyper-V 2008 R2 must be deployed on both hosts. The first version of Hyper-V does not support live migration.
- Source and destination Hyper-V hosts must be configured as a Failover clusterwith shared storage enabled.
- Source and destination systems must be using shared storage (i.e. via SAN or iSCSI configurations)
- Source and destination systems must be running processors from the same manufacturer. It is not, for example, possible to migrate a virtual machine from an Intel based host to one containing an AMD CPU.
 
- The virtual machine on which the migration is to be performed must be configured as ''Highly Available'' and to use Cluster Shared Volumes.
 
- All Hyper-V hosts in the Failover cluster must be configured to boot from the same drive letter. In other words, a host that boots from the C drive cannot perform a live migration to host that boots from the D drive.
== The Live Migration Process ==
- '''Network Re-direction''' - The network environment is modified to direct traffic intended for the virtual machine to the destination host.
== Performing a Live Migration using the Failover Cluster Manager == Assuming that the system requirements outlined earlier in this chapter have been met and a virtual machine is running on a host within such an environment, a live migration can be initiated.  Live migrations may be initiated either from within the ''Failover Cluster Manager'' console or using Windows PowerShell. A migration may be performed using the manager as follows: In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want. In the console tree (on the left), select the node under which you want to move a clustered virtual machine using live migration. Right-click the virtual machine resource displayed in the center pane (not on the left), and then click Live migrate virtual machine to another node. Select the node that you want to move the virtual machine to. When migration is complete, the virtual machine is running on the new node. To verify that the virtual machine successfully migrated, you will see the virtual machine listed under the new node (in Current Owner).  == Performing a Live Migration using Windows PowerShell == For a command-line or script based method of performing live migrations, the Windows PowerShell environment may be used as follows: Open PowerShell. Click Start, point to All Programs, click Windows Powershell 2.0, and then click Windows Powershell 2.0.  The Failover Clustering feature must be installed on the computer on which you are starting the PowerShell session. To install the Failover Clustering feature, type: Add-Module FailoverClusters  Type:  Get-Cluster “<Cluster Name>” | Move-ClusterVirtualMachineRole -Name “<VM group name>” -Node “<Destination node name>”  Where: <Cluster Name> is the name of the cluster that the virtual machine is included in. 
Assuming that <VM group name> is the system requirements outlined earlier in this chaoter have been met and a virtual machine is running on a host within such an environment, a live migration can be initiatedresource group.
Live migrations may be initiated either from within the ''Failover Cluster Management'' console or using Windows PowerShell.
Once launched, <Destination node name> is the Failover Cluster console lists name of the destination node to which you would like to move the virtual machines running on hosts within the cluster together with the corresponding status of each onemachine using live migration.
1,798
edits

Navigation menu