HOTSPOT
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
Can’t you do a Storage Migration for the server with an AMD Processor?
The Processor type is just for Live Migration, isn’t it?
Answer is Storage Migration for VM3 and Live Migration for VM6??
Storage Migration Requirements:
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.
http://technet.microsoft.com/en-us/library/hh831656.aspx
Live Migration Requirements:
Requirements
Common requirements for any form of live migration:
Two (or more) servers running Hyper-V that:
Support hardware virtualization.
Use processors from the same manufacturer. For example, all AMD or all Intel.
Belong to either the same Active Directory domain, or to domains that trust each other.
Virtual machines must be configured to use virtual hard disks or virtual Fibre Channel disks (no physical disks). For more information on virtual Fibre Channel, see Hyper-V Virtual Fibre Channel Overview.
Use of an isolated network, physically or through another networking technology such as VLANs, is recommended for live migration network traffic.
http://technet.microsoft.com/en-us/library/hh831435.aspx
The original answer is correct.
You wouldn’t use a storage migration because storage migration is primarily used for updating a VM’s physical storage that is available to the Hyper-V.
You are also not using storage migration to move entire VM’s, just the storage capabilities.
I understand that your comment is from 2014, but just so everyone know, as of now you CAN migrate both VM and storage data using Storage Migration.
original answer is correct
The answer is correct.
For VM3: Answer is “export and import” roles. Can’t do live or storage migration because different processors manufactures.
Quick migration is for Windows Server 2008 and replaced with live migration.
For VM6: Answer is “live migration”. “Export and import” and “storage migration” aren’t the least downtime.
Quick migration is for Windows Server 2008 and replaced with live migration.
http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/management/using-quick-storage-migration-system-center-virtual-machine-manager-2008-r2-.html
My doubt is: question state we add Server 3 “to the network”. we don’t know if Server 3 is domain-joined. Live migration require both hyper-v server to be active directory member. Am I wrong?
I’m afraid Live Migration will not work for VM6 because it’s not a cluster:
http://kunaludapi.blogspot.co.il/2013/01/differance-between-hyperv-live.html
“With HyperV live migration, you can move running VMs from one Hyper-V physical host to another without any disruption of service or perceived downtime. It requires Microsoft Failover Clustering.”
And on the other hand I found this:
https://technet.microsoft.com/en-us/library/hh831435.aspx
Section “Live migration outside of a clustered environment. “
Your dead right with this. Live migration and quick migration options ONLY exist inside a cluster. The correct way to move a Hyper-V is using storage migration. Dont be put off by the name…you CAN move an entire hyper-v using the storage migration feature. It required the “live migration” SETTINGS in hyper-v settings to be configured on both servers, but this is the only way to move an entire hyper-v outside of a failover cluster.
Correct Answer is:
Export / Import
Storage Migration
Wrong Gareth.
See Anat’s link.
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, while the virtual machine’s storage remains on the central SMB share. This allows users to gain the benefits of virtual machine mobility without having to invest in the clustering infrastructure if they do not need guarantees of availability in their environment. (Hyper-V with SMB storage can also be configured with Failover Clustering if you do require high availability. For information about different configurations of Hyper-V with SMB storage, see Deploy Hyper-V over SMB.)
This question is about Processor Compatibility mode as Im sure we have all worked out
IMO what they are trying to discover is if you are aware of the following
1. You can live migrate between processors of exactly the same manufacturer/version with no complications or additional considerations
2. You can live migrate between processors of the same manufacturer but of different versions if you enable Processor Compatibility Mode in Hyper-V settings
3. You cannot live migrate between different processor manufacturers.
4. To migrate/move between different manufacturers (eg Intel>AMD)the VM must go offline during the migration
We must minimise downtime!
VM3 is going from AMD to Intel so the VM must go offline.
Export/Import will work but requires time
Quick Migration Will also work (because the VM briefly goes offline)
Quick Migration meets the requirements of minimising downtime
VM6 is going from Intel to Intel so we can do a Live Migration
The catch is that as we don’t know what Intel processor versions we are migrating between and we may need to consider enabling Processor Compatibility Mode and if this is not already enabled we need to shut down the VM to enable it!!!
Nice one Microsoft 🙂
I guess the take away from it all is that on every VM you build you should enable Processor Compatibility Mode from the outset, just to cover yourself for possible future migrations without having to switch the VM off, just to check one little box in the VM settings.
If anyone can tell us why MS decided to make that check box greyed out when VM is running it would be interesting to know
Answer IMO is VM3 Quick Migration; VM6 Live Migration
“With Quick Migration, a VM is put in a saved state; the VM’s memory information is transferred to another host which then starts the VM. Quick Migration requires shared torage and Windows Server Cluster,”
So I vote :
1. export import
2. live migration
BYZ thanks for pointing that out. I missed the fact that the servers are not members of clusters and agree with you, so
E/I & LM are correct
Agreed. A quick migration will ONLY work when the hosts share the same storage and the VM is moving from one node to another in a cluster. Since this is not referenced in the question, the answer cannot be quick migration.
The answer is correct.
cbt nuggets videos say that the only way to migrate between hosts with different processors is to export & import
Yep. The answer is right.
Apparently quick migration is only in 2008 and needs failover clustering.
https://technet.microsoft.com/en-us/library/dn859550.aspx
Virtual machines cannot be live migrated or saved and restored across virtualization hosts that use processors from different CPU manufacturers. For example, you cannot move running virtual machines or virtual machine saved state from a host with Intel processors to a host with AMD processors. If you must move a virtual machine in this case, the virtual machine must first be shut down, then restarted on the new host.
I would go with:
VM3 = Export/Import
VM6 = Storage Migration
Live migration only works in Cluster. If it were called “shared Nothing live Migration” that would work.
Here an explanation from official 20412D Trainer Handbook:
– Virtual Machine and Storage Migration. With this method, you move a powered-on virtual machine from one location to another or from one host to another by using the Move Virtual Machine Wizard in Hyper-V Manager. Virtual Machine and Storage Migration does not require failover clustering or any other high availability technology.
– Quick Migration. This method also is available in Windows Server 2008. It requires that failover clustering be installed and configured. During the migration process, when you use Quick Migration to move virtual machines between cluster nodes, a virtual machine is placed in a saved state. This causes some downtime until the memory content is copied to another node, and the machine is restored from the saved state.
– Live Migration. This improvement over Quick Migration is also available in Windows Server 2008 R2. It enables you to migrate a virtual machine from one host to another without experiencing downtime. In Windows Server 2012 and Windows Server 2012 R2, you also can perform Shared Nothing Live Migration, which does not require failover clustering. In addition, hosts do not have to share any storage for this type of migration to be performed.
Correct.
The problem that all of you have in common is understanding the actual terms. Here’s a really good article, updated as of 2016. Look at the screenshots and read everything.
http://www.altaro.com/hyper-v/hyper-v-live-migration-methods/
1. Quick Migration:
– Transfer only works from one host to another within the same cluster.
– Requires shared storage and obviously failover clustering
2. Live Migration (2008 R2):
– Transfer of ownership of a “clustered” VM from one node/host to another, provided that the hosts are within the SAME cluster.
3. Shared Nothing Live Migration (starting in Windows Server 2012 and 2012 R2):
– Transfer of VM from one node/host to another, but the VM cannot be clustered. You CAN move the VM to a host that is part of a cluster, but the VM itself should not have a cluster role at the time of the transfer. You can move the VM itself OR both the VM + storage.
4. Storage Live Migration:
– Transfer of one or “more” of a VM’s files. You can move the VM itself OR both the VM + storage. Works for non-clustered VMs as well as clustered VMs.
Question does not mention use of cluster. This rules out Quick Migration and Live Migration for VM6. IF question gave us “Shared Nothing Live Migration”, that would be the best choice. Is the answer then “Storage Migration”? Well, it should really be called “Storage Live Migration” to be exact, but even if it’s not I think that’s still the best answer. You can move not just the VM, but also its storage. This works for non-clustered VMs OR clustered VMs, so it doesn’t matter if the question mentions the use of a cluster or not.
The article that Ricky mentions is very interesting. If you read it slowly and you add the information in the following microsoft article “https://technet.microsoft.com/en-us/library/hh831435.aspx” where are indicated the requirements for live migration in a clustered environments, a storage Shared environment and a without anything shared environment. We can get the following conclusions:
Live Migration: It is possible with and without a cluster and can be done directly from Hyper-V.
Quick Migration: Legacy technology still available for being faster than live migration, but we can avoid using it.
Storage Migration: Only moves storage. It starts from Move – Virtual Machine Storage. But it allows you to select the full VM path in which case it is already a Live Migration.
From Hyper-V we only have the option to Move. We can select to move only storage (Storage Migration) or full MV (Live or Quick migration).
Therefore, being clustered or not is not relevant and the original response is correct.