Migrated Database - different IP address

The objective of this procedure is to install an entirely new instance of ERA Server and keep your existing ERA database, including existing client computers. The new ERA Server will have a different IP address from the old ERA Server, and the database of the old ERA server will be imported to the new server machine prior to installation.
 

validation-status-icon-warning IMPORTANT: Migrating databases is only supported between identical database types (from MySQL to MySQL or from MSSQL to MSSQL).

validation-status-icon-warning IMPORTANT: When migrating a database, you must migrate between instances of the same ESET Remote Administrator version. For example when you have ERA 6.3.12.0, you can only migrate to ERA version 6.3.12.0. See our Knowledgebase article for instructions to determine the versions of your ERA components. After completing database migration, you can perform an upgrade, if necessary, to get the latest version of ESET Remote Administrator.

 

 On your current (old) ERA Server:

1.Generate a new ERA Server certificate (with connection information for the new ERA 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.

2.Export a server certificate from current ERA Server and save onto your external storage.

oExport all Certification Authority Certificates from your ERA Server and save each CA certificate as a .der file.

oExport Server Certificate from your ERA Server to a .pfx file. Exported .pfx will have private key included as well.

3.Create a policy to define a new ERA 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).

4.Stop the ERA Server service.

5.Export/Backup the ERA Database.

6.Turn off the current ERA Server machine (optional).

validation-status-icon-warning IMPORTANT: Do not uninstall/decomission your old ERA Server yet.

 

On your new ERA Server:

1.Install/Launch a supported ERA database.

2.Import/Restore the ERA database from your old ERA Server.

3.Install ERA 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 ERA Server.

4.Connect to ERA Web Console.

5.Import all CAs exported from your old ERA Server. To do so, follow the instructions for importing a public key.

6.Change your ERA Server certificate in Server settings to use the previous Server certificate from your old ERA Server (exported in step 1.). Do not stop the ERA Server service until step 7.

7.Restart the ERA Server service, see our Knowledgebase article for details.

Client computers should now connect to your new ERA Server using their original ERA Agent certificate, which is being authenticated by the imported CA from the old ERA Server. If clients are not connecting, see Problems after upgrade/migration of ERA Server.

 

Old ERA Server uninstallation:

Once you have everything running correctly on your new ERA Server, carefully decommission your old ERA Server using our step-by-step instructions.