- Reference >
- MongoDB Compatibility Matrix
MongoDB Compatibility Matrix¶
On this page
This page describes compatibility between Ops Manager features and MongoDB.
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.
MongoDB Versions Compatible with Ops Manager¶
Ops Manager can manage databases that run specific versions of MongoDB. The following table displays the version compatibility. The MongoDB edition can be either Community or Enterprise.
| MongoDB Version | Ops Manager 5.0 |
|---|---|
| MongoDB 5.0 | check circle icon |
| MongoDB 4.4 | check circle icon |
| MongoDB 4.2 | check circle icon |
| MongoDB 4.0 | check circle icon |
| MongoDB 3.6 | check circle icon |
| MongoDB 3.4 | |
| MongoDB 3.2 | |
| MongoDB 3.0 | |
| MongoDB 2.6 |
Version support covers the full release series from the first to the last release.
Example
Ops Manager 5.0 supports the entire MongoDB release series from 4.0.0 to 4.0.20.
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 Versions¶
To learn more about backup considerations specific to MongoDB 4.4 and later and 4.2 and earlier, see Backup Considerations.
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 3.2.7.1927 or later.
Backup Compatibility¶
To back up MongoDB deployments running the 3.6 or later release series, upgrade to Backup Agent 6.0.3.689 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.
Note
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.