Fortinet 107 FortiWeb 5.0 Patch 6 Administration Guide
See also
•Updating firmware on an HA pair
•SNMP traps & queries
•HA heartbeat & synchronization
•How HA chooses the active appliance
•Configuration settings that are not synchronized by HA
•Fail-to-wire for power loss/reboots
•Topologies for high availability (HA) clustering
•Replicating the configuration without FortiWeb HA (external HA)
Replicating the configuration without FortiWeb HA (external HA)Configuration synchronization provides the ability to duplicate the configuration from another
FortiWeb appliance without using FortiWeb high availability (HA). The synchronization is
unilateral push: it is not a bilateral synchronization. It adds any missing items, and overwrites
any items that are identically named, but does not delete unique items on the target FortiWeb,
nor does it pull items from the target to the initiating FortiWeb.
Replicating the configuration can be useful in some scenarios where you cannot use, or do not
want, FortiWeb HA:
•External active-active HA (load balancing) could be provided by the firewall, the router, or
an HTTP-aware load balancer, since active-active HA is not provided by FortiWeb itself.
•External active-passive HA (failover) could be provided by a specialized failover device,
instead of the FortiWebs themselves, for network load distribution, latency, and performance
optimization reasons. The failover device must monitor for live routes.
•Multiple identical non-HA FortiWeb appliances in physically distant locations with the
same network scheme might be required to have the same (maybe with a few extra different)
server policies, and therefore management could be simplified by configuring one FortiWeb
and then replicating that to the others.
In such cases, you may be able to save time and preserve your existing network topology by
synchronizing a FortiWeb appliance’s configuration with another FortiWeb. This way, you do not
need to individually configure each one, and do not need to use FortiWeb HA.