Failover Cluster - Linux

The following refers to ESET Remote Administrator installation and configuration on a Red Hat high-availability cluster.

Linux Cluster Support

ESET Remote Administrator Server or ERA Proxy components can be installed on Red Hat Linux 6 cluster and higher. Failover Cluster is only supported in active/passive mode with the cluster manager rgmanager.

Prerequisites

Active/passive cluster must be installed and configured. Only one node can be active at a time, other nodes must be on standby. Load balancing is not supported.

Shared storage - iSCSI SAN, NFS and other solutions are supported (any technology or protocol which provides block based or file based access to shared storage, and makes the shared devices appear like locally attached devices to the operating system). Shared storage must be accessible from each active node in the cluster, and the shared file system must be properly initialized (for example, using the EXT3 or EXT4 file system).

The following HA add-ons are required for system management:

orgmanager

oConga

rgmanager is the traditional Red Hat HA cluster stack. It is a mandatory component.

The Conga GUI is optional. The Failover Cluster can be managed without it, however we recommend that you install it for best performance. In this guide we assume that it is installed.

Fencing must be properly configured in order to prevent data corruption. The cluster administrator must configure fencing if it is not already configured.

If you do not already have a cluster running, you can use the following guide to set up a high-availability Failover Cluster (active/passive) on Red Hat: Red Hat Enterprise Linux 6 Cluster Administration.

Scope

ESET Remote Administrator components that can be installed on a Red Hat Linux HA cluster:

ERA Server with ERA Agent

ERA Proxy with ERA Agent

validation-status-icon-infoNOTE: ERA Agent must be installed, otherwise the ERA cluster service will not run.

validation-status-icon-infoNOTE: Installation of the ERA Database or ERA Web Console on a cluster is not supported.

The following installation example is for a 2-node cluster. However, you can install ESET Remote Administrator on a multi-node cluster using this example as a reference only. The cluster nodes in this example are named node1 and node2.

Installation steps

1.Install ERA Server or ERA Proxy on node1.

oPlease note that the hostname in the Server or Proxy certificate must contain the external IP (or hostname) of the cluster’s interface (not local IP or hostname of the node).

 

2.Stop and disable the ERA Server (or ERA Proxy) Linux services using the following commands:

service eraserver stop
chkconfig eraserver off
 

3.Mount shared storage to node1. In this example, the shared storage is mounted to /usr/share/erag2cluster.

4.In /usr/share/erag2cluster, create the following directories:

/usr/share/erag2cluster/etc/opt/eset/RemoteAdministrator/Server
/usr/share/erag2cluster/opt/eset/RemoteAdministrator/Server
/usr/share/erag2cluster/var/log/eset/RemoteAdministrator/Server
/usr/share/erag2cluster/var/opt/eset/RemoteAdministrator/Server

5.Move recursively the following directories to the destinations shown below (source > destination):

Move folder:

Move to:

/etc/opt/eset/RemoteAdministrator/Server

/usr/share/erag2cluster/etc/opt/eset/RemoteAdministrator

/opt/eset/RemoteAdministrator/Server

/usr/share/erag2cluster/opt/eset/RemoteAdministrator

/var/log/eset/RemoteAdministrator/Server

/usr/share/erag2cluster/var/log/eset/RemoteAdministrator

/var/opt/eset/RemoteAdministrator/Server

/usr/share/erag2cluster/var/opt/eset/RemoteAdministrator

6.Create symbolic links (this may require to create new folders manually):
 
ln -s /usr/share/erag2cluster/etc/opt/eset/RemoteAdministrator/Server /etc/opt/eset/RemoteAdministrator/Server
ln -s /usr/share/erag2cluster/opt/eset/RemoteAdministrator/Server /opt/eset/RemoteAdministrator/Server
ln -s /usr/share/erag2cluster/var/log/eset/RemoteAdministrator/Server /var/log/eset/RemoteAdministrator/Server
ln -s /usr/share/erag2cluster/var/opt/eset/RemoteAdministrator/Server /var/opt/eset/RemoteAdministrator/Server

7.Copy the eracluster_server (eracluster_proxy) script found in the setup directory of ERA Server or ERA Proxy to /usr/share/cluster. The scripts do not use the.sh extension in the setup directory.

cp /opt/eset/RemoteAdministrator/Server/setup/eracluster_server /usr/share/cluster/eracluster_server.sh

8.Unmount the shared storage from node1

9.Mount the shared storage to the same directory on node2 as you mounted to on node1 (/usr/share/erag2cluster).

10.On node2, create the following symbolic links:
 
ln -s /usr/share/erag2cluster/etc/opt/eset/RemoteAdministrator/Server /etc/opt/eset/RemoteAdministrator/Server
ln -s /usr/share/erag2cluster/opt/eset/RemoteAdministrator/Server /opt/eset/RemoteAdministrator/Server
ln -s /usr/share/erag2cluster/var/log/eset/RemoteAdministrator/Server /var/log/eset/RemoteAdministrator/Server
ln -s /usr/share/erag2cluster/var/opt/eset/RemoteAdministrator/Server /var/opt/eset/RemoteAdministrator/Server

11. Copy the eracluster_server or (eracluster_proxy) script found in the setup director of ERA Server or ERA Proxy to /usr/share/cluster. The scripts do not use the .sh extension in the setup directory.

cp /opt/eset/RemoteAdministrator/Server/setup/eracluster_server /usr/share/cluster/eracluster_server.sh

The next steps are performed in Conga Cluster Administration GUI:

12. Create a Service Group, for example EraService.

The ESET Remote Administrator cluster service requires three resources: IP address, file system and script.

13. Create the necessary service resources.

Add an IP address (external cluster address where Agents will connect), file system and Script resources.

The file system resource should point to the shared storage.

The mount point of the file system resource should be set to /usr/share/erag2cluster.

The “Full Path to Script File” parameter of the Script resource should be set to /usr/share/cluster/eracluster_server (or /usr/share/cluster/eracluster_proxy).

14. Add the above resources to the EraService group.

After the Server cluster is successfully set up, install ERA Agent on both nodes on the local disk (not on the shared cluster disk). When using the --hostname= command, you must specify the external IP address or hostname of the cluster's interface (not localhost!).