Key concepts : HA heartbeat & synchronization : Configuration settings that are not synchronized by HA
 
Configuration settings that are not synchronized by HA
All configuration settings on the active appliance are synchronized to the standby appliance, except the following:
Setting
Explanation
Operation mode
You must set the operation mode of each HA group member before configuring HA. See “Setting the operation mode”.
Host name
The host name distinguishes each member of the FortiWeb HA cluster. See “Changing the FortiWeb appliance’s host name”.
Network interfaces
(reverse proxy or offline protection mode only)
or
Bridge
(true transparent proxy or transparent inspection mode only)
Only the FortiWeb appliance acting as the main appliance, actively scanning web traffic, is configured with IP addresses on its network interfaces (or bridge).
The standby appliance will only use the configured IP addresses if a failover occurs, and the standby appliance therefore must assume the role of the main appliance. See “Configuring the network interfaces” or “Configuring a bridge (V-zone)”.
RAID level
RAID settings are hardware-dependent and determined at boot time by looking at the drives (for software RAID) or the controller (hardware RAID), and are not stored in the system configuration. Therefore, they are not synchronized. See “RAID level & disk statuses”.
HA active status and priority
The HA configuration, which includes Device Priority, is not synchronized because this configuration must be different on the primary and secondary appliances.
See also
Data that is not synchronized by HA
Configuring a high availability (HA) FortiWeb cluster
HA heartbeat & synchronization