EMS HA deployment options
FortiClient EMS supports the following HA setup options with EMS application HA combined with or without PostgreSQL DB HA (see EMS High Availability (HA) concepts):
|
Install scenario |
Description |
|---|---|
|
EMS nodes in HA with Postgres DB HA cluster using EMS PostgreSQL HA Docker, single region |
Install EMS in an HA configuration with the Postgres DB also in an HA configuration using EMS PostgreSQL HA Docker. This install uses five Linux machines: two for the EMS HA nodes, two for the Postgres DB nodes, and one for the witness node. |
|
EMS nodes in HA with Postgres DB HA cluster for geo-redundancy |
Install EMS nodes in a geographically distant HA cluster. Each data center also includes PostgreSQL DB/witness nodes that are part of the same cluster but running in different regions. The setup of a geographically distributed infrastructure allows you to ensure redundancy in case of failure on a data center. |
|
Set up an EMS cluster using two or more EMS VM appliances. Each EMS VM appliance, when deployed, is pre-installed with a local postgresql database which serves the EMS node in the appliance VM host. To set up an EMS VM cluster, all the EMS nodes within the cluster must be configured to use a remote postgresql database installed on none of the VM hosts. |
|
|
Install EMS in an HA configuration with the Postgres DB installed on a remote Linux machine. This install uses three Linux machines: two for the EMS HA nodes and one for the Postgres DB. |
|
|
EMS nodes in HA with Postgres DB HA cluster using native Postgres without Docker, single region |
Install EMS in an HA configuration with the Postgres DB also in an HA configuration without using Docker. This install uses at least five servers: two for the EMS HA nodes and at least three for the Postgres DB/witness nodes. |