Migrated Database - same/different IP address
The objective of this procedure is to install an entirely new instance of ESET PROTECT Server and keep your existing ESET PROTECT database, including existing client computers. The new ESET PROTECT Server will have the same or different IP address, and the database of the old ESET PROTECT Server will be imported to the new server machine before installation.
|
•Migrating databases is only supported between identical database types (from MySQL to MySQL or from Microsoft SQL to Microsoft SQL). •When migrating a database, we recommend migrating between instances of the same ESET PROTECT On-Prem version. See our Knowledgebase article for instructions to determine the versions of your ESET PROTECT components. After completing database migration, you can perform an upgrade, if necessary, to get the latest version of ESET PROTECT On-Prem. |
I. On your current (old) ESET PROTECT Server:
|
We recommend the migration to a different IP address for advanced users only. If your new ESET PROTECT Server has a different IP address, perform these additional steps on your current (old) ESET PROTECT Server: a)Generate a new ESET PROTECT Server certificate with connection information for the new ESET PROTECT Server. Leave the default value (an asterisk) in the Host field to allow for distribution of this certificate with no association to a specific DNS name or IP address. b)Create a policy to define a new ESET PROTECT Server IP address and assign it to all computers. Wait for the policy to be distributed to all client computers (computers will stop reporting in as they receive the new server information). |
1.Stop the ESET PROTECT Server service.
2.Export/Back up the ESET PROTECT database.
3.Turn off the current ESET PROTECT Server machine (optional if the new server has a different IP address).
|
Do not uninstall/decommission your old ESET PROTECT Server yet. |
II. On your new ESET PROTECT Server:
|
To use a new ESET PROTECT Server with the same IP address, ensure the network configuration on your new ESET PROTECT Server (IP address, FQDN, Computer name, DNS SRV record) matches that of your old ESET PROTECT Server. |
|
ESET PROTECT Mobile Device Management/Connector (MDM/MDC) component (on-premises only) reached End of Life in January 2024. ESET PROTECT On-Prem versions 11.1 and later do not support mobile device management. |
1.Install/Launch a supported ESET PROTECT database.
2.Import/Restore the ESET PROTECT database from your old ESET PROTECT Server.
3.Install ESET PROTECT Server using the All-in-one package installer (Windows) or choose another installation method (Windows manual installation, Linux or Virtual Appliance). Specify your database connection settings during installation of ESET PROTECT Server.
4.Connect to ESET PROTECT Web Console.
5.Navigate to More > Settings > Connection. Click Change certificate > Open certificate list and select the Server certificate of the old ESET PROTECT Server and click OK twice.
6.Restart the ESET PROTECT Server service.
7.Log in to ESET PROTECT Web Console and click Computers.
After one or two Agent connection intervals, client computers should connect to your new ESET PROTECT Server using their original ESET Management Agent certificate. If clients are not connecting, see Problems after upgrade/migration of ESET PROTECT Server.
III. Old ESET PROTECT Server uninstallation:
When you have everything running correctly on your new ESET PROTECT Server, carefully decommission your old ESET PROTECT Server using our step-by-step instructions.