Menu
InformatiWeb Pro
  • Index
  • System admin
  • Virtualization

Login

Registration Password lost ?
FR
  • Windows Server
    • WS2012 R2
    • WS2016
  • Citrix
    • Citrix XenApp / XenDesktop
    • Citrix XenServer
  • VMware
    • VMware ESXi
    • VMware vSphere
    • VMware Workstation
  • Microsoft
    • Hyper-V
  • RAID
    • Adaptec SmartRAID
    • Broadcom MegaRAID
  • UPS
    • APC Back-UPS Pro
  • Firewall
    • pfSense
  • NAS
    • Unraid
  • InformatiWeb Pro
  • Virtualization
  • VMware
  • Courses
  • Learn how to migrate VMs and create clusters on VMware vSphere 6.7
  • Enable vSphere HA on a cluster
16 / 19
  • Enable vSphere FT on a cluster
  • Enable VMCP on a VM in a cluster

Enable vSphere HA on a cluster to ensure high availability of a VMware vSphere 6.7 infrastructure

  • VMware
  • 28 February 2025 at 12:26 UTC
  • InformatiWeb
  • 6/8
Previous page

On your cluster page, you will see several messages appear, including this one.

Plain Text

HA vSphere HA failover in progress.

Since our host "esxi2" is no longer available, vSphere HA has designated our host "esxi1" as master.

As expected, our Windows 10 virtual machine is working again, but on our host "esxi1".

On your cluster, you will see these messages appear:

Plain Text

Insufficient vSphere HA failover resources.
Insufficient resources to satisfy vSphere HA failover level on cluster Cluster_IW cluster in DC-Brussels.

This is due to the fact that vSphere HA will no longer be able to ensure the availability of your VMs in the event of another host failure.

Now, we turn on our host "esxi2" again.

Our host "esxi2" starts.

Our host "esxi2" has started.

After a few minutes, all messages (errors and warnings) will be gone.

As you can see, there is no longer any problem on our cluster.

Neither on our host "esxi1".

However, you will see a message temporarily appear on the host that you have just restarted.

Plain Text

Quick stats on esxi2.informatiweb.lan is not up-to-date.

A few minutes later, this message will automatically disappear.

As expected, your "Win 10 x64 v2004" virtual machine works without problems on the last host where it was located.
In our case, on our host "esxi1".

Next page

Share this tutorial

Partager
Tweet

To see also

  • VMware vSphere 6.7 - Cluster admission control

    VMware 3/5/2025

    VMware vSphere 6.7 - Cluster admission control

  • VMware vSphere 6.7 - Create a cluster

    VMware 2/14/2025

    VMware vSphere 6.7 - Create a cluster

  • VMware vSphere 6.7 - Create a cluster and enable EVC mode

    VMware 2/19/2025

    VMware vSphere 6.7 - Create a cluster and enable EVC mode

  • VMware vSphere 6.7 - Create a datastores cluster and enable SDRS

    VMware 2/12/2025

    VMware vSphere 6.7 - Create a datastores cluster and enable SDRS

Comments

No comment

Share your opinion

Pinned content

  • Software (System admin)
  • Linux softwares
  • Our programs
  • Terms and conditions
  • Share your opinion

Contact

  • Guest book
  • Technical support
  • Contact

® InformatiWeb-Pro.net - InformatiWeb.net 2008-2022 - © Lionel Eppe - All rights reserved.

Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.