Deploying SSFE in High Availability will require two servers. These are:
- Primary (Appliance1)
- Secondary (Appliance2)
This is always the first server to be installed. During installation, the Primary server must be selected at the prompt. Configuration and testing is done on the Primary server before setting up the Secondary server.
The Secondary server is installed after the Primary server has been configured and verified working. During installation, the Secondary server can be selected at the prompt. After installation, there is no configuration needed to set up the Secondary server. All settings are replicated from the Primary server during the setup process.
Both the Primary and Secondary servers require two network interface controllers (NICs). The first NIC must be connected to the production network. It is used for communication with SSFE clients and apps. The second NIC must be connected to a private switch. It is used for replication between the two servers.
Both NIC's must be connected to the right switch during installation.
Load Balancing and High Availability
Load balancing and high availability is achieved by using either a Network Load Balancer (NLB) or by implementing a Domain Name System (DNS) load balance.
The NLB requires third-party hardware and/or software and the configuration will depend on the type of NLB used. Then the required DNS records for SSFE will need to point to the NLB's IP address.
DNS load balance means setting up the required DNS records for SSFE and pointing them to the production IP address of both the Primary and Secondary servers. This means each FQDN will resolve two IP addresses.
The required DNS records for SSFE are:
SSFE_Domain refers to the Domain Name setting configured in the Administration Web Console > Administration > System Settings > Domain Name section of the SSFE console.