Pull database from other server

This feature allows you to pull the ESET PROTECT database from an existing ESET PROTECT VA running in your infrastructure. It is only supported on the ESET PROTECT Server, not on the other components (MDM, ERA Proxy 6.x). It is convenient when upgrading your ERA/ESMC VA to the latest ESET PROTECT VA, or if you want to migrate your ESET PROTECT VA.



In case of migration, you need to keep your old ESET PROTECT VA accessible in order for the hostname/IP address change policy to apply to all client computers. Otherwise, clients will not be connecting to your new ESET PROTECT VA and keep trying to connect to the old one.

Make sure that SSH is enabled on your old ESET PROTECT VA.

A database pull can only be performed when moving to a newer version or the same version of ESET PROTECT server. During the pull procedure, the database structure is updated but this process will fail when pulling to an older server. Database pull is one of two ways how to upgrade your VA.

To perform a database pull, follow the steps below:

1.Deploy a new ESET PROTECT VA, but do not configure it yet.

2.Open the VM's console and on the main screen, press Enter on your keyboard to Enter management mode of your newly deployed ESET PROTECT VA.

3.Type eraadmin and press Enter twice to login.


4.Select Pull database from other server using the arrow keys and press Enter.


5.Enter database root password on the remote ESET PROTECT VA you want to pull the ESET PROTECT database from (your old ESET PROTECT VA). If you are only using one password on your old ESET PROTECT VA, type it here.

6.Enter connection to remote ESET PROTECT VA (SSH) - type user name (root) and your old ESET PROTECT VA host name or IP address in the following format: root@IPaddress or root@hostname

7.If you are asked about The authenticity of host, type yes. Otherwise, ignore this step.

8.Type the VM password of your old ESET PROTECT VA and press Enter. The message Remote ERA Server database was backed up will be displayed when backup operations are completed.



The amount of time needed for backup and restore operations to complete will vary depending on database size.

9.Type the VM password of your old ESET PROTECT VA again. You might be asked to enter the password multiple times during copying, depending on time takes to copy the database.

10. Wait until the database is restored.


11. If you are performing an upgrade: After a successful ESET PROTECT database pull, shutdown old ESET PROTECT VA to decommission it.



We recommend that you keep your old ESET PROTECT VA long enough before you verify that the new instance is functioning properly.

We strongly recommend that you do not uninstall the old ESET PROTECT VA Server using an uninstallation script. This will dissociate (remove) all licenses from the new ESET PROTECT VA Server database as well. To prevent this behavior, delete the old ESET PROTECT VA Server database (DROP DATABASE) before the uninstallation.

12. Configure your new appliance:

Upgrade - configure your new VA exactly the same as your previous ESET PROTECT VA.

Migration - change configuration to suit a new domain (configure or rejoin domain) or network properties, for example, if you have moved your ESET PROTECT VA to a different network.



Make sure all data is preserved, all clients are connecting to your new server and your ESET PROTECT VA behaves the same way as the previous one.