Docs Menu

Docs HomeMongoDB Ops Manager

Upgrade Ops Manager

On this page

  • Upgrade Path
  • Considerations
  • Prerequisites
  • Procedure
  • Troubleshooting

This tutorial describes how to upgrade an existing Ops Manager installation.

Warning

Upgrade Managed Databases to MongoDB 3.6 or Later

Ops Manager 6.0 doesn't support MongoDB 3.4. If you are using MongoDB 3.4 or earlier and want to upgrade to Ops Manager 6.0, you must upgrade to at least MongoDB 3.6. However, we recommend that you upgrade to at least MongoDB 4.0 before upgrading to Ops Manager 6.0.

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

Important

  • If you have an Ops Manager 4.2 or later installation with more than one Ops Manager host pointing to the same Application Database, you can upgrade Ops Manager without incurring monitoring downtime. During this upgrade, Ops Manager enters a state known as Upgrade Mode. See Upgrade Mode for more information.

  • To ensure a successful upgrade, 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.

  • There are no supported downgrade paths for Ops Manager.

Note

All upgrades for Ops Manager versions 4.2.x and later use the same procedure. To upgrade to a higher version, you must first use this procedure upgrade to the latest available patch of your initial version, then use the procedure again to upgrade to the next version. If the following table has additional information related to the upgrade procedure for a given version, review it first.

The following table lists upgrade paths for all versions:

Existing Version
Upgrade Path
6.0.x

Upgrade from Ops Manager 6.0.x to the latest available patch version of 6.0 using this procedure.

5.0.x

Upgrade from Ops Manager 5.0.x to the latest available patch version of 5.0. Then upgrade to the latest available version of 6.0. Use this procedure for both processes.

4.4.x

Upgrade from Ops Manager 4.4.x to the latest available patch version of 4.4. Then upgrade to the latest available version of 5.0. Use this procedure for both processes.

Important

Ops Manager version 4.4.13 fixes a bug that would re-enable Ops Manager instances for API writes during an upgrade.

Tip

4.2.x

Upgrade from Ops Manager 4.2.x to the latest available patch version of 4.2. Then upgrade to the latest available version of 4.4. Use this procedure for both processes.

An unintentional and temporary disabling of TLS occurs when upgrading to versions earlier than 4.2.24. Upgrading to 4.2.24 or later first avoids this outcome.

4.0.x

Use the v4.2 upgrade tutorial to upgrade from Ops Manager 4.0.x to version 4.2.24 or later. Then use this procedure to upgrade to the latest available version of 4.2.

An unintentional and temporary disabling of TLS occurs when upgrading to versions earlier than 4.2.24. Upgrading to 4.2.24 or later first avoids this outcome.

3.6.x
Use the v4.0 upgrade tutorial to upgrade from Ops Manager 3.6.x to version 4.0.x.
3.4.x
Use the v3.6 upgrade tutorial to upgrade from Ops Manager 3.4.x to version 3.6.x.
2.x or earlier
Use the v3.4 upgrade tutorial to upgrade from Ops Manager 2.x or earlier.

Before upgrading Ops Manager from 5.0 to 6.0, review the following considerations:

Use standard connection strings when connecting to the AppDB during the upgrade procedure. Using DNS SRV connection strings can cause the upgrade to fail.

Ops Manager 6.0.0 requires a minimum of MongoDB 4.4.0 for Ops Manager backing databases.

Note

Your MongoDB version for Ops Manager backing databases can't be later than your Ops Manager version.

If Ops Manager manages your MongoDB Tools, the tool versions are upgraded when you upgrade Ops Manager.

If you run Ops Manager 6.0.x in local mode, you must download and install a compatible version of the MongoDB Tools TGZ package to the versions directory.

Ops Manager Server Versions
Compatible MongoDB Database Tools Version

To access older versions of the MongoDB Tools, click Archived releases on the Download page.

Adds support to run Ops Manager on Debian 11.

  • Deprecates SNMP alerts. Ops Manager 7.0.0 will not include SNMP alerts.

  • Adds support for automating deployments on RedHat Enterprise Linux version 8 and Amazon Linux 2 on the ARM64/aarch64 architecture.

  • Removes support for automating deployments on Debian 9 and RedHat Enterprise Linux 6.

Removes support for automating MongoDB 3.4 deployments.

Your servers must meet the Ops Manager System Requirements.

Warning

Potential for Production Failure

Your Ops Manager instance can fail in production if you fail to configure the following:

If your backing databases run the MMAPv1 storage engine, the upgrade process fails. Ops Manager prompts you to upgrade the storage engine for those backing databases to WiredTiger.

You must have administrator privileges on the servers on which you perform the upgrade.

To download the software, click the download link available on the customer downloads page. MongoDB provides the URL of that page to its customers.

  • If you can't access this link, visit the download page for a current evaluation copy of the Ops Manager software.

  • If you need an earlier version of the Ops Manager software, visit the Release Archive.

If you plan to run Ops Manager in Local Mode, download the MongoDB software to your versions library directory. The required software includes:

Before you upgrade Ops Manager, make sure:

If you upgraded the platform for the MongoDB Agent hosts, upgrade the MongoDB Agents before upgrading Ops Manager.

Note

Upgrade Mode for Highly Available applications

If you have an Ops Manager 4.2 or later installation with more than one Ops Manager host pointing to the same Application Database, you can upgrade Ops Manager without incurring monitoring downtime. During this upgrade, Ops Manager enters a state known as Upgrade Mode. This mode enables the following benefits throughout the upgrade process:

  • Alerts and monitoring operate

  • Ops Manager instances remain live

  • Ops Manager Application may be accessed in read-only mode

  • Ops Manager APIs that write or delete data are disabled

Your Ops Manager instance stays in Upgrade Mode until all Ops Manager hosts have been upgraded and restarted.

You should not upgrade more than one Ops Manager host at a time.

When Ops Manager enters upgrade mode, the Backup Daemons attempt to stop themselves. This process can fail if the Daemons are in the middle of a long backup job. In this case, do one of the following:

  • Restart the first Ops Manager instance once the Backup Daemons finish the job.

  • Stop the Backup Daemons manually.

To manually stop your Backup Daemons:

If you're running your Ops Manager Application in a high availability configuration, complete this procedure on one Ops Manager host at a time.

This warning displays due to the version of the Guice library that Ops Manager uses. You can safely ignore this warning.

←  Configure Ops Manager to Use an HTTP Proxy for Outgoing TrafficVerify Integrity of Ops Manager Packages →