Configuring system settings : Using high availability (HA) : Configuring the HA mode and group : Configuring the primary HA options
Configuring the primary HA options
Go to System > High Availability > Configuration and click the arrow to expand the HA configuration section, if needed. The options presented vary greatly depending on your choice in the Mode of operation drop-down-list.
 
Table 32: HA main options
GUI item
Description
Mode of operation
Enables or disables HA, selects active-passive or config-only HA, and selects the initial configured role this FortiMail unit in the HA group.
off: The FortiMail unit is not operating in HA mode.
master: The FortiMail unit is the primary unit in an active-passive HA group.
slave: The FortiMail unit is the secondary unit in an active-passive HA group.
config master: The FortiMail unit is the primary unit in a config-only HA group.
config slave: The FortiMail unit is a secondary unit in a config-only HA group.
Caution: For config-only HA, if the FortiMail unit is operating in server mode, you must store mail data externally, on a NAS server. Failure to store mail data externally could result in mailboxes and other data scattered over multiple FortiMail units. For details on configuring NAS, see “Storing mail data on a NAS server” and “Selecting the mail data storage location”
On failure
Select one of the following behaviors of the primary unit when it detects a failure, such as on a power failure or from service/interface monitoring.
switch off: Do not process email or join the HA group until you manually select the effective operating mode (see “click HERE to restart the HA system” and “click HERE to restore configured operating mode”).
wait for recovery then restore original role: On recovery, the failed primary unit‘s effective HA mode of operation resumes its configured master role. This also means that the secondary unit needs to give back the master role to the primary unit. This behavior may be useful if the cause of failure is temporary and rare, but may cause problems if the cause of failure is permanent or persistent.
wait for recovery then restore slave role: On recovery, the failed primary unit’s effective HA mode of operation becomes slave, and the secondary unit continue to assume the master role. The primary unit then synchronizes the content of its MTA queue directories with the current master unit. The new master unit can then deliver email that existed in the former primary unit’s MTA queue at the time of the failover. For information on manually restoring the FortiMail unit to acting in its configured HA mode of operation, see “click HERE to restore configured operating mode”.
In most cases, you should select the wait for recovery then restore slave role option.
For details on the effects of this option on the Effective Operating Mode, see Table . For information on configuring service/interface monitoring, see “Configuring service-based failover”.
This option appears only if “Mode of operation” is master.
Shared password
Enter an HA password for the HA group. You must configure the same Shared password value on both the primary and secondary units.