Failover Cluster

Below are the high-level steps required to install ESET Security Management Center in a Failover Cluster environment.

details_hoverNOTE

See also this Knowledgebase article about cluster installation of ESMC Server.

1.Create a Failover Cluster with a shared disk:

a.Instructions to create a failover cluster in Windows Server 2016 and 2019

b.Instructions to create a failover cluster in Windows Server 2012 and 2012 R2

c.Instructions to create a failover cluster in Windows Server 2008 R2

2. In the Create Cluster Wizard enter the desired hostname (make up one) and IP address.

3.Get the shared disk of the cluster online on node1 and install ESMC Server using the standalone installer on it. Make sure that This is a cluster installation is selected during installation and select the shared disk as application data storage. Make up a hostname and enter it for the Server certificate of ESMC Server next to the pre-filled hostnames. Remember this hostname and use it in step no. 6 when creating the ESMC Server Role in the Cluster Manager.

4.Stop ESMC Server on node1, bring the shared disk of the cluster online on node2 and install ESMC Server using the standalone installer on it. Make sure that This is a cluster installation is selected during installation. Choose the shared disk as application data storage. Keep database connection and certificate information intact, they were configured during installation of ESMC Server on node1.

5.Configure your firewall to allow incoming connections on all ports used by ESMC Server.

6.In the cluster configuration manager create and start a Role (Configure Role > Select Role > Generic service ...) for the ESMC Server service. Select the ESET Security Management Center Server service from the list of available services. It is very important to use the same hostname for the Role as was used in step 3 concerning the Server certificate.

details_hoverNOTE

The term Role is used in Windows Server 2012 and later. In Windows Server 2008 R2, Services and applications is used instead.

7.Install ESET Management Agent on all cluster nodes using the standalone installer. In the Agent configuration and Connection to ESET Security Management Center Server screens use the hostname you used in step no. 6. Store Agent data on the local node (not on the cluster disk).

8.Web server (Apache Tomcat) is not supported on a cluster, therefore it has to be installed on a non-clustered disk or a different machine:

a)Web Console can be easily installed on a separate computer and properly configured to connect to ESMC Server cluster Role.

b)After Web Console is installed, locate its configuration file at: C:\Program Files\Apache Software Foundation\[ Tomcat folder ]\webapps\era\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config\EraWebServerConfig.properties

c)Open the file in Notepad or any other simple text editor. In the line server_address=localhost replace localhost with the IP address or hostname of the ESMC Server cluster Role.