Navigation

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.

Compatible MongoDB Versions

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

Ops Manager Compatible MongoDB versions
3.6 or later 2.4 (monitoring only), 2.6, 3.0, 3.2, 3.4. 3.6
3.4.x 2.4.3, 2.6, 3.0, 3.2, 3.4
2.0 or later (up to but excluding 3.4) 2.4.3, 2.6, 3.0, 3.2
1.6 or later (up to but excluding 2.0) 2.4.3, 2.6, 3.0

Note

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

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

To back up MongoDB deployments running 3.6 or later, upgrade your Backup Agents to version 6.0.0.676 or later.

Warning

Starting in Ops Manager 3.4, Ops Manager does not support backing up deployments that run MongoDB version 2.4.

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.