Migrating Professional Edition of Applications Manager

1. In order to migrate Applications Manager and its contents to a new machine, you need to ensure that the version of Applications Manager you install in the new machine matches that of the old machine. (To know details about the build number in your old machine, navigate to Settings tab -> Support-> Installation Information from the Applications Manager console).
   
2. Perform the installation as per the guidelines. Then, start the Applications Manager service in the new machine. Verify if all default monitors exist, and then stop the service.
   
3. Before migrating, stop Applications Manager in your old machine:
   
1. For Windows:
   Open Command prompt with administrator permission.
   Navigate to <ApplicationsManager_Home> folder.
   Run the command: shutdownApplicationsManager.bat -force.
2. For Linux:
   Open Command prompt with administrator permission.
   Navigate to <ApplicationsManager_Home> folder.
   Run the command: sh shutdownApplicationsManager.sh -force
4. For Applications Manager with PostgreSQL backend, take a backup of the database in your old machine & restore it in the new machine using the steps given here.
5. For Applications Manager with MS SQL backend, you can provide the previously installed MS SQL database details when prompted during the new installation. You can find the details of your previously-installed MS SQL database in the database_params.conf  file located under the <ApplicationsManager_Home>/working/conf/ directory. Here is a sample screenshot of the file's contents:
   
   where, 
   localhost represents the name of the host in which MSSQL db is installed,
   1433 represents the port number, and
   AMDB represents the name of the MS SQL database.
6. If you had recently applied a patch to rectify any issue in Applications Manager, we recommend that you move the patch files in working/classes/com and working/WEB-INF/classes directory into the same path in the new installation.
7. To move the configuration files, mibs and ssh-keys, execute the BackupConfig.bat (sh) file in the old server and RestoreConfig.bat (sh) file in the new server. [The files will be present under <Applications Manager Home>/bin directory. ] 
   
8. Start the new Applications Manager service.
   For windows:
   Open services.msc.
   Start the ManageEngine Applications Manager service.
   For Linux:
   Open the terminal.
   Navigate to the directory in which you've installed Applications Manager and run the below command:
   nohup sh startApplicationsManager.sh &
   Note: If you're using Applications Manager v16140 and above, run the below command instead: 
   sh startApplicationsManager.sh -d
   
9. After starting Applications Manager, apply your original license file.

Migrating Enterprise Edition of Applications Manager

1. To migrate a Managed Server, first install APM as a professional edition in your new machine and delete the <AppManager_Home>/conf/install.txt file and add the below mentioned changes in AMServer.properties file:
   
1. Open AMServer.properties file under <AppManager_Home>/conf/ directory in your old Managed server.
   
2. Copy the below parameters & add them to the AMServer.properties file in your new installation.
   am.server.type=MAS
   am.server.startresidrange=<serverid x 10000000> (For example in first Managed server startresidrange will be 10000000 , in second Managed server startresidrange will be 20000000 & so on)
   am.adminserver.host=<Admin Server HostName>
   am.adminserver.port=<Admin Server SSL Port>
3. If you had recently applied a patch to rectify any issue in Applications Manager, we recommend that you move the patch files in working/classes/com and working/WEB-INF/classes directory into the same path in the new installation.
2. Once you complete the above mentioned steps, start the Applications Manager service in the new machine.
   
3. Open APM's admin console and click on the Managed Server tab. A list of all Managed servers will be displayed. Click on edit option for the Managed server that you are migrating to a new machine and update the hostname and IP address of the same.
   

NOTES:

1. There should be no date and time difference between the two hosts as it may affect reports & alarms.
   
2. Migration will work for moving data between:
   
1. Linux to Linux
   
2. Windows to Windows
   
3. Linux to Windows
   
4. Windows to Linux (only with PostgreSQL backend)

Migrating configuration data

1. Execute BackupPGSQL.bat/.sh --confiles command to take config file backup.
   
2. Execute BackupPGSQL.bat/.sh --configtables command to take config table backup.
   
3. Restore the backups by executing below command by replacing <backupFile> file with configuration files backup:
   RestorePGSQL.bat/sh <backupFile>
4. Once the restoration is complete, execute the RestorePGSQL.bat/.sh command with configuration tables backup file:
   RestorePGSQL.bat/sh <backupFile>

Note: In Enterprise Edition, backup of report or configuration data (like --reports, --configtables, --exclude-reports, --exclude-raw) taken from one server should not be restored in another server.