I am in the process of a new 4 host cluster install.
HA is enabled and I can successfully use vmotion on the 2 test images I have on the cluster.
I can also enable FT and startup the images but only if the HA enforce option is OFF. If it is ON then the secondary FT fails to start and actually complains about not being able to vmotion which was odd.
Once the images are up and running I can move either the primary or secondary to different hosts with vmotion with no problems at all.
Is there any way to set anti-affinity rules to ensure that the secondary FT gets created on a different host.
We are using the advanced license so don't have DRS / DPM and as such if try to set the rules in there it doesn't let us.
please see the script to acomplish the task-http://vmprofessional.com/2009/06/drs-and-anti-affinity-rules.html
please award points if you see fit.Thanks