OpManager Enterprise Edition - A guide to migration and backup

Learn how to migrate your database, about backup & restore, and the steps to enable HTTPS in OpManager version 12300 and above.

When should you migrate?

  • When hardware, server OS, or SQL requirements have been changed.
  • When you need new servers for space and better performance.
  • If you need to migrate products to a dedicated server.
  • When adding a new database or new server type.

Migrating Central and Probe from one server to another server

For PostgreSQL

Steps to migrate Central from one server to another:

  1. Stop OpManagerCentral service. Execute 'OpManagerService.bat -r' under the OpManagerCentral/bin directory to remove the OpManagerCentral service in the existing machine.
  2. Take a compressed backup of the entire OpManagerCentral folder.
  3. Extract the folder to the new system where Central is about to be installed.
  4. Open command prompt with administrator privileges in the machine where Central needs to be installed.
  5. Go to the OpManagerCentral/bin directory in the new machine and execute 'initPgsql.bat' to give access permission for the database from the new server.
  6. In the same command prompt, execute ‘OpManagerService.bat’ to add OpManagerCentral as a service.
  7. Start OpManagerCentral from Windows services in the new machine.
  8. To update Central details for the new machine:
    1. If the new system's IP address or host name differs from that of the existing machine, go to "OpManagerProbe/conf/OpManager" directory, locate “NOCServerDetail.xml” file and update the "NOCServerName" attribute value with the new server name.
    2. If the IP address and host name of the new machine is the same as that of the existing machine, the 'NOCServerName' need not be updated.
  9. Restart all the probes.
  10. To clean up the existing machine, uninstall OpManagerCentral.

Steps to migrate Probe from one server to another:

  1. Stop OpManagerProbe service. Execute 'OpManagerService.bat -r' under the OpManagerProbe/bin directory to remove the OpManagerProbe service in the existing machine.
  2. Take a compressed backup of the entire OpManagerProbe folder.
  3. Extract the folder to the new system where the probe is about to be installed.
  4. Open command prompt with administrator privileges in the machine where Central needs to be installed.
  5. Go to the OpManagerProbe/bin directory in the new machine and execute 'initPgsql.bat' to give access permission for the database from the new server.
  6. In the same command prompt, execute 'OpManagerService.bat' to add OpManagerProbe as a service.
  7. Start OpManagerProbe from Windows services in the new machine
  8. To update probe details for the new machine:
    1. If the new system's IP address or host name differs from that of the existing machine, go to Settings --> Configuration --> Probe Details. Click on the probe name to modify the probe and update NAT Name detail for the probe which has been moved.
    2. If the IP address and host name of the new machine is the same as that of the existing machine, the NAT name need not be updated.
  9. To clean up the existing machine, uninstall OpManagerProbe.

For MSSQL:

Case 1: To move only the installation without moving the database.

Case 2: To move both the database and the installed machine.

Case 1: To move only the installation without moving the database

In Central:

  1. Stop OpManagerCentral Service. Execute 'OpManagerService.bat -r' under the OpManagerCentral/bin directory to remove the OpManagerCentral service in the existing machine.
  2. Take a compressed backup of the entire OpManagerCentral folder.
  3. Extract the folder to the new system where the Central is about to be installed.
  4. If you want to use the same database, continue without any changes. Please ensure that the database server is reachable in the new machine.
  5. To update Central details for the new machine:
    1. If the new system's IP address or host name differs from that of the existing machine, go to "OpManagerProbe/conf/OpManager" directory, locate "NOCServerDetail.xml" file and update the "NOCServerName" attribute value with the new server name.
    2. If the IP address and host name of the new machine is the same as that of the existing machine, the 'NOCServerName' need not be updated.
  6. Restart all the probes.
  7. To clean up the existing machine, uninstall OpManagerCentral.

In Probe:

  1. Stop OpManagerProbe Service. Execute 'OpManagerService.bat -r' under the OpManagerProbe/bin directory to remove the OpManagerProbe service in the existing machine.
  2. Take a compressed backup of the entire OpManagerProbe folder.
  3. Extract the folder to the new system where the Probe is about to be installed.
  4. If you want to use the same database, continue without any changes. Please ensure that the database server is reachable in the new machine.
  5. To update probe details for the new machine:
    1. If the new system's IP address or host name differs from that of the existing machine, go to Settings --> Configuration --> Probe Details. Click on the probe name to modify the probe and update NAT Name detail for the probe which has been moved.
    2. If the IP address and host name of the new machine is the same as that of the existing machine, the NAT name need not be updated.
  6. Start OpManagerProbe from Windows services in the new machine.
  7. To clean up the existing machine, uninstall OpManagerProbe.

Case 2: To move both the database and the installed machine

It is not recommended to move the database from one Server Studio to another. Contact opmanager-support@manageengine.com for further assistance.

Data Backup and Restoration

Moving installation from one server to another using backup and restore

Steps to migrate Central :

  1. Stop the OpManagerCentral service and take a backup using the steps given in this page.
  2. Stop all the probes to avoid loss of data.
  3. Do a new, clean installation of Central in the required server.
  4. Follow the steps given in this page to restore the data.
  5. Start OpManagerCentral.
  6. To update Central details for the new machine:
    1. If the new system's IP address or host name differs from that of the existing machine, go to "OpManagerProbe/conf/OpManager" directory, locate "NOCServerDetail.xml" file and update the "NOCServerName" attribute value with the new server name.
    2. If the IP address and host name of the new machine is the same as that of the existing machine, the 'NOCServerName' need not be updated.
  7. Restart all the probes.
  8. To clean up the existing machine, uninstall OpManagerCentral.

Steps to migrate Probe:

  1. Stop the OpManagerProbe service and take a backup using the steps given in this page.
  2. Do a new, clean installation of the probe in the required server.
  3. After the probe is installed successfully, start the service and check if the probe is communicating properly with the central.
  4. Stop the newly installed probe.
  5. Follow the steps given in this page to restore the data.
  6. Start the OpManagerProbe.
  7. In Central, go to 'Probe Details' page and verify that the status of the old probe is displayed as "Running" and the status of new probe is displayed as "Server Down".
  8. Delete the new probe (*Do not delete the old probe*).
  9. To update probe details for the new machine:
    1. If the new system's IP address or host name differs from that of the existing machine, go to Settings --> Configuration --> Probe Details. Click on the probe name to modify the probe and update NAT Name detail for the probe which has been moved.
    2. If the IP address and host name of the new machine is the same as that of the existing machine, the NAT name need not be updated.
  10. 10. To clean up the existing machine, uninstall OpManagerProbe.

Steps to Migrate OpManager Standalone to Enterprise Edition

  1. Upgrade existing OpManager Standalone setup to OpManager Version 123278 or above.
  2. After upgrading to version 123278, take a backup using the steps given in this page.
  3. Do a new clean installation of Central Server in a separate machine.
  4. In OpManager Standalone, execute the batch file "MigrateToEnterprise.bat" under OpManager/bin with arguments as given below.
  5. After migration is completed in Standalone, Central server will automatically shutdown after few seconds.

MigrateToEnterprise.bat <CentralProtocol> <CentralServerName/IP Address> <CentralPort> <ProbeName> <Contact> <Email> <ProbeInstallationKey> -skipMetadata

For Example : MigrateToEnterprise.bat http opm-noc 80 USProbe John John@XyzCompany.com *************

*ProbeInstallationKey - Key can be obtained in Central, go to Settings --> Configuration --> Probe Details.

*-skipMetadata - This argument is optional. Use this if you want to avoid sending collected data from standalone to Central server. If -skipMetadata is not specified, all the data will be pushed to the Central by default and will be time-consuming.

Steps to Migrate OpManager Version 11600 LEE edition to Enterprise Edition

Contact opmanager-support@manageengine.com to migrate OpManager version 11600 LEE to OpManager Enterprise.

Enabling HTTPS in Central and Probe

Steps to enable HTTPS in OpManager : (for version 123181 and above)

  1. In both, probe and Central, navigate to Settings --> Basic Settings --> Security Settings --> SSL Configuration --> Enable Secure Mode.
  2. For more details on configuring HTTPS, refer this page.
  3. Restart Central service.
  4. For all the probes, edit InitImpl attribute in OpManagerProbe/conf/OpManager/CommunicationInfo.xml from
    com.me.opmanager.extranet.remote.communication.http.probe.HTTPProbeCommInit
    to
    com.me.opmanager.extranet.remote.communication.https.probe.HTTPSProbeCommInit
  5. Restart all the probes.
  6. In Central, go to Settings --> Configuration --> Probe Details --> Edit each Probe --> set NAT protocol as HTTPS.

Changing Ports in Central & Probe

In Central :

  • Open Command prompt with administrator privileges and go to the OpManagerCentral/bin directory and execute ChangeWebServerPort.bat (eg : ChangeWebServerPort.bat 443).
  • For all the probes In the "OpManagerProbe/conf/OpManager" directory, locate "NOCServerDetail.xml" file and update the "NOCServerPort" attribute value.
  • First, restart OpManagerCentral and then restart all Probes.

In Probe :

  • Open Command prompt with administrator privileges and go to the OpManagerProbe/bin directory and execute ChangeWebServerPort.bat (eg : ChangeWebServerPort.bat 443).
  • Restart the Probe
  • In Central, go to Settings --> Configuration --> Probe Details --> Edit each Probe --> update the new port in NAT Port.