Pull database from other server

This feature allows you to pull the ERA database from an existing ERA VA running in your infrastructure. It is convenient when upgrading your ERA VA to the latest version, or if you want to migrate your ERA VA. To perform database pull, follow the steps below:

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

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

validation-status-icon-warning IMPORTANT

Type eraadmin and press Enter twice to login.

pull_db_login

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

pull_db

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

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

icon_details_hoverNOTE

If the migration from ERA 6.2 to 6.4 fails in this point, use only IPaddress instead of root@IPaddress.

6.Type yes  if you are asked about The authenticity of host, otherwise ignore this step.

7.Type the VM password of your old ERA VA and press Enter.

pull_db_interactive

The message Remote ERA Server database was backed up will be displayed when backup operations are finished.

icon_details_hoverNOTE

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

8.Type the VM password of your old ERA VA again. You might be asked to enter the password multiple times during copying. This depends on how long it takes to copy the database, especially if it is large.

9.Wait until the database is restored.

10. If you are doing Upgrade, after a successful ERA database pull, shutdown old ERA VA to decommission it. However, we recommend that you preserve  your old ERA VA long enough to verify that the new instance is functioning properly, after which the old instance can be deleted.

validation-status-icon-warning IMPORTANT

In case of migration, you need to keep your old ERA 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 ERA VA and keep trying to connect to the old one.

11. Configure your new appliance, configuration will vary based on your reason for migration, for example, in case of:

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

Migration - change configuration to suite a new domain or network properties, for example if you've moved your ERA VA to a different network.

icon_details_hoverNOTE

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