3. Improved Live Migration
Live Migration was introduced in Windows Server 2008 R2 to provide a
high-availability solution for VMs running on Hyper-V hosts. Live
Migration uses the Failover
Clustering feature to allow running VMs to be moved between cluster
nodes without perceived downtime or loss of network connection. Live
Migration provides the benefit of increased agility by allowing you to
move running VMs to the best host for improving performance, achieving
better scaling, or ensuring optimal workload consolidation. Live
Migration also helps increase productivity and reduce cost by allowing
you to service your host machines without interruption or downtime for
your virtualized workloads.
Live Migration in Windows Server
2008 R2 required storing VMs on an Internet Small Computer Systems
Interface (iSCSI) or Fibre-Channel SAN. In addition, Live Migration in
Windows Server 2008 R2 supported performing only a single Live
Migration at a time—multiple simultaneous Live Migrations were not
supported.
Now Live Migration in Windows Server 2012 has been improved in
several significant ways. First, Live Migrations can be performed much
more quickly. In fact, you can even saturate a 10 GB network connection
when performing a Live Migration between Windows Server 2012 Hyper-V
hosts, something you couldn’t do before with Windows Server 2008 R2
Hyper-V hosts.
A second improvement to Live Migration in Windows Server 2012 is
that now you can perform multiple Live Migrations simultaneously within
the same failover cluster. This means, for example, that if you needed
to take down a particular cluster node for immediate servicing, you can
migrate all running VMs from that node to a different node quickly and
simultaneously in a single operation using either the GUI or a
PowerShell command. This can greatly simplify the task of performing
maintenance on Hyper-V hosts within your environment.
A third improvement is that Live Migration is now possible even if
you don’t have a failover clustering infrastructure deployed. In the
previous version of Windows Server 2008 R2, Live Migration required
installing the Failover Clustering feature, and you also needed to ensure that Cluster Shared
Volume (CSV) storage was enabled to ensure the logical unit number
(LUN) on which your VM is stored could be accessed by any cluster node
at any given time. With Windows Server 2012, however, you have two
additional options for Live Migration that can be performed outside a
failover clustering environment:
-
You can store your VMs on a shared
folder on your network, which lets you live-migrate between
non-clustered Hyper-V hosts while leaving the VM’s files on the share.
-
You also can live-migrate a VM directly from one stand-alone Hyper-V host to another without using any shared storage at all.
Let’s look at these two Live Migration options in a bit more detail.
3.1 Live Migration using a shared folder
With Hyper-V in Windows Server 2012 you can now store all of a VM’s
files on a shared folder on your network provided the shared folder is
located on a file server running Windows Server 2012 (see Figure 6).
The reason the shared folder must be located on a file server running
Windows Server 2012 is because this scenario is supported only through
the new capabilities of version 3 of the server message block (SMB) protocol (SMB
3).
Live Migration using SMB 3 shared
storage does not in itself provide high availability unless the file
share itself is also highly available. It does, however, also provide
the benefit of enhanced VM mobility. And this added mobility can be
achieved without the high costs associated SANs and their associated
switching fabric. SANs also add extra management overhead in the form
of provisioning and managing LUNs. But by simply deploying a Windows
Server 2012 file server, you can centralize storage of the VMs in your
environment without the added cost and management overhead associated
with using a SAN.
Live Migration using SMB 3 shared
storage does have a couple of requirements to get it to work, namely
the permissions on the share must be configured appropriately,
constrained delegation must be enabled in Active Directory directory
service, and the path to the shared
storage must be configured correctly in the VM’s settings. But once
everything is set up properly, the procedure for performing Live
Migration is essentially unchanged from before.