Thanks to Anti-affinity rules, VMware Fault Tolerant virtual machines are?

Thanks to Anti-affinity rules, VMware Fault Tolerant virtual machines are?

A.
Sometimes located on the same host, but only in a powered off state

B.
Never located on the same host

C.
Sometimes located on the same host if an HA event occurs

D.
Never located within the same cluster

5 Comments on “Thanks to Anti-affinity rules, VMware Fault Tolerant virtual machines are?

  1. Daniel says:

    NOT SURE

    You can use vSphere Fault Tolerance with vSphere Distributed Resource Scheduler (DRS) when the Enhanced vMotion Compatibility (EVC) feature is enabled. This process allows fault tolerant virtual machines to benefit from better initial placement and also to be included in the cluster’s load balancing calculations.

    When a cluster has EVC enabled, DRS makes the initial placement recommendations for fault tolerant virtual machines, moves them during cluster load rebalancing, and allows you to assign a DRS automation level to Primary VMs (the Secondary VM always assumes the same setting as its associated Primary VM.)

    DRS does not place more than a fixed number of Primary or Secondary VMs on a host during initial placement or load balancing. This limit is controlled by the advanced option das.maxftvmsperhost. The default value for this option is 4. However if you set this option to 0, DRS ignores this restriction.

    When vSphere Fault Tolerance is used for virtual machines in a cluster that has EVC disabled, the fault tolerant virtual machines are given DRS automation levels of “disabled”. In such a cluster, each Primary VM is powered on only on its registered host, its Secondary VM is automatically placed, and neither fault tolerant virtual machine is moved for load balancing purposes.

    If you use affinity rules with a pair of fault tolerant virtual machines, a VM-VM affinity rule applies to the Primary VM only, while a VM-Host affinity rule applies to both the Primary VM and its Secondary VM. If a VM-VM affinity rule is set for a Primary VM, DRS attempts to correct any violations that occur after a failover (that is, after the Primary VM effectively moves to a new host).

  2. Abs says:

    I think the correct answer is
    C. Never located on the same host.
    Ref: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_availability.pdf
    Page 32:
    “A fault tolerant virtual machine and its secondary copy are not allowed to run on the same host. Fault Tolerance
    uses anti-affinity rules, which ensure that the two instances of the fault tolerant virtual machine are never on
    the same host. This ensures that a host failure cannot result in the loss of both virtual machines.”

  3. Clay says:

    A is CORRECT

    http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.avail.doc_50/GUID-623812E6-D253-4FBC-B3E1-6FBFDF82ED21.html

    Bottom note:
    The anti-affinity check is performed when the Primary VM is powered on. It is possible that the Primary and Secondary VMs can be on the same host when they are both in a powered-off state. This is normal behavior and when the Primary VM is powered on, the Secondary VM is started on a different host at that time.


Leave a Reply

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