This page describes compatibility between Ops Manager features and MongoDB.
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 8.0 | Ops Manager 7.0 | Ops Manager 6.0 |
|---|---|---|---|
MongoDB 8.2 | Supported | ||
MongoDB 8.0 | Supported | ||
MongoDB 7.0 | Supported | Supported | |
MongoDB 6.0 | Supported | Supported | Supported |
MongoDB 5.0 | Deprecated | Supported | Supported |
Note
A deprecated version still works with the corresponding Ops Manager release, but we will remove the support for this version in the next release. MongoDB Support recommends migrating to a supported version to avoid potential incompatibility issues.
To learn more, see MongoDB Legacy Support Policy and MongoDB Software Lifecycle Schedules for Ops Manager.
Version support covers the full release series from the first to the last release.
Example
Ops Manager 8.0 supports MongoDB versions 6.0 through 8.0.
Tip
To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual.
BI Connector Compatibility
To use the MongoDB Connector for BI on Ops Manager 8.0.0 or later, you must use MongoDB 4.4 or later.
If your BI Connector runs MongoDB 3.6, you must disable the BI Connector, or update MongoDB to 4.4 before you upgrade Ops Manager to 8.0.0 or later.
Backup Considerations for MongoDB Versions
To learn more about backup considerations specific, see Backup Considerations.
To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual.
Agent Compatibility
The following table lists the Ops Manager versions that are compatible with the associated MongoDB Agent release series.
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.