Hi everybody,
Sorry for long winded post, I tried to put as much as info as possible for better understanding
We are trying to achieve following:
SET UP:
Cluster has 4 ESXI hosts, ESX1,ESXi2,ESXi3, ESXi4.
Cluster is enabled for DRS and HA.
Cluster has two VMS:
VM1, FT protected, Primary is on ESXi1, Secondary is on ESXi2
VM2, FT protected, Primary is on ESXi1, Secondary is on ESXi2
We are trying to achieve following:
1) If either VM1 or VM2 ( primary goes down), then both Secondary VMS on ESXi2 should take up the role of Primary.
For above, I am thinking to set up VM heart beats , if master host misses heart beats from either of them, reboot the hosts, this will force Secondary VMS on ESXi2 to assume Primary roles
2) The new secondary VMS must be powered on ESX3 or ESXI 4 . They have be to be together .
I have been looking into affinity rules.
Using vSphere DRS Groups and VM-Host Affinity Rules with MSCS Virtual Machines
You must use VM-Host affinity rules because vSphere HA does not obey VM-VM affinity rules. This means that if a host fails, vSphere HA might separate clustered virtual machines that are meant to stay together, or vSphere HA might put clustered virtual machines that are meant to stay apart on the same host. You can avoid this problem by setting up DRS groups and using VM-Host affinity rules, which are obeyed by vSphere HA.
3)Does FT obey VM-HOST affinity rule?
If yes, then I should be able to following:
Create VM-HOST affinity rules.
VM1, VM2 -VM GRP1
ESXI1- HOST GRP1
ESXI2- HOSTGRP2
ESXI3-HOSTGRP3
ESXI4-HOST GRP4
Then creates VM host affinity rules:
1)VMGRP1 must run HOSTGRP1
2) VM GRP1 must run HOST GRP2
3) VM GRP1 must run HOST GRP3
4) VM GRP1 must run on HOST GRP4
My understanding is the rules above are checked in the order by DRS, HA
Any feedback is appreciated !!