Skip to main content
Hitachi Vantara Knowledge

Advanced features

CautionBefore you use any advanced features, verify that the system is configured correctly and that it can operate with advanced features installed.

vSphere High Availability features

VMware High Availability (HA) monitors all virtualized servers and detects physical server and operating system failures. HA can improve the availability of the virtual SMU and make HNAS deployments more robust.

vSphere Fault Tolerance (FT) provides continuous availability for applications if a server fails.

The main HA and FT configuration options when used with virtual SMUs are as follows:

  • vSphere vMotion® and Storage vMotion®: Provide Manual and automatic migration of compute and storage without service interruption. The three vMotion scenarios are:
    • Host-only migration (with shared storage)Moves VM execution from one host to another.
    • Storage-only migration (single host access to two storage pools)Moves a VM’s disk image from one storage pool to another storage pool.
    • Host and storage migrationA combination of both host and storage migration.

    Risk of losing quorum: none to minimal. However, vMotion does not protect against an ESXi host loss.

  • Cold standby SMU: In an ESXi HA cluster, if the ESXi host running the primary virtual SMU fails, a new instance of the primary virtual SMU starts on another ESXi host. The new instance uses the last updated disk image from the shared storage. Although recovery is fast, it requires starting the VM, which is not fast enough to prevent a quorum loss. If the HNAS cluster is healthy, an SMU HA failover does not affect its availability, but it does prevent access to NAS Manager and the CLI while the new instance of the SMU starts.

    Risk of losing quorum: high to certain.

  • Hot standby SMU: With FT on, a secondary virtual SMU (on a different ESXi host) takes over immediately from a primary virtual SMU if the primary SMU fails. This requires a 10 Gbps FT logging network in addition to the normal network that connects the ESXi hosts and the HNAS nodes. If the SMU serves as a quorum device, the failover should be within the five-second requirement before a quorum loss occurs. In this case, an SMU HA failover can occur without affecting the HNAS cluster, even if one of the HNAS nodes is down.

    Risk of losing quorum: none to minimal.

In summary, HA provides a highly available virtual SMU, but failovers will cause a short-term loss of quorum. FT provides a highly available virtual SMU with a negligible chance of losing quorum.

Guidelines and requirements

Follow these guidelines when you use vSphere High Availability (HA) or Fault Tolerance (FT) to ensure that the system operates correctly.

  • Verify that VMware Tools is installed.
  • Test that vSphere vMotion, HA, or FT configurations are robust and operate correctly.
  • Do not host the virtual SMU on the same HNAS cluster for which the SMU is providing quorum to avoid creating a circular dependency. A quorum loss could prevent access to the SMU's disk image
  • Follow guidelines for CPU and memory allocations. Make sure that the SMU VM always has sufficient resources so that the quorum device is not paused or unresponsive for more than five seconds.
  • Use 10 Gbps for the FT logging network. Do not use 1 Gbps for the FT logging network as doing so will affect the virtual SMU's performance.
  • Use a larger ESXi license when required rather than limit the number of virtual CPUs. FT configurations allow a maximum of two or four virtual CPUs, depending on the ESXi license installed. If you have more than two or four managed entities, verify that operation is sufficient with less than one virtual CPU per managed entity.
  • Set up HA or FT configurations with the vSphere Web Client to receive more informative error messages.

For more information about vSphere High Availability, including features, license options, and pricing, visit: