Navigation

Upgrade Ops Manager

Upgrade Paths

The version of your existing Ops Manager installation determines the upgrade path you must take to upgrade to Ops Manager 3.6 or later.

Important

  • You must follow the upgrade path for your existing version to perform necessary database migrations.
  • To protect your data, Ops Manager refuses to start direct upgrades from versions 1.8.x and 2.0.x to version 3.4 or later.
  • In high availability environments, you must shut down every Ops Manager application server before starting any Ops Manager application servers upgraded to the new version.

The following table lists upgrade paths for all versions:

Existing Version Upgrade Path
3.6.x Use this tutorial to upgrade from Ops Manager on 3.6.x to a more recent 3.6.x version.
3.4.x Use this tutorial to upgrade from Ops Manager 3.4.x to version 3.6.x.
2.x
  1. Upgrade from Ops Manager 2.0.x to version 3.4.x. For the specific upgrade path for your version, refer to v3.4 upgrade documentation.

  2. Ensure that your deployment has fully migrated to 3.4 before upgrading to 3.6. To verify:

    1. Click the Admin link in the top right corner of Ops Manager.
    2. Go to General > Ops Manager Config.
    3. Click Miscellaneous tab, and scroll to Ops Manager Data Migration section. If the displayed status is Migration is Complete, you may upgrade to 3.6

    For more information, see Ops Manager Data Migration.

  3. Use this tutorial to upgrade from Ops Manager 3.4.x to version 3.6+.

1.8.x or earlier
  1. Follow the appropriate upgrade path to upgrade your version to 2.0.x. For the specific upgrade path for your version, refer to v2.0 upgrade documentation.
  2. Upgrade from Ops Manager 2.0.x to version 3.4.x. For the specific upgrade path for your version, refer to v3.4 upgrade documentation.
  3. Use this tutorial to upgrade from Ops Manager 3.4.x to version 3.6+.

There are no supported downgrade paths for Ops Manager.

Important

It is crucial that you back up the existing conf-mms.properties and gen.key files because the upgrade process will delete existing data.

Advisories

Before upgrading Ops Manager from 3.4 to 3.6, complete the following actions:

  • Upgrade all backing databases to MongoDB 3.2 or later.

  • Upgrade the monitoring schema.

    To monitor the schema upgrade:

    1. Click Admin.

    2. Click Ops Manager Config.

    3. Click the Miscellaneous tab.

      The progress should be shown before the Default Monitoring Data Retention heading.

  • Change mms.minimumTLSVersion if you must support older TLS versions.

    Ops Manager Application supports TLS 1.2 only by default.

    To re-enable ciphers which have been disabled, change mms.disableCiphers.

    Warning

    Consider the security implications carefully before doing this.

Procedures

Upgrade with RPM Package
Upgrade Ops Manager on Red Hat, Fedora, CentOS, and Amazon AMI Linux.
Upgrade with DEB Package
Upgrade Ops Manager on Debian and Ubuntu systems.
Upgrade from Archive on Linux
Upgrade Ops Manager on other Linux systems, without using package management.
Upgrade on Windows
Upgrade Ops Manager on Windows systems.