Configuration and Conversion to HA

The StorNext GUI has a menu item for configuring HA: Tools > High Availability > Convert. It automatically inserts the haFsType HaUnmanaged configuration item in every file system configuration, and restarts the FSMs to enable HA. This menu item must be selected separately on each server. It is the operator’s responsibility to ensure that HA is running on both servers; there are no built-in tests to ensure that this has been done. The ha_peer file must be created manually to contain the IP address of the peer MDC, which is used for negotiated restarts of HA timers to avoid unnecessary HA resets.

For more information about using the Convert menu option, see the StorNext online help and Converting to HA.

Each FSM configuration file must be given the haFsType HaUnmanaged configuration item, and the ha_peer file must be given the numerical IP address of its peer, which is used for negotiated restarts of HA timers to avoid unnecessary HA resets.

The FSM configuration files and fsnameservers files must be identical on both servers. When these things are done correctly, HA Monitoring is protecting the metadata against split-brain scenario. It is on by default; there is no means for turning it off other than removing the haFsType item from the FSM configuration files.