Hotspot Question
Your network contains an Active Directory domain named contoso.com.
The domain contains two member servers named Server1 and Server2. All servers run Windows
Server 2012 R2. Server1 and Server2 have the Hyper-V server role installed.
The servers are configured as shown in the following table.
You add a third server named Server3 to the network. Server3 has Intel processors.
You need to move VM3 and VM6 to Server3.
The solution must minimize downtime on the virtual machines.
Which method should you use to move each virtual machine? To answer, select the appropriate
method for each virtual machine in the answer area.
Answer: 
Explanation:
VM3: export/import is the only option due to different processor manufacturers
VM6: Live migration can be used as both have Intel CPU’s Live Storage Migration requires same
processor manufacturers Live migration requires same same processor manufacturers Quick
migration has downtime
http://technet.microsoft.com/en-us/library/dd446679(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/hh831656.aspx
http://technet.microsoft.com/en-us/library/jj628158.aspx
Live migration is for failover clustering, same for quick migration.
The question doesn’t say anything about clustering, nor about shared storage. So, I think that the correct answer for VM6 is storage migration. You can have storage migration, although you don’t have a failover clustering feature in place.
Storage migration is also a “live migration” without clustering.
http://blogs.technet.com/b/uspartner_ts2team/archive/2012/07/23/storage-live-migration-on-windows-server-2012.aspx
1
0
You can’t perform a storage migration to another machine. Storage migration is for moving the VHDs of the VM to either another folder/volume on the same host or to shared storage. The VM will still be running on the original system.
Live motion, however, will move the vm and it’s files to another host. Live motion in a cluster leaves the VHD in the same spot (CSV) but changes the host running the VM. With two nodes in a stand alone config, live motion moves everything.
http://www.jamesbannanit.com/wp-content/uploads/2012/03/SVR8-LM-0002-300×224.png
0
0
WRONG, on so many levels. It’s not Live “motion”, it’s Live “migration”. The term “motion” is used by VMWare (i.e VMotion).
Furthermore, you CAN move VM + storage or just the VM itself using Storage Migration. Storage Migration does not require failover clustering, but it works for both non-clustered VMs as well as clustered VMs.
0
0
I Agree, It should be storage migration
1
0
According to this clusters are NOT required for live migrations.
https://www.petri.com/windows-server-2012-hyper-v-live-migration
0
0
Watcher is right since newer versions of Hyper-V include Live Migration as you can see in this image
https://4sysops.com/wp-content/uploads/2015/06/Live-migration-settings-in-Hyper-V-2012-R2.png
(Before, Live Migration was only found in Failover Cluster Manager).
This question states that both servers have Hyper-V server role only (Not Failover Cluster) so both answers are right VM3 E/I – VM6 LM
0
0
“Live migration outside of a clustered environment.
In Windows Server 2012, you can configure a virtual machine so that it is stored on an SMB file share. You can then perform a live migration on this running virtual machine between non-clustered servers running Hyper-V”
Can’t argue with that. From technet article hh831435
0
0
The “Live Migration” vs “Storage Migration” debate here and on http://www.aiotestking.com/microsoft/which-method-should-you-use-to-move-each-virtual-machine-2/ seems to depend on whether Shared Nothing Live Migration is regarded as a feature of Live Migration or a separate kind of migration. Those who say it’s separate are going for Storage Migration.
It seems to me that it’s a feature of Live Migration, so I’m going VM3 E/I – VM6 LM like Starlin.
From https://technet.microsoft.com/en-us/library/hh831435(v=ws.11).aspx
You can also perform a live migration of a virtual machine between two non-clustered servers running Hyper-V when you are only using local storage for the virtual machine. (This is sometimes referred to as a “shared nothing” live migration.
0
0