Upgrade ERA installed in Failover Cluster in Linux

If you have ERA Server installed in a Failover Cluster environment in Linux and wish to upgrade the installation, proceed with the steps below.

Manual upgrade from version 6.3 to latest version

1.Disable EraService in Conga (Cluster Administration GUI) under Service groups and ensure that ERA Agent and ERA Server are stopped on both nodes.

2.Upgrade ERA Server on node1 by performing the following steps:

oMount the shared storage to this node

oUpgrade ERA Server manually to latest version by executing the .sudo ./server-linux-x86_64.sh command in a Terminal window

oReplace the old cluster script located at /usr/share/cluster/eracluster_server.sh with the new one found in /opt/eset/RemoteAdministrator/Server/setup/eracluster_server. Keep the old file name.

oStop the ERA Server service (stop eraserver) after the upgrade

oDisable ERA Server autostart by renaming the following 2 files:

·mv /etc/init/eraserver.conf /etc/init/eraserver.conf.disabled

·mv /etc/init/eraserver-xvfb.conf /etc/init/eraserver-xvfb.conf.disabled

oUnmount the shared storage from this node

3.Repeat these steps to upgrade ERA Server on node2.

4.Start EraService in Conga (Cluster Administration GUI) under Service groups.

5.Upgrade ERA Agent on all cluster nodes.

6.Check ERA Console to see if all nodes are connecting and show as the latest version.
 

Manual upgrade from version 6.1 or 6.2 to version 6.3

Please note that for older ERA versions the ERA Agent service was running always only on the active node in the failover cluster. Starting with ERA 6.3, the ERA Agent service is running on all nodes all the time. This way all nodes can be monitored by ERA all the time.

Please be aware, that the change described above will cause that during upgrade new computer will be created at least for one of the cluster nodes. If you do not need event history for them, do not forget to manually remove the old computer(s) via ERA Console.

1.Disable EraService in Conga (Cluster Administration GUI) under Service groups and ensure that ERA Agent and ERA Server are stopped on both nodes.

2.Upgrade ERA Server on node1 by performing the following steps:

oMount the shared storage to this node

oUpgrade ERA Server manually to version 6.3 by executing .sudo ./server-linux-x86_64.sh command in a Terminal window

oReplace the old cluster script located at /usr/share/cluster/eracluster_server.sh with the new one found in /opt/eset/RemoteAdministrator/Server/setup/eracluster_server. Keep the old file name.

oStop the ERA Server service (stop eraserver) after the upgrade

oDisable ERA Server autostart by renaming the following 2 files:

·mv /etc/init/eraserver.conf /etc/init/eraserver.conf.disabled

·mv /etc/init/eraserver-xvfb.conf /etc/init/eraserver-xvfb.conf.disabled

oUnmount the shared storage from node1

3.Upgrade ERA Server on node2 by performing the same steps as in previous point 2.

4.Remove old agent from node1 by performing the following steps:

oMount the shared storage to this node

oUninstall old ERA Agent (use the installer script with --uninstall parameter)

oCheck whether your system has the following symbolic links

·/etc/opt/eset -> /usr/share/erag2cluster/etc/opt/eset

·/opt/eset -> /usr/share/erag2cluster/opt/eset

·/var/log/eset -> /usr/share/erag2cluster/var/log/eset

·/var/opt/eset -> /usr/share/erag2cluster/var/opt/eset
 
Command to list symbolic links in directory /etc/opt/:
find /etc/opt/ -maxdepth 1 -type l -ls
 

oIf those symbolic links exist, remove them using the commands below

·unlink /etc/opt/eset

·unlink /opt/eset

·unlink /var/log/eset

·unlink /var/opt/eset

oCreate new symbolic links - for each of them corresponding folder needs to be created first. Use the commands below:
 
 

·mkdir -p /etc/opt/eset/RemoteAdministrator
ln -s /usr/share/erag2cluster/etc/opt/eset/RemoteAdministrator/Server /etc/opt/eset/RemoteAdministrator/Server

·mkdir -p /opt/eset/RemoteAdministrator
ln -s /usr/share/erag2cluster/opt/eset/RemoteAdministrator/Server /opt/eset/RemoteAdministrator/Server

·mkdir -p /var/log/eset/RemoteAdministrator
ln -s /usr/share/erag2cluster/var/log/eset/RemoteAdministrator/Server /var/log/eset/RemoteAdministrator/Server

·mkdir -p /var/opt/eset/RemoteAdministrator
ln -s /usr/share/erag2cluster/var/opt/eset/RemoteAdministrator/Server /var/opt/eset/RemoteAdministrator/Server

oUnmount the shared storage from this node

5.Repeat these steps to remove the old ERA Agent from node2.

6.Start EraService in Conga (Cluster Administration GUI) under Service groups.

7.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!).

8.Check ERA Console to see if all nodes are connecting and show as the latest version.