The no host for secondary VM alarm shows that VMware Fault Tolerance cannot find a compatible host to place a secondary VM for mission-critical or data-intensive Oracle VMware or SQL Server VMware applications.
VMware Fault Tolerance (FT) is a feature providing guest redundancy for most mission-critical applications that cannot tolerate data loss or interruption of service. This feature can be enabled on any virtual machine that resides in an HA cluster.
When VMware Fault Tolerance (FT) is enabled on a primary VM, a secondary VM is created on a different host in the cluster. This allows the secondary VM to run in virtual lockstep with the primary VM. The following events are triggered when a failure occurs:
- A transparent failover takes place in which the secondary VM continues execution from the exact point where the primary left off.
- The secondary VM becomes the new primary VM.
- A new secondary virtual machine is started on another host.
During this failover, there is no data loss or noticeable service interruption.
Note:VMware Fault tolerance can only be enabled on VMs that meet specified Fault Tolerance requirements.
Confio IgniteVM helps identify the impact of the no host for secondary VM alarm for sites running Oracle on VMware, SQL Server on VMware, and other virtual databases. IgniteVM helps DBAs maintain performance and availability on virtual servers. IgniteVM is the only virtualization-aware database monitoring solution.
Learn more about IgniteVM solutions for: