You have a datacenter that contains six servers. Each server has the Hyper-V server role
installed and runs Windows Server 2012 R2. The servers are configured as shown in the
following table.
Host4 and Host5 are part of a cluster named Cluster1. Cluster1 hosts a virtual machine
named VM1.
You need to move VM1 to another Hyper-V host. The solution must minimize the downtime
of VM1.
To which server and by which method should you move VM1?
A.
To Host3 by using a storage migration
B.
To Host6 by using a storage migration
C.
To Host2 by using a live migration
D.
To Host1 by using a quick migration
Explanation:
The migration of a virtual machine between physical computers is only supported on
computers that have the same processor steppings or are from the same vendor. Therefore
you cannot move a virtual machine from a Hyper-V host on an Intel-based server to a HyperV Host on an AMD-based server.
Ref: http://technet.microsoft.com/en-us/library/ee849855(v=WS.10).aspx
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.
Ref: http://technet.microsoft.com/en-us/library/hh831656.aspx
Quick Migration saves, moves and restores VMs, which results in some downtime.
Ref: http://technet.microsoft.com/en-us/library/jj628158.aspx
Windows Server 2008 R2 & Microsoft Hyper-V Server 2008 R2 – Hyper-V Live Migration
Overview & Architecture (http://www.microsoft.com/en-us/download/details.aspx?id=12601 )
Why not D ?
Storage migration doesn’t change VM host, so IMHO D is correct answer.
It does…you can select to just move the VHDs or to move the whole hyper-V.
Live migration and quick migration are selections only available inside a failover cluster, so C and D arent valid options. answer B is the wrong proccessor type.
Sorry Gareth but you are mistaken… Live/Quick/Move migration can take place from cluster to cluster, cluster to host, host to cluster, host to host.
The only difference is where you initiate the migration. If the source vm is a (node) cluster, you use cluster manager, if the source vm is on a host you have to use hyper-v manager. Or you can do it using powershell as well. (move-vm)
https://technet.microsoft.com/en-us/library/jj628158.aspx
https://technet.microsoft.com/en-us/library/hh831435.aspx
https://technet.microsoft.com/en-us/library/dn641214.aspx
According to the linked documentation, quick migration can only occur between other cluster nodes, apparently, and the only ones the question indicates are clustered are Host3 and Host4. I’d say the answer is A because none of the others are doable.
Quick migration—This type of migration is also known as cluster transfer, and can be used to migrate a highly available virtual machine. It leverages Windows Failover Cluster to migrate virtual machines between cluster nodes. The running state of the virtual machine is saved to disk (the virtual machine is hibernated), the disk is failed over to the other cluster node, and then the saved state is loaded to wake up the virtual machine. Downtime is minimal because quick migration takes a snapshot of the virtual machine and transfers data without requiring the virtual machine to be turned off.
Sorry, the clustered machines are Host4 and Host5, not 3 and 4…
Tell the correct option plzzzz A or D ????
FFS Hassan go study a bit.
I put Money that he has failed this exam atleast twice since posting all these requests for correct answers… Some people just can’t hack it…
I passed first time, dipshit
Hassan you have absolutely no room to talk. I wish we could ban you because you never have anything to contribute. If you had passed the first time you wouldn’t be here looking for answers on a test you had already passed you lying cuck.
Also, quick migration requires shared storage, which Host1 does not have. The answer has to be A.
This article gives a good overview: https://www.simple-talk.com/sysadmin/virtualization/hyper-v-migration-technologies/
After reading this I don’t think any of these answers are correct because, as others have said, just moving storage does not change where the VM is hosted. Ideally, if “shared nothing live migration” is an option on the test, I’d select that. Otherwise I would go with A, because we know live migration isn’t possible due to processor discrepancies and the fact that there is no shared storage and they aren’t in a cluster together, and quick migration isn’t possible because it requires shared storage and for the machines to be in a cluster together. Of the possible choices I really think A is the best fit.
A is correct answer because Host3, Host4 & Host5 has same type of processor i.e. Intel.
Just to be clear, IMHO
1)Storage migration is not VM migration! It migrates just the storage! So the A,B is surely wrong
2)You can’t use Live migration, or migrate at all to Host2, because of processor difference.
3)That leave us with quick migration to Host1, that will have some downtime, but it’s the onle doable option
Agreed
Must be D. Check out live migration outside a clustered environment. For my understanding, quick migration is a live migration of a saved state VM.
you can move the whole hyper-v using the storage migration feature…you can select to just move the VHDs or to move the whole hyper-V.
Live migration and quick migration are selections only available inside a failover cluster, so C and D arent valid options. answer B is the wrong proccessor type.
A. Host3 is the only option to allow minimum downtime and has same processor manufacturers
B. Storage Migration requires same processor manufacturers
C. Live migration requires same same processor manufacturers
D. Quick migration has downtime
Don’t mistake quick and live migration. D could be a good answer but has a downtime.
A is correct.
Many people here seem to forget Storage Migration is NOT a VM Migration. Options A and B would still have the VM in the RAM of one of the cluster nodes. Migrating a VM means both the running kernel AND the storage, so A and B are not viable options.
C would be the best option, but LIVE migrations between Intel and AMD CPU’s is not possible.
Which leaves D. While not a perfect option due to the incurred downtime, it does achieve the goal of migrating the ENTIRE VM, which is what was asked, and has no technical impossibilities.
You are wrong. you CAN migrate the whole hyper-V using the storage migration feature.
You can select to just move the VHDs or to move the whole hyper-V.
Live migration and quick migration are selections only available inside a failover cluster, so C and D arent valid options. answer B is the wrong proccessor type.
You can migrate “the whole hyper-v” stuff, except for the current machine state, meaning its ownership. A is only half the solution, but it’s still the only one doable.
After re-re-re-reading question, I think correct option is A.
https://technet.microsoft.com/en-us/library/hh831656.aspx:
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.
This discards B and D (different proccessor manufacturer, local storage), C is discard because different proccessor dont let live migration. Only leaves A option.
Found this in the following article: https://technet.microsoft.com/en-us/library/hh831656.aspx
“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”
This would suggest to me that the answer is A, although storage migration does not move the WHOLE
none of the answers are right but i would go with A.
hosts 2 & 6 cannot be used as they have a different processor which rules out B & C.
according to transcenders ‘Quick migration requires that you have failover clustering installed.’ Hosts 1, 2 and 6 aren’t part of a cluster which rules out D.
This leaves A but storage migration is used to move storage, not VM’s.
Answer A is the right answer, and storage migration part of the solution. You must move storage as well as the VM itself. Option D is not doable because Host 1 is not part of a cluster, so quick migration cannot be performed. The other options are also discarded due to processor not being compatible.
The answer is D. In Server 2012 R2 you can migrate vm’s to hosts with local hard drives. Storage migration will move only VM files and not the VM. VM will remain on its host. So the only option here is to quick migrate it to host 1.
The given Answer A is correct.
Quick Migration only works in cluster.
Please read in the official trainer handbook page 453.
• 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.
A becuase live migration only use csv as it uses cluster.
“You can also use storage migration to move, service, or upgrade storage resources, or for migration of a standalone or cluster virtual machine”
https://technet.microsoft.com/en-us/library/jj628158(v=sc.12).aspx
Should be A.
Why it cannot be D
With this in mind the question says: “The solution must minimize the downtime
of VM1.”
“The disadvantage of Quick Migration is that the VM is briefly brought offline during the migration process”. Page 63 Exam Ref 70-412
Dolittle
I’m kinda pissed at this question. “You need to move VM1 […]”
Move in what way? Migrate it? Move the storage? Both?
IMO the only option is to do a quick migration if they want to change the host, even though it will imply downtime. If they want to move the storage then yes, the obvious answer is A.
While A can indeed migrate the VM components to another host, I’m pretty sure that it won’t change the ownership, meaning that it will still run on the initial node. Storage migration is not VM migration
A is correct.
Neither live migration nor quick migration is supported between hosts with processors from different manufacturers. Microsoft Exam Ref Guide 70-412 chapter 1 page 67
First introduced in Windows Server 2008, Quick Migration is still an available option when you choose to move a clustered VM in Windows Server 2012 from one node to another. Quick Migration saves the VM state and resumes the machine on the destination node. The advantage of Quick Migration is that it is a faster process from start to finish for the VM you are migrating and it requires less network bandwidth. The disadvantage of Quick Migration is that the VM is briefly brought offline during the migration process. If minimizing downtime is not a priority and you want to transfer a VM as quickly as possible, then Quick Migration is the best option. Microsoft Exam Ref Guide 70-412 chapter 1 page 63
B. Has an AMD
C. Has an AMD
D. Goes offline during migration
to avoid confusion. D will work, but the solution is to minimize downtime. With option A, there is no downtime and the VM is moved.
You cannot made storage migration to a disk not connected to the same host. Storage migration are not possible. Quick migration can be done outside the cluster. So, te only working option is D.
Toni you are wrong, Quick Migration occurs within the confines of a cluster.
lucasdrums took the words from my finger tips!
I will be answering A in the exam tomorrow and I will report back
We’re still waiting for your response….
Folks, as stated: “You need to MOVE VM1 to another Hyper-V HOST. The solution must MINIMIZE the downtime of VM1.”
Technet Migrating Virtual Machines and Storage Overview says about storage migration: “Quick storage migration allows you to move virtual machine STORAGE from one location to another.”
– Nothing there about migrating the VM to another HOST! It can’t be A.
Here’s whats in the section about Quick Migration: “This type of migration is also known as cluster transfer, and can be used to migrate a highly available virtual machine.”(…) “Downtime is minimal because quick migration takes a snapshot of the virtual machine and transfers data without requiring the virtual machine to be turned off.”
– Nothing against moving from iSCSI to local storage, and, it states that the downtime is minimal