MongoDB Cloud Manager
On this page
- OAuth 2.0 authentication for programmatic access to Cloud Manager is available as a Preview feature.
- The feature and the corresponding documentation might change at any time during the Preview period. To use OAuth 2.0 authentication, create a service account to use in your requests to the Cloud Manager Public API.
Welcome to the documentation for MongoDB Cloud Manager. Engineered by the team who develops MongoDB, Cloud Manager provides a complete package for managing MongoDB deployments.
MongoDB Cloud Manager can automate, monitor, and back up your MongoDB infrastructure.
Automation
Cloud Manager Automation enables you to configure and maintain MongoDB nodes and clusters.
MongoDB Agents using Automation on each MongoDB host can maintain your MongoDB deployments. You can install the MongoDB Agent. Automation can add hosts and deploy and upgrade new or existing clusters.
Monitoring
Cloud Manager Monitoring provides real-time reporting, visualization, and alerting on key database and hardware indicators.
How Monitoring Works
When you activate Monitoring on a MongoDB host, Monitoring collects statistics from the nodes in your MongoDB deployment. The Agent transmits database statistics back to Cloud Manager to report deployment status in real time. You can set alerts on indicators you choose.
Backup
Cloud Manager Backup provides scheduled snapshots and point-in-time recovery of your MongoDB replica sets and sharded clusters.
How Backup Works
When you activate Backup for a MongoDB deployment, Backup takes snapshots of data from the MongoDB processes you have specified.
Note
Only sharded clusters or replica sets can be backed up. To back up a standalone mongod process, you must convert it to a single-member replica set.
Backup Workflow
Backups rely upon the
MongoDB version compatibility
of your database.
This Feature Compatibility Version ranges from the current version to
one version earlier. For MongoDB 4.2, the FCV can be 4.0 or
4.2.
The backup process takes a snapshot of the data directory at its scheduled snapshot intervals.
This process copies the data files in a MongoDB deployment, sending them over the network to backup storage for Cloud Manager.
Your deployment can still handle read and write operations during the copying process.
With the new backup process, there are no longer initial syncs. As a
result of not having initial syncs, Cloud Manager (using a mongod running
FCV 4.2) can support a wider array of customers such as those
heavily using renameCollection.
The MongoDB Agent uses WiredTiger's incremental backup cursor to capture the incremental changes.
Once backup has started, Cloud Manager backs up the data as an ongoing and continuous process. This process continues creating snapshots as long as the head database remains synchronized with the database.
This process works like replica set data synchronization.
The backup process:
Performs an inital sync to back up all of your existing data in its current state. In sharded clusters, this occurs on each shard and on the config servers.
Takes snapshots of the
datadirectory in a deployment as often as your snapshot schedule specifies and then transfers the snapshots to a storage system.Monitors the oplog constantly and adds new database operations to the latest backup to keep the local Cloud Manager copy of the data to allow point-in-time restores.
The MongoDB Agent then tails each replica set's oplog to update the backup when performing a point-in-time restore. The backup is consistent with the original primary up to the last oplog that the MongoDB Agent supplies.
The backup process works in this manner regardless of how snapshots are stored.
Backup uses a MongoDB instance version equal to or greater than the version of the replica set it backs up.
Backup takes and stores snapshots based on a user-defined snapshot retention policy. Sharded cluster snapshots temporarily stop the balancer. The snapshots then can insert a marker token into all shards and config servers in the cluster. Cloud Manager takes a snapshot when the marker tokens appear in the snapshot data.
To learn more about how to configure backups, see Backup Configuration Options.
Monthly backup costs for Cloud Manager are based on the size per-gigabyte of your most recent snapshot. To learn about Cloud Manager backup pricing, see Backup Costs.
Restore Data
Backup can restore data from a complete scheduled snapshot or from a selected point between snapshots.
You can restore sharded clusters and replica sets from selected points in time.
For sharded clusters, you can restore from checkpoints between snapshots.
For replica sets, you can restore from selected points in time.
When you restore from a snapshot, Cloud Manager reads directly from the snapshot storage. You can restore the snapshot:
To another cluster.
To download the snapshot files from an HTTPS link.
When you restore from a point in time, Cloud Manager does the following:
Restores a full snapshot from the snapshot storage.
Applies stored oplogs until it reaches the specified point.
Delivers the snapshot and oplog updates using the same HTTPS mechanisms.
When you restore from a checkpoint or point in time, Cloud Manager does the following:
Restores a full snapshot from the snapshot storage.
Applies stored oplogs until it reaches the specified point.
Delivers the snapshot and oplog updates using the same HTTPS mechanisms. To enable checkpoints, see Enable Cluster Checkpoints.
MongoDB welcomes your feedback. Let us know how we can improve Ops Manager.