Follow these steps to configure a High Availability (HA) system on Windows:
- Install StorNext if not already installed (see Install the StorNext File System on a Windows MDC: Interactively).
- Obtain and install StorNext licenses, which must include at least Maintenance, Server and Failover licenses for both MDCs (see Obtain and Install StorNext Licenses – GUI-based Appliances and Customer-supplied MDCs).
- If this is an existing configuration with clients, it is recommended that you stop StorNext services on all StorNext clients to avoid the clients hanging (see Configure a StorNext File System on Windows).
- Verify that configuration files are correct and identical on both MDCs.
- The *.cfg files should be identical on both computers.
- The fsnameservers files should be identical on both computers.
- The fsmlist files should be identical on both computers.
- If the optional
ha_smith_intervalfile is configured, it must be identical on both computers (for more details, see High Availability Systems).
- Copy and paste the *.cfg files and fsmlist files from the primary MDC to the secondary MDC before proceeding to Step 5.
- Create the ha_peer file in the configuration directory of each MDC (C:\Program Files\StorNext\config\ha_peer). The ha_peer file on each MDC must contain the numerical IP address of its redundant-peer MDC, which enables intra-MDC communication for HA functionality.
Enable High Availability (HA) on both redundant-peer MDCs by doing the following:
Caution: If you do not perform these steps on both MDCs your metadata could become corrupted.
After installing StorNext, on each MDC run Start > All Programs > StorNext > File System Cfg (Advanced). The File System Configuration window displays.
- On the Tools menu, click HA Configuration.
- Click Enable High Availability (HA). Note that you cannot enable HA if there are no file systems configured.
High Availability is now configured. You may now test the HA reset functionality by running the following command on either MDC:cvadmin -e "hamon smith"
The MDC will immediately reboot. Clients for any StorNext file systems that were being served by active FSMs on the reset MDC will trigger elections that will result in the activations of corresponding FSMs on the redundant HA MDC. This can be observed by running the following command on the redundant MDC both before and after resetting its peer MDC:cvadmin –e "select"
Restart services on any clients that you stopped earlier (see Configure a StorNext File System on Windows).
Note: Restarting StorNext faster than once per three minutes can trigger a startup delay of three minutes. The delay slows down looping HA resets so that an administrator can correct any configuration problems that are causing the resets.