How do I migrate Applications Manager installed in one machine to a different machine?

How do I migrate Applications Manager installed in one machine to a different machine?

For migrating Professional Edition of APM:
  1. In order to migrate APM 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: From the APM web console, navigate to Support tab -> Installation Information).
  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 APM with PGSQL backend, take a backup of the database in your old machine & restore it in the new machine using the steps given here.
  5. For APM with MSSQL backend, you can provide the previously installed MSSQL database details when prompted during the new installation.
    Note: You can find the details of your previously installed MSSQL database in the database_params.conf  file located in the apm/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 MSSQL database.
  6. To move the configuration files, mibs and ssh-keys,
    Run BackupConfig.bat (sh) file in the old server and RestoreConfig.bat (sh) file in the new server. [The files will be present in: <AppManager Home>/bin directory. ] 
  7. 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 &
  8. After starting Applications Manager, apply your original license file.
For migrating Enterprise Edition of APM (Migrating a Managed Server):
  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>
  2. Once you have added the parameters, 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.
For migrating Enterprise Edition of APM (Migrating Admin Server):
  1. To migrate a Admin Server, first install APM as a Admin edition in your new machine.
  2. Follow steps 4, 5 mentioned in the ''For migrating Professional Edition of APM'' section given above.
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 PGSQL backend)



      New to ADManager Plus?

        New to ADSelfService Plus?

        Start your free trial

          • Related Articles

          • Connecting to Applications Manager's bundled database

            Before you connect to Applications Manager's back-end database, it is important that you take a backup of the AppManager directory so that you don't make any changes/accidentally modify the database. 1. Identify which database Applications Manager is ...

          • Self monitor Applications Manager using Real User Monitoring

            We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...

          • Unable to upgrade Applications Manager - MySQL Deprecation

            Problem: You encounter the following error while trying to install service pack for Applications Manager v16140 and above: Reason: This error occurs because MySQL backend database has been deprecated in Applications Manager. Solution: You have to ...

          • How do I migrate the MS SQL DB used by Applications Manager to another MS SQL server?

            Follow the steps given below to migrate MS SQL database of Applications Manager to another MS SQL server: 1. Shutdown Applications Manager completely before the database migration. a. Stop Applications Manager service. b. Shutdown Applications ...

          • How to manually uninstall Applications Manager?

            Windows Shut Down Applications Manager (Ensure that the ManageEngine ApplicationsManager service has been stopped if it has been installed as a Windows service) Open a command prompt with administrator privileges, navigate go to the <Applications ...

            Related Products