You need to ensure that VM1 remains available from HV1 while drive E is being replaced

Your network contains three servers named HV1, HV2, and Server1 that run Windows Server 2012
R2. HV1 and HV2 have the Hyper-V server role installed. Server1 is a file server that contains 3 TB of
free disk space.
HV1 hosts a virtual machine named VM1. The virtual machine configuration file for VM1 is stored in
D:\VM and the virtual hard disk file is stored in E:\VHD.
You plan to replace drive E with a larger volume.
You need to ensure that VM1 remains available from HV1 while drive E is being replaced. You want
to achieve this goal by using the minimum amount of administrative effort.
What should you do?

Your network contains three servers named HV1, HV2, and Server1 that run Windows Server 2012
R2. HV1 and HV2 have the Hyper-V server role installed. Server1 is a file server that contains 3 TB of
free disk space.
HV1 hosts a virtual machine named VM1. The virtual machine configuration file for VM1 is stored in
D:\VM and the virtual hard disk file is stored in E:\VHD.
You plan to replace drive E with a larger volume.
You need to ensure that VM1 remains available from HV1 while drive E is being replaced. You want
to achieve this goal by using the minimum amount of administrative effort.
What should you do?

A.
Perform a live migration to HV2.

B.
Add HV1 and HV2 as nodes in a failover cluster. Perform a storage migration to HV2.

C.
Add HV1 and HV2 as nodes in a failover cluster. Perform a live migration to HV2.

D.
Perform a storage migration to Server1.

Explanation:
One of the great new features coming in Windows Server 2012 is Storage Migration for Hyper-V.
Storage Migration allows an administrator to relocate the source files that make up a virtual
machine to another location without any downtime.

Storage Migration creates a copy of the file or files at the new location. Once that is finished, Server
2012 does a final replication of changes and then the virtual machine uses the files in the new
location.

Windows Server 2012 Hyper-V – Part 3: Storage Migration

Show Hint

Leave a Reply 2

Your email address will not be published. Required fields are marked *

seven + sixteen =

kurt

kurt

Han says:
December 4, 2014 at 4:38 am
‘Using a minimum amount of adminitrative effort’ is the always key for this type of questions.
They will give multiple possible solutions, but with that key in mind, D is the answer.

A,C is not the answer because VM1 has to remain in HV1
B is possible, but it takes lots of effort to set up cluster.
D seems the best answer. You just do storage migration lively to another server, then bring back when large disk is insert to hot swap bay.

Reply

kurt

kurt

clusters are not least admin effort. so really between A and D. A live migration requires domain joined pcs and can be done outside of a cluster. however D is the answer. live migration has all the options of storage migration.

Reply