Virtual Machine Storage Migration Overview
Applies To: Windows Server 2012 R2, Windows Server 2012
In Windows Server 2008 R2, you can move a running instance of a virtual machine using live migration, but you are not able to move the virtual machine’s storage while the virtual machine is running.
Hyper-V in Windows Server 2012 introduces support for moving virtual machine storage without downtime by making it possible to move the storage while the virtual machine remains running. You can perform this task by using a new wizard in Hyper-V Manager or by using new Hyper-V cmdlets for Windows PowerShell.
You can add storage to either a stand-alone computer or to a Hyper-V cluster, and then move virtual machines to the new storage while the virtual machines continue to run.
The most common reason for moving a virtual machine’s storage is to update the physical storage that is available to Hyper-V. You can also move virtual machine storage between physical storage devices, at run time, to respond to reduced performance that results from bottlenecks in the storage throughput.
Hyper-V in Windows Server 2012 makes it possible to move virtual machine storage while a virtual machine is running.
You need the following to use the Hyper-V functionality of moving virtual machine storage:
One or more installations of Windows Server 2012 with the Hyper-V role installed.
A server that is capable of running Hyper-V. Specifically, it must have processor support for hardware virtualization.
Virtual machines that are configured to use only virtual hard disks for storage.
You cannot move the storage of a virtual machine when any of its storage is directly attached to a physical disk.
This new feature allows you to move the virtual hard disks of a virtual machine while those virtual hard disks remain available for use by the running virtual machine. When you move a running virtual machine’s virtual hard disks, Hyper-V performs the following steps, as shown in Figure 1:
Figure 1 Moving virtual hard disks
Throughout most of the move operation, disk reads and writes go to the source virtual hard disk.
While reads and writes occur on the source virtual hard disk, the disk contents are copied to the new destination virtual hard disk.
After the initial disk copy is complete, disk writes are mirrored to both the source and destination virtual hard disks while outstanding disk changes are replicated.
After the source and destination virtual hard disks are completely synchronized, the virtual machine switches over to using the destination virtual hard disk.
The source virtual hard disk is deleted.