You need to ensure that you can start VM1 on Server1 if Server2 fails

Your network contains two servers named Server1 and Server2 that run Windows Server 2012
R2. Both servers have the Hyper-V server role installed. Server1 and Server2 are located in
different offices. The offices connect to each other by using a high-latency WAN link.
Server2 hosts a virtual machine named VM1.
You need to ensure that you can start VM1 on Server1 if Server2 fails.
The solution must minimize hardware costs.
What should you do?

Your network contains two servers named Server1 and Server2 that run Windows Server 2012
R2. Both servers have the Hyper-V server role installed. Server1 and Server2 are located in
different offices. The offices connect to each other by using a high-latency WAN link.
Server2 hosts a virtual machine named VM1.
You need to ensure that you can start VM1 on Server1 if Server2 fails.
The solution must minimize hardware costs.
What should you do?

A.
On Server1, install the Multipath I/O (MPIO) feature.
Modify the storage location of the VHDs for VM1.

B.
From the Hyper-V Settings of Server2, modify the Replication Configuration settings.
Enable replication for VM1.

C.
On Server2, install the Multipath I/O (MPIO) feature.
Modify the storage location of the VHDs for VM1.

D.
From the Hyper-V Settings of Server1, modify the Replication Configuration settings.
Enable replication for VM1.

Explanation:
You first have to enable replication on the Replica server–Server1–by going to the server and
modifying the “Replication Configuration” settings under Hyper-V settings.
You then go to VM1– which presides on Server2– and run the “Enable Replication” wizard on
VM1.



Leave a Reply 3

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


sysadmin

sysadmin

correct. the source host needs to have replication enabled for the PARTICULAR VM. the target host needs to have its Hyper-v settings modified.

qwe

qwe

Gotta remember that: hyper-v settings = target, vm settings = source