Failover Cluster—Windows
Below are the high-level steps required to install ESET PROTECT On-Prem in a Failover Cluster environment.
|
•The cluster setup of the database on Windows environments is supported only for the Microsoft SQL Server, not for MySQL/MariaDB. •See also this Knowledgebase article about cluster installation of ESET PROTECT Server. |
1.Create a Failover Cluster with a shared disk.
2.Click Start > Failover Cluster Manager > right-click Failover Cluster Manager > Create Cluster. In the wizard, select both nodes and type the desired Cluster Name (make up one) and IP address.
|
Remember the cluster name—you will use it as a hostname in the following steps. |
3.Get the shared disk of the cluster online on the first node and install ESET PROTECT Server using the standalone installer on it. Ensure that This is cluster installation is selected during installation, and select the shared disk as application data storage. Type the hostname (created in step two) for the Server certificate of ESET PROTECT Server next to the pre-filled hostnames.
4.Stop ESET PROTECT Server on the first node, bring the shared disk of the cluster online on the second node and install ESET PROTECT Server using the standalone installer on it. Ensure that This is cluster installation is selected during installation. Choose the shared disk as application data storage. Keep the database connection and certificate information intact; they were configured during the ESET PROTECT Server installation on the first node.
5.Configure your firewall to allow incoming connections on all ports used by ESET PROTECT Server.
6.Create and start a role for the ESET PROTECT Server service: In the Failover Cluster Manager, click Roles > Next. In Select Role, click Generic Service > Next. Select the ESET PROTECT Server service from the list of available services and click Next. Type the Name (Use the same hostname for the role as in step two), select the network, type the IP Address and complete the wizard.
7.Web server (Apache Tomcat) is not supported on a cluster. Therefore, you must install it on a non-clustered disk or a different machine:
a.Install the Web Console on a separate computer and configure it properly to connect to ESET PROTECT Server cluster role.
b.After Web Console is installed, stop the Apache Tomcat service.
c.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
d.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 ESET PROTECT Server cluster role.
e.Start the Apache Tomcat service.
8.Open the ESET PROTECT Web Console in a supported web browser; a login screen will be displayed (substitute IP_ADDRESS_OR_HOSTNAME with the IP address or hostname of your ESET PROTECT Web Console):
Open the Web Console: |
Login screen link (All-in-one installation) |
Login screen link (manual installation) |
|---|---|---|
From the computer hosting the ESET PROTECT Web Console |
https://localhost |
http://localhost:8080/era |
From any computer with internet access to the ESET PROTECT Web Console |
https://IP_ADDRESS_OR_HOSTNAME |
http://IP_ADDRESS_OR_HOSTNAME:8080/era |
9.Install the ESET Management Agent on each cluster node. You have several options:
•Using the Agent standalone installer—In the Agent configuration screen, use the same hostname as in steps two and three. You can export the Agent certificate and a Certification Authority via the ESET PROTECT Web Console. Select the local node (not the cluster disk) as the Agent installation folder.
•Using the Agent installer created in the ESET PROTECT Web Console. In the installer creation wizard, use the same hostname as in steps two and three.