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.

MongoDB 2.4 reached its End of Life date in March 2016

Starting in Ops Manager 3.6, MongoDB 2.4 is no longer supported for Automation and Backups:

  • All MongoDB 2.4 processes in Automation will be unmanaged.
  • All MongoDB 2.4 backups will be stopped.

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:

Ops Manager Release Series Minimum Compatible MongoDB Versions
4.0 2.6.0, 3.0.0, 3.2.0 3.4.0, 3.6.0, and 4.0
3.6 2.4.0 (monitoring only), 2.6.0, 3.0.0, 3.2.0, 3.4.0, 3.6.0
3.4 2.4.3, 2.6.0, 3.0.0, 3.2.0, 3.4.0
2.0 to 3.2 2.4.3, 2.6.0, 3.0.0, 3.2.0
1.6 to 1.8 2.4.3, 2.6.0, 3.0.0

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.

See also

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

Agent Compatibility

Monitoring Agent 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 Agent PowerPC Compatibility

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

Backup Agent 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.