ESET PROTECT VA upgrade/migration
|
You can upgrade to ESET PROTECT On-Prem 13.1 from ESET PROTECT On-Prem 11.1 and later. A direct upgrade from the End of Life versions 8.x–11.0 has not been tested and is not supported. |
Perform the following to upgrade or migrate your VA:
•Upgrade—Install a later version of ESET PROTECT components.
•Migration—Move the ESET PROTECT Virtual Appliance to another Virtual Appliance of the same version.
•Migration and upgrade—Move the ESET PROTECT Virtual Appliance to another Virtual Appliance of the later version.
There are two ways of upgrading your VA:
•Using the database pull—Upgrades the Appliance, including the underlying operating system, not just the ESET PROTECT Server. The process is complex and requires running two concurrent appliances during the transition period. We recommend using the database pull to upgrade to the major versions or for troubleshooting.
•Upgrading via Components Upgrade task in the Web Console—The process is simpler and does not require access to the appliance, only to the Web Console. We recommend this procedure for minor and hotfix upgrades. Components upgrade does not upgrade the underlying operating system or other packages needed for proper functioning of ESET PROTECT Server.
Migration and upgrade process (recommended way to upgrade)
|
Before the migration Back up your database and export Certification Authority and Peer Certificates from your old ESET PROTECT VA before migrating or upgrading the ESET PROTECT Server. If your old ESET PROTECT VA does not use advanced security and has SHA-1 certificates, follow these steps before the migration in your old ESET PROTECT VA to prevent the failed login in the new VA: 1.Enable the advanced security. 2.Follow the certificate replacement steps. |
|
ESET PROTECT On-Prem Mobile Device Management (MDM) reached the End of Life. To manage mobile devices, migrate to cloud-based ESET PROTECT. |
Follow these instructions to migrate from the earlier VA to the latest VA (including the migration from CentOS to Rocky Linux).
1.Download the latest protect_appliance.ova (or protect_appliance.vhdx.zip if you use Microsoft Hyper-V).
2.Deploy a new ESET PROTECT VA. See ESET PROTECT Virtual Appliance deployment process for instructions. Do not configure the new ESET PROTECT VA via its web interface.
3.Pull the database from your old VA.
|
Do not uninstall/decommission your old VA Server. |
4.Configure ESET PROTECT Virtual Appliance via its web interface.
5.Verify the new ESET PROTECT VA behaves like the old one:
If the new ESET PROTECT VA has a different IP address:
If the new ESET PROTECT VA has the same IP address:
6.Upgrade a ESET Management Agents sample group using an ESET PROTECT Components Upgrade task.
|
Do not include the ESET Management Agent running on the ESET PROTECT VA in the sample because the Agent upgrade causes a temporary connection loss to ESET PROTECT, making the server appear corrupted. |
7.If the sample upgrade is successful and Agents are still connecting, continue with the rest of the Agents.
Upgrade process (an alternative way to upgrade)
|
Upgrading to the latest ESET PROTECT On-Prem on the same VA does not upgrade other VA software (operating system, packages needed for proper functioning of ESET PROTECT Server). We recommend that you migrate the server after a clean upgrade. |
Upgrade the VA using a Components Upgrade task:
1.Upgrade the ESET PROTECT Server first.
2.Upgrade a ESET Management Agents sample group.
3.If the sample upgrade is successful and Agents are still connecting, continue with the rest of the Agents.