This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

MongoDB Compatibility Matrix

This page describes compatibility between Ops Manager features and MongoDB.

Ops Manager supports certain End of Life MongoDB versions

Ops Manager won’t support Backup and Monitoring for MongoDB 2.6, 3.0, 3.2, or 3.4 after September 30, 2022. Currently, Ops Manager doesn’t support Automation for MongoDB 2.6, 3.0, 3.2, or 3.4.

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

MongoDB Versions Compatible with Ops Manager

The following table lists which versions of MongoDB Community and Enterprise are compatible with each major version of Ops Manager:

Supported Versions of MongoDB for Each Version of Ops Manager
MongoDB Version Ops Manager 4.4
MongoDB 4.4 check circle icon
MongoDB 4.2 check circle icon
MongoDB 4.0 check circle icon
MongoDB 3.6 check circle icon

Version support covers the full MongoDB release series from the first to the last release.

See also

To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual.

LDAP Authorization Compatibility

LDAP authorization was added to MongoDB Enterprise with version 3.4. This feature allows you to assign roles to users using LDAP. This feature was later changed to provide additional security with MongoDB 3.4.11. Ops Manager 3.4.13 or later, 3.6.3 or later, and 4.0.0 or later are compatible with MongoDB versions 3.4.11 or later.

Backup Considerations for MongoDB 4.2 and 4.4

Backup support for the following MongoDB versions is growing but currently limited:

  • 4.2 with "featureCompatibilityVersion" : 4.2
  • 4.4 with "featureCompatibilityVersion" : 4.4

Support will be extended in future releases of Ops Manager.

To learn more about backup considerations specific to MongoDB 4.2 and 4.4, see Backup Considerations.

See also

To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual.

Agent Compatibility

Monitoring Compatibility

To monitor a deployment running MongoDB 3.6 or later release series, you must use Monitoring Agent version 2.7.0 or later.

Automation PowerPC Compatibility

To manage PowerPC Linux-based hosts, you must use Automation Agent or later.

Backup Compatibility

To back up MongoDB deployments running the 3.6 or later release series, upgrade to Backup Agent or later.

MongoDB Deployment Types

Using Ops Manager, you can configure all MongoDB deployment types: sharded clusters, replica sets, and standalones.

The shards in a sharded cluster must be replica sets. That is, a shard cannot be a standalone mongod. If you must run a shard as a single mongod (which provides no redundancy or failover), run the shard as a single-member replica set.


You may not upgrade a sharded MongoDB deployment to version 3.4 if the deployment uses mirrored mongod instances as config servers. To allow the sharded deployment to be upgraded, see Convert Config Servers to a Replica Set. The conversion requires that the sharded deployment run MongoDB version 3.2.4 or later. Deployments running previous versions must upgrade to version 3.2.4 before an upgrade to version 3.4.