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 the 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 -i’ 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. From version 12.4.042, update the Central Details in the Central Details page under Settings-->Configuration.
  10. Restart all the probes.
  11. To clean up the existing machine, uninstall OpManagerCentral.

Steps to migrate Probe from one server to another:

For Windows probe, if OpManager agents are installed for monitoring, kindly carry out the steps in this page before proceeding further.

  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 Probe 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 -i' 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. In the same command prompt execute OpManagerService.bat -i to add OpManagerCentral as a service.
  5. If you want to use the same database, continue without any changes. Please ensure that the database server is reachable in the new machine.
  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.

In Probe:

For Windows probe, if OpManager agents are installed for monitoring, kindly carry out the steps in this page before proceeding further.

  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. In the same command prompt execute OpManagerService.bat -i to add OpManagerProbe as a service.
  5. If you want to use the same database, continue without any changes. Please ensure that the database server is reachable in the new machine.
  6. 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.
  7. Start OpManagerProbe from Windows services in the new machine.
  8. 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 : (from version 124042 and above)

  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:
  7. If the new system's IP address or host name differs from that of the existing machine, go to Settings--> Configuration --> Central in each probe and update the new Central system's IP address or host name.
  8. If the IP address and host name of the new machine is the same as that of the existing machine, the host name of the Central server need not be updated in the Probes.
  9. To clean up the existing machine, uninstall OpManagerCentral.

Steps to migrate Central : (till  version 124041)

  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:
  7. If the new system's IP address or host name differs from that of the existing machine, go to OpManagerProbe/conf/OpManager directory and locate "NOCServerDetail.xml" file and update NOCServerName attribute value with new server name. in each probe and update the new Central system's IP address or host name.
  8. 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:

For Windows probe, if OpManager agents are installed for monitoring, kindly carry out the steps in this page before proceeding further.

  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. To clean up the existing machine, uninstall OpManagerProbe.

Migrating from OpManager Standard/Professional to OpManager Enterprise Edition

If you are upgrading to OpManager Enterprise Edition for reasons concerning scalability or remote network monitoring or both, you can migrate from OpManager Standard/Professional without having to start afresh. This means all the configuration and historical data in the existing OpManager installation can be safely ported to the enterprise edition during the migration.

Upon migration, the existing OpManager installation (Standard/Professional Edition) will function as a Probe server. The Central server has to be installed in a new machine.

To migrate to OpManager Enterprise Edition, follow the steps given below:(For OpManager version 124181 and above)

Step 1: Installing OpManager Central

Install the version of OpManagerCentral corresponding to the version of OpManager Standard/Professional Edition in a new machine.

  1. OpManagerCentral can be downloaded from this link.
  2. In the List of Products field, select OpManager.
  3. In the Product Version field, enter the version corresponding to the existing OpManager Standard/Professional Edition and click on Submit.
  4. In the new page, click on the required version (124181 and above) from the list.
  5. Click on the required OpManager_Central_64bit file to download.

Step 2: Database Backup

Backup the existing OpManager Standard/Professional Edition database. To backup the database, follow the steps in this page.

Step 3: Migration

Migrating to OpManager Enterprise Edition can be done in two ways:

  1. User Interface - Migrating with a step by step wizard
  2. Console Mode - Migrating with Command Prompt. Console mode is chosen as default migration method if the UI is not supported.

1. Migration using User Interface:

  • Go to the bin folder under OpManager installation directory.
    • Windows OS: Run the MigrateToEnterprise.bat file as administrator.
    • Linux OS: Run the MigrateToEnterprise.sh file as root user.
  • The Migration Tool wizard appears.
  • In the wizard, enter the corresponding < Central Server Name >, < Protocol >, < Port > and the < Probe Installation Key >.
  • Enter the required < Probe Name >, < Contact Name > and < Contact E-mail id >.
  • Click on MIGRATE.
(Click on the check box if the historical data in existing OpManager Professional/Essential edition has to be sent to the Central.)

2. Migration using Console mode:

  • Go to the bin folder under OpManager installation directory.
    • Windows OS: Run the MigrateToEnterprise.bat file using -c as parameter.
    • Linux OS: Run the MigrateToEnterprise.ssh file using -c as parameter.
  • Enter the details in the below order.
    < Central Protocol >
    < Central Name >
    < Central Port >
    < Probe Name >
    < Contact Name >
    < Email >
    < Probe Installation Key >    .

Historical data from probe servers can be sent to the Central server based on user preferences. However, the historical data will still be available in probe server.

The migration process is complete. Now the OpManager installation functions as a probe server and synchronizes data with the Central server.

* Points to note:

  • The OpManager Central version (to be downloaded) has to match with the existing OpManager version (Standard/Professional Edition) for successful migration.
  • The OpManager version can be found by clicking on the User icon on the top right hand side of the existing OpManager installation.
  • The Probe Installation Key can be found under OpManagerCentral > Settings > Configuration > Probe Details.
  • Historical data - The past performance data collected by OpManager. Historical data is used for populating graphs, charts and generating reports.

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 versions from 123181 till 124041)

  1. In both, probe and Central, navigate to Settings --> General 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 Probes edit InitImpl attribute in OpManagerProbe/conf/CommunicationInfo.xml from com.me.opmanager.extranet.remote.communication.http.probe.HTTPProbeCommInit to com.me.opmanager.extranet.remote.communication.http.probe.HTTPSProbeCommInit
  5. Restart all the Probes.
  6. In Central, go to Settings --> COnfiguration --> Probe Details --> Edit Each Probe --> set NAT Protocol as HTTPS.

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

  1. In both, probe and Central, navigate to Settings --> General Settings --> Security Settings --> SSL Configuration --> Enable Secure Mode.
  2. For more details on configuring HTTPS, refer this page.
  3. Restart Central service.
  4. Then for each of the Probe, navigate to Settings --> Configuration --> Central Details --> Protocol --> HTTPS.

Changing Ports in Central & Probe

In Central : (till version 124041)

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

In Probe : (till version 124041)

  • 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 new port in NAT Port.


In Central : (from version 124042 and above)

  • Open Command prompt with administrator privileges and go to the OpManagerCentral/bin directory and execute ChangeWebServerPort.bat (eg : ChangeWebServerPort.bat 443).
  • Restart OpManagerCental.
  • Then open each Probe and navigate to Settings --> Configuration --> Central Details  and specify the updated port number of the Central system.

In Probe : (from version 124042 and above)

For Windows probe, if OpManager agents are installed for monitoring, kindly carry out the steps in this page before proceeding further.

  • 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 and edit each Probe for which the port is changed. 
  • Update it in NAT Port.