Docs Menu
Docs Home
MongoDB Cloud Manager

FAQ: Backup and Restore

On this page

  • Requirements
  • What MongoDB Permissions does Backup Require?
  • How Does Cloud Manager Measure Data Size?
  • Does Backup Work with All Types of Deployments?
  • Why Does The Backup Feature Not Support Standalone Deployments?
  • Operations
  • Will Backup Impact My Production Databases?
  • How Do I Maintain a Replica Set with Backup enabled?
  • Legacy Backup Agent
  • Where Should I Run The Backup Agent?
  • Can I Run the Backup and Monitoring Agents on a Single System?
  • Can I Run Multiple Backup Agents to Achieve High Availability?
  • Does the Backup Agent Modify My Database?
  • How Does the Initial Backup Sync Impact Database Performance?
  • Namespace Filters
  • How Can I Prevent Cloud Manager from Backing Up a Collection?
  • How Can I Change which Namespaces Are Backed Up?
  • Data Restoration
  • How Does Cloud Manager Provide Point-in-Time Restores?
  • Can I Take Snapshots More Frequently than Every 6 Hours?
  • Can I Set My Own Snapshot Retention Policy?
  • How Long Does It Take to Create a Restore Snapshot?
  • Does the Backup Feature Perform Any Data Validation?
  • How Do I Restore a Snapshot?
  • What Is Delivered when I Restore a Snapshot?
  • How Does Cloud Manager Roll Back Backed-up Data?
  • What Conditions Require a Resync?

This FAQ addresses common questions about Cloud Manager and how it backs up and restores databases and collections.

The introduction of the MongoDB Agent and the new backup process for MongoDB 4.2 with a FCV of 4.2 have changed some of these answers. Those answers have admonitions explaining the impact of these new features to existing answers.

If you are backing up a MongoDB instance that has authentication enabled, the MongoDB Agent requires the privileges described for the MongoDB Agent backup function.


See also:

Cloud Manager uses the following conversions to measure snapshot size and to measure how much oplog data has been processed:

  • 1 MB = 1024 2 bytes (1 MiB)

  • 1 GB = 1024 3 bytes (1 GiB)

  • 1 TB = 1024 4 bytes (1 TiB)

  • For MongoDB 4.2 and later, see Backup Considerations for Databases.

  • For any MongoDB with FCV of 4.0 and earlier databases, Backup doesn't support standalone deployments. Backup has full support for replica sets and sharded clusters.

Cloud Manager copies data from the oplog to provide a continuous backup with point-in-time recovery. Cloud Manager does not support backup of standalone hosts because they do not have an oplog. To support backup with a single mongod instance, you can run a one-member replica set.


This answer applies only to databases running MongoDB with FCV of 4.0 and earlier

The Backup feature typically has minimal impact on production MongoDB deployments. This impact performs similar to that of adding a new secondary to a replica set.

By default, the agent performs its initial sync, the most resource intensive operation for backups, against a secondary member of the replica set to limit its impact. You may optionally configure the agent to perform the initial sync against the replica set's primary, although this increases the impact of the initial sync operation.

Yes, Cloud Manager uses enterprise-grade hardware co-located in secure data centers to store all user data. The Backup transmits all data using SSL. The data is stored and processed on encrypted volumes. Cloud Manager requires two-factor authentication to provide any data for restores.

There is currently no limit on the total size of snapshot storage. Backup works best for deployments whose total size is less than 2 TB.

If you wish to use the Backup feature for a larger deployment, please contact us for more information.

Most operations in a replica set are replicated via the oplog and are thus captured by the backup process. Some operations, however, make changes that are not replicated: for these operations you must have Cloud Manager resync from your current replica set to include the changes.

The following operations are not replicated and therefore require resync:

  • Renaming or deleting a database by deleting the data files in the data directory. As an alternative, remove databases using an operation that MongoDB will replicate, such as db.dropDatabase() from mongosh.

  • Changing any data while the instance is running as a standalone.

  • Rolling index builds.

  • Using compact or repairDatabase to reclaim a significant amount of space.

    Resync is not strictly necessary after compact or repairDatabase operations but will ensure that the Cloud Manager copy of the data is resized, which means quicker restores and lower cost.

The pricing for Cloud Manager Backup is based on snapshot size, schedule, and retention policy. See Backup Pricing.

Backup capability has been moved to the MongoDB Agent with Backup activated. This replaces the individual Backup Agent. This information covers issues unique to the legacy Backup Agent. All of this information applies to MongoDB databases running FCV of 4.0 or earlier.

Run the Backup Agent on a host that:

  • Is separate from your MongoDB instances. This avoids system resource contention.

  • Can connect to your MongoDB instances. Check network settings for connections between the agent and MongoDB hosts. For a list of needed ports, see open ports for agents.

  • Has at least 2 CPU cores and 3 GB of RAM above platform requirements. With each backup job it runs, the Backup Agent further impacts host performance.

There is no technical restriction that prevents the Backup Agent and the Monitoring from running on a single system or host. However, both agents have resource requirements, and running both on a single system can affect the ability of these agents to support your deployment in Cloud Manager.

The resources required by the Backup Agent depend on rate and size of new oplog entries (i.e. total oplog gigabyte/hour produced.) The resources that the Monitoring requires depends on the number of monitored mongod instances and the total number of databases provided by the mongod instances.

You can run multiple Backup Agents for high availability. If you do, the Backup Agents must run on different hosts.

When you run multiple Backup Agents, only one agent per project is the primary agent. The primary agent performs the backups. The remaining agents are completely idle, except to log their status as standbys and to periodically ask Cloud Manager whether they should become the primary.

The Backup Agent writes a small token called a checkpoint into the oplog of the source database at a regular interval. These tokens provide a heartbeat for backups and have no effect on the source deployment. Each token is less than 100 bytes.


You may use checkpoints for clusters that run MongoDB with Feature Compatibility Version of 4.0 or earlier. Checkpoints were removed from MongoDB instances with FCV of 4.2 or later.


See also:

The impact of the initial backup synchronization should be similar to syncing a new secondary replica set member. The Backup Agent does not throttle its activity, and attempts to perform the sync as quickly as possible.

Backup always connects to the Cloud Manager servers using an TLS (HTTPS) connection.

Backup can connect to replica sets and shared clusters configured with TLS.


Namespace filtering is supported only for Cloud Manager versions 6.0.8 and later. Your MongoDB deployments must have featureCompatibilityVersion values of 4.0 and earlier, or 6.0.1 and later.

Cloud Manager provides a namespaces filter that allows you to specify which collections or databases to back up.

To edit the filter, see Edit a Backup's Settings. Changing the namespaces filter might necessitate a resync. If so, Cloud Manager handles the resync.

Cloud Manager produces a copy of your data files that you can use to seed a new deployment.

When you trigger the restore, Cloud Manager creates a link to this snapshot. Once clicked, Cloud Manager retrieves chunks from the Snapshot Store and streams them to the target host.

The MongoDB Backup Restore Utility running on that host then downloads and applies oplog entries to reach the specified point in time.

Cloud Manager can build a restore to any point in time within a 24-hour period by replaying the oplog to the desired time.

To learn how to restore replica sets and sharded clusters, see Restore MongoDB Deployments.

No. Cloud Manager does not support a snapshot schedule more frequent than every 6 hours. For more information, see Snapshot Frequency and Retention Policy.

Yes. You can change the schedule through the Edit Snapshot Schedule menu option for a backed-up deployment. Administrators can change the snapshot frequency and retention policy through the snapshotSchedule resource in the API.

Customizing snapshot frequency and retention policies give you greater control over your backup costs.

Although we only charge you for only one copy of the data, Cloud Manager stores at least 3 copies of your data in at least 2 geographic locations to ensure redundancy.

Cloud Manager transmits all backups in a compressed form from the Cloud Manager host to your infrastructure.

Within the U.S., Cloud Manager sends snapshots at 50 to 100 Mbps. Assuming a compression factor of 4x and transmission speeds of 50 Mbps, transmitting a 250 GB snapshot takes 2.5 hours.

In addition, point-in-time restores depend upon the amount the oplog entries that your host must apply to the received snapshot to roll forward to the requested point-in-time of the backup.

Backup conducts basic corruption checks and provides an alert if any component (e.g. the agent) is down or broken, but does not perform explicit data validation. When it detects corruption, Cloud Manager errs on the side of caution and invalidates the current backup and sends an alert.

You can request a restore via Cloud Manager, where you can then choose which snapshot to restore and how you want Cloud Manager to deliver the restore. All restores require 2-factor authentication. If you have SMS set up, Cloud Manager will send an authorization code via SMS. You must enter the authorization code into the backup interface to begin the restore process.


From India, use Google Authenticator for two-factor authentication. Google Authenticator is more reliable than authentication with SMS text messages to Indian mobile phone numbers (i.e. country code 91).

Cloud Manager delivers restores as tar.gz archives of MongoDB data files.

To learn more about restores, see Restore MongoDB Deployments.

If your MongoDB deployment experiences a rollback, then Cloud Manager also rolls back the backed-up data.

Cloud Manager detects the rollback when a tailing cursor finds a mismatch in timestamps or hashes of write operations. Cloud Manager enters a rollback state and tests three points in the oplog of your replica set's primary to locate a common point in history. Cloud Manager rollback differs from MongoDB secondary rollback in that the common point does not necessarily have to be the most recent common point.

When Cloud Manager finds a common point, the service invalidates oplog entries and snapshots beyond that point and rolls back to the most recent snapshot before the common point. Cloud Manager then resumes normal backup operations.

If Cloud Manager cannot find a common point, a resync is required.


This feature is incompatible with MongoDB 4.2 with FCV of 4.2.

If the Backup Agent's tailing cursor cannot keep up with your deployment's oplog, then you must resync your backups.

This scenario might occur if:

  • Your application periodically generates a lot of data, shrinking the primary's oplog window to the point that data is written to the oplog faster than Cloud Manager can consume it.

  • If the Backup Agent is running on an under-provisioned or over-used machine and cannot keep up with the oplog activity.

  • If the Backup Agent is down for a period of time longer than the oplog size allows. If you bring down your agents, such as for maintenance, restart them in a timely manner. For more information on oplog size, see Replica Set Oplog in the MongoDB manual.

  • If you delete all replica set data and deploy a new replica set with the same name, as might happen in a test environment where deployments are regularly torn down and rebuilt.

  • If there is a rollback, and Cloud Manager cannot find a common point in the oplog.

  • If an oplog event tries to update a document that does not exist in the backup of the replica set, as might happen if syncing from a secondary that has inconsistent data with respect to the primary.

  • If you create an index in a rolling fashion.

← FAQ: Automation