asked on

Hyper V on Server 2016

Hello,

I am trying to simulate a replacement of VMware ESX on Hyper V running on server 2016.
In my lab, I have two physical servers with the hyper V role installed, the failover cluster manager role and the Hyper V replica broker role. Storage is presented via iSCSI target on Qnap NAS.

Here are my questions.
How do I configure the DRS function? What allows that function?
I attempted to configure Replication, and I received an error that I could not replicate virtual machine to the same cluster.
Suggestions Please

Muhammad Burhan

review previous post related to your question,
https://www.experts-exchange.com/questions/28413814/Hyper-V-Replica-Vs-Hyper-V-cluster.html

furthermore, configure Replica Broker properly to perform all the functions smoothly,
http://fixmyitsystem.com/2014/03/C2Creplica.html

ASKER CERTIFIED SOLUTION

Philip Elder

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Luciano Patrão

Hi,

What are you trying to replicate or use DRS? In your Nested VMware?? Or in your physical Hyper-V?

Because there a big difference.

Jail

stressedout2004

ASKER

I'm trying to understand how to use Hyper V in place of VMware. I don not understand hyper V.

I have Cluster Shared Volumes created.

I am creating VM's in the Fail Over Cluster Manager.

I want to simulate pulling the plug on a cluster node named Hyperv743-01 and see the VMs turn back on the second cluster Node named HyperV743-02. What direction do I need to look in.

SOLUTION

Luciano Patrão

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Philip Elder

Pull the plug(s) on the node. It should work as long as storage is set up identically on both nodes and the virtual switch(es) are named identically on both nodes.

stressedout2004

ASKER

Storage is the same and virtual switches are the same.
I pulled the NIC cable and the VM whet to a status of Unmonitored. The Node I disconnected shows a status of isolated.

stressedout2004

ASKER

it worked Philip, I had to wait for the time out on the cluster Quorum which is 15 minutes.

Philip Elder

In Server 2016 "Node Flapping" is the status with Isolated Mode being the measure taken. Yes, there is a time-out before the node is considered "Offline" and the VMs fail over. If the node goes isolated but the VMs remain online then whatever the outage is needs to be addressed to allow that node back into the cluster.

stressedout2004

ASKER

I added some notes doe this look true?\

When you add Hyper V nodes to a failover cluster, this creates the High Availability for any hosts assigned to the cluster. You can control how soon the Cluster restarts a hosts by using the properties of the Cluster Disk For Quorum Disk. By default, if a node stops and does not resume after 15 minutes, the failed hosts will be restarted on the surviving nodes in the cluster.
Cluster-Disk.png

Philip Elder

This article explains the feature and how to tweak its settings: Virtual Machine Compute Resiliency in Windows Server 2016. Resiliency Period is the setting and quarantine settings.

stressedout2004

ASKER

thank you