- Reference >
- MongoDB Compatibility
MongoDB Compatibility¶
On this page
This page describes compatibility between Ops Manager features and MongoDB.
MongoDB 2.4 reached its End of Life date in March 2016
- Ops Manager will remove support for Automation and Backup of MongoDB 2.4 in Ops Manager 3.6 (estimated date: late 2017). Ops Manager groups must upgrade their MongoDB 2.4 deployments before the Ops Manager 3.6 release. Starting in Ops Manager 3.6, Automation will no longer support upgrades from MongoDB 2.4.
- Ops Manager will continue to support Monitoring of MongoDB 2.4 deployments.
Automation and MongoDB¶
Automation supports MongoDB 2.4 and later.
Automation has these additional compatibility requirements:
| To deploy: | You must run: |
|---|---|
| MongoDB 3.2.x | Ops Manager 2.0 or later |
| MongoDB 3.0.x | Ops Manager 1.6 or later |
Monitoring and MongoDB¶
Monitoring supports MongoDB 2.4 or later. However, to monitor MongoDB 3.0 or later, you must use Monitoring Agent version 2.7.0 or later.
Monitoring has these additional compatibility requirements:
| To monitor: | You must run: |
|---|---|
| MongoDB 3.2.x | Ops Manager 2.0 or later |
| MongoDB 3.0.x | Ops Manager 1.6 or later |
Backup and MongoDB¶
Ops Manager can back up:
- MongoDB 2.4.3 or later for sharded clusters.
- MongoDB 2.0 or later for replica sets.
Backup has these additional compatibility requirements:
| To back up: | You must run: |
|---|---|
| MongoDB 3.2.x | Ops Manager 2.0 or later |
| MongoDB 3.0.x | Ops Manager 1.6 or later |
MongoDB Deployment Types¶
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.