ESET Online Help

Search English
Select the topic

Upgrading via ESET Cluster

Creating an ESET Cluster lets you upgrade multiple servers using earlier versions of ESET Mail Security. We recommend using the ESET Cluster method if you have 2 or more servers with ESET Mail Security in your environment. Another benefit of this upgrade method is that you can continue using the ESET Cluster in so the configuration of ESET Mail Security will be synchronized on all member nodes.

Follow the steps below to upgrade using this method:

1.Log on to one of the servers running ESET Mail Security and upgrade it by downloading and installing the latest version over your existing one. Follow the steps for regular installation. All of the original configuration of your old ESET Mail Security will be preserved during the installation.

2.Run the ESET Cluster wizard and add cluster nodes (servers you want to upgrade ESET Mail Security on). If required, you can add other servers that do not run ESET Mail Security yet (an installation will be performed on these). We recommend that you to leave the default settings in place when specifying your Cluster name and install type (make sure Push license to nodes without activated product is selected).

3.Review the Nodes check log screen. It will list servers with earlier product versions and that the product will be reinstalled. ESET Mail Security will also be installed on any added servers where it is not currently installed.

cluster_older_version

4.The Nodes install and cluster activation screen will display installation progress. When installation is successfully completed, it should finish with results similar to these:

cluster_install_log_perfect

If your network or DNS is not configured correctly, you may receive the error message Failed to obtain activation token from the server. Try running the ESET Cluster wizard again. It will destroy the cluster and create a new one (without reinstalling the product) and activation should finish successfully this time. If the issue persists, check your network and DNS settings.

cluster_failed_token