-Vhds @(@{ "SourceFilePath " = "C:\vm\vhd1.vhdx ";
"DestinationFilePath " = "D:\VHDs\vhd1.vhdx "}, @{ "SourceFilePath " = "C:\vm\vhd2.vhdx ";
"DestinationFilePath " = "E:\VHDs\vhd2..vhdx "}, @{ "SourceFilePath " = "C:\vm\vhd3.vhdx ";
"DestinationFilePath " = "F:\VHDs\vhd3.vhdx "})
Once the storage migration is initiated, it will run until it’s finished; it will never give
up, no matter how long it may take. As the administrator, you can cancel the storage
migration manually through the Cancel move storage action. Rebooting the Hyper-V
host would also cause all storage migrations to be cancelled. You can see the progress
of storage migrations in the Hyper-V Manager tool or you can query them through
WMI, as shown here:
PS C:\ > Get‐WmiObject ‐Namespace root\virtualization\v2 `
-Class Msvm_MigrationJob |
ft Name, JobStatus, PercentComplete, VirtualSystemName
Name JobStatus PercentComplete VirtualSystemName
—— ————- ———————-————————-
Moving Storage Job is running 14 6A7C0DEF-9805-...
Shared Nothing Live Migration
With the existing Live Migration technology and the new ability to move the storage
of a virtual machine with no downtime, Windows Server 2012 introduced Shared
Nothing Live Migration. This feature allows you to move virtual machines between
any two Windows Server 2012 Hyper-V hosts with no downtime and no shared
resource. This means no shared storage, no shared cluster membership; all that is
needed is a gigabit network connection between the Windows Server 2012 Hyper-V
hosts. With this network connection, a virtual machine can be moved between Hyper-
V hosts, which includes moving the virtual machine’s virtual hard disks, the virtual
machine’s memory content, and then the processor and device state with no
downtime to the virtual machine. Do not think that the Shared Nothing Live
Migration capability means Failover Clustering is no longer needed. Failover
Clustering provides a high availability solution, while Shared Nothing Live Migration
is a mobility solution but does give new flexibility in the planned movement of virtual
machines between all Hyper-V hosts in your environment without downtime. It can
supplement Failover Cluster usage. Think of now being able to move virtual machines
into a cluster, out of a cluster, and between clusters with no downtime to the virtual
machine in addition to moving them between stand-alone hosts. Any storage
dependencies are removed with Shared Nothing Live Migration.
Failover Clustering provides some assurance that the hosts in a failover cluster have a
similar configuration as long as it passed validation. This provides a confident
migration of virtual machines between hosts without the fear of misconfigurations
and therefore problems with virtual machines functioning if migrated. When Shared
Nothing Live Migration is used to migrate virtual machines between unclustered
Hyper-V hosts, there is no guarantee of common configuration, and therefore you