Docs Menu
Docs Home
/
MongoDB Ops Manager
/ /

Change the Version of MongoDB

On this page

  • Considerations
  • Prerequisites
  • Procedure

You can upgrade or downgrade MongoDB versions within the same Feature Compatibility Version (FCV) in Ops Manager sharded clusters, replica sets, and standalone MongoDB instances while maximizing the availability of your deployments.

You can add custom-built versions of MongoDB for Ops Manager to download.

If Ops Manager doesn't manage your deployment, change the version of MongoDB manually. To learn more, see upgrade tutorials for each MongoDB release.

Note

Ops Manager support for End of Life MongoDB versions

Ops Manager doesn't support Backup, Monitoring, or Automation for versions earlier than MongoDB 3.6.

Ops Manager continues to support Automation, Backup, and Monitoring using the MongoDB Agent for clusters running MongoDB 3.6 or later.

Note

Downgrading Limitations

You cannot downgrade a MongoDB deployment:

  • From version 5.0 to any version before 4.4.0

  • From version 4.4 to any version before 4.2.6

If the MongoDB deployment has its Feature Compatibility Version set to the same release series as its Version, you must first manually downgrade the instance's featureCompatibilityVersion.

1
2

To downgrade your deployment from version 7.0 to 6.0, you must contact support for assistance. For more information, see Downgrade 7.0 to 6.0.

Note

This sets the featureCompatibilityVersion to 6.0.

3
  1. Import the deployment back into Ops Manager.

  2. Edit the deployment in Ops Manager and select the downgraded version under the Version column.

2

Read the Downgrade Considerations and take appropriate action for unsupported features.

4
  1. Import the deployment back into Ops Manager.

  2. Edit the deployment in Ops Manager and select the downgraded version under the Version column.

3
  1. Import the deployment back into Ops Manager.

  2. Edit the deployment in Ops Manager and select the downgraded version under the Version column.

2

Note

This removes any 4.4 incompatible features and sets the featureCompatibilityVersion to 4.2.

3
  1. Import the deployment back into Ops Manager.

  2. Edit the deployment in Ops Manager and select the downgraded version under the Version column.

1
  1. If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.

  2. If it is not already displayed, select your desired project from the Projects menu in the navigation bar.

  3. If it is not already displayed, click Deployment in the sidebar.

  1. Click the Clusters view.

2
3

In the Cluster Configuration section, the Cluster Settings heading lists the processes with their names, MongoDB versions, data directories and log files.

  1. Scroll to the Cluster Settings heading.

  2. Click the Version arrow for the first MongoDB process in the list.

Note

If you're running in local mode and don't see your desired version, you can Update the Version Manifest Manually.

To learn more, see Local Mode Configuration.

4

For each MongoDB process that you want to change:

  1. Click the current version number for the process.

  2. Click the desired version number.

5

If you are upgrading to a new major version, and wish to enable features offered in the new major version, you must also update the featureCompatibilityVersion.

For each MongoDB deployment that you want to change:

  1. Click the current featureCompatibilityVersion for the deployment.

  2. Click the value that matches the desired version number.

6
7
8

Otherwise, click Cancel and you can make additional changes.

Back

MongoDB Versions