Migrate the same version of ESET Remote Administrator from an old server to a new one

Published on 02/22/2015 by Wouter Makkinje

Filed under ESET

Last modified 05/21/2015

Print this page

rate 1 star rate 2 star rate 3 star rate 4 star rate 5 star
Your rating: none, Average: 0 (0 votes)

This article have been viewed 4285 times

How do I migrate the same version of ESET Remote Administrator from an old server to a new one?

KB Solution ID: SOLN2683|Last Revised: January 29, 2014

Warning:

  • Make sure that you have sufficient free disk space and temporary disk space to perform this migration (the migration process requires 3-4 times more free disk space than the actual size of the database). Insufficient disk space is a common cause of migration failure.
  • Do not deactivate the older server until you are sure that your client workstations are communicating with the new server.

To migrate the same version of ESET Remote Administrator from an old server to a new one, complete the following step-by-step process:

  1. Configure ESET Remote Administrator Server to ignore server name mismatches
  2. Perform database cleanup (optional)
  3. Export policies / groups
  4. Back up the old server
  5. Download and install ERAS and ERAC on the new server
  6. Move your client workstations to the new server
  7. Restore saved database onto the new server

 

I. Configure ESET Remote Administrator Server to ignore server name mismatches:

In order to prevent server name mismatches after migration, configure the ESET Remote Administrator Server to ignore server name mismatches by following the steps below:

  1. Open the ESET Remote Administrator Console (ERAC) by double-clicking the ERAC icon on your Desktop, or by clickingStart  All Programs  ESET  ESET Remote Administrator Console  ESET Remote Administrator Console.
  2. Click Tools  Server Options.
  3. Click the Advanced tab, then click Edit Advanced Settings.
  4. In the ESET Configuration Editor, expand Remote Administrator  ERA Server  Settings  Advanced and selectIgnore database server name mismatch.
  5. Select the check box next to Yes / No. Click Console to save your changes.
  6. Click OK to exit the Server Options window. You can now proceed to Part II below (performing database cleanup).

II. Perform database cleanup (optional):

NOTE:

Performing a database cleanup is an optional step that might help to speed up the database import in part VII.

  1. Open the ESET Remote Administrator Console (ERAC) by double-clicking the ERAC icon on your Desktop, or by clickingStart  All Programs  ESET  ESET Remote Administrator Console  ESET Remote Administrator Console.
  2. Click Tools  Server Options  Server Maintenance tab.
  3. In the Cleanup scheduler section, click Clean Up Now, then Yes to confirm the action. Once the clean up is complete, proceed to Part III.

 

III. Export policies / groups

Before continuing, export any policies and groups that you would like to import after migration using the Knowledgebase article below:

IV. Back up the old server:

 

V. Download and install the ESET Remote Administrator Server and Console on the new server:

 

VI. Move your client workstations to the new server:

Configure your client workstations to report to the new server hostname or IP Address. Refer to the following Knowledgebase article for step-by-step instructions :


If migration fails 
due to insufficient disk space, follow the steps below:

  1. Reinstall your version of ESET Remote Administrator.
  2. Restore the database using the ERA Maintenance Tool.
  3. Restore the following directory: C:\Documents and Settings\All Users\Application Data\ESET\ESET Remote Administrator\Server\
  4. Resolve the insufficient disk space issue by ensuring that you are accounting for the increased disk space necessary to perform this migration.
  5. Perform the steps in Part V again.

 

VII. Restore the saved database onto the new server:

    1. On the new server, open the Start Menu and click All Programs  ESET  ESET Remote Administrator Server  ESET Remote Administrator Maintenance Tool.
    1. In the ERA Maintenance Tool window, click Next twice.
    1. In the Maintenance Task section, select Database restore (from an external dump file).

      Figure 1-1

    1. In the Database connection properties section, click Load all settings from file and choose the file you saved when you backed up the old server.
    2. Click Test connection to make sure the connection is functioning properly. Click Next to continue.

      Figure 1-2

    1. In the Dump file window, locate the your saved dump file.
  1. Click Next, then Start to begin restoring the server.

NOTE:

Once you have completed steps 1-7 in part VI, verify that all of your settings have been restored successfully. If the ESET Remote Administrator Server service does not start successfully after migration, verify that it is not due to a server name mismatch issue by examining the following directories:

  • Server 2003, XP: C:\Documents and Settings\All Users\Application Data\ESET\ESET Remote Administrator\Server\logs\era.log
  • SBS 2011, Server 2008, Windows 7: C:\ProgramData\ESET\ESET Remote Administrator\Server\logs\era.log

Repair a server name discrepancy: Run the ERA service with the ‘-server_name_repair’ option from the Windows command prompt.

For example, open a Windows command prompt as an administrator (click Start  All Programs  Accessories. Right-click Command Prompt and choose Run as administrator from the context menu) and enter the following command replacing the path to the ERA service in this example with the path to ‘era.exe’ on your server:

C:\Program Files\ESET\ESET Remote Administrator\Server\era.exe -server_name_repair