This version of the manual is no longer supported. Learn more about upgrading your version of MongoDB.

Backup a Sharded Cluster with Database Dumps



The following procedure applies to MongoDB instances using the MMAPv1 storage engine.

This document describes a procedure for taking a backup of all components of a sharded cluster. This procedure uses mongodump to create dumps of the mongod instance. An alternate procedure uses file system snapshots to capture the backup data, and may be more efficient in some situations if your system configuration allows file system backups. See Backup and Restore Sharded Clusters for more information.

See MongoDB Backup Methods and Backup and Restore Sharded Clusters for complete information on backups in MongoDB and backups of sharded clusters in particular.



To capture a point-in-time backup from a sharded cluster you must stop all writes to the cluster. On a running production system, you can only capture an approximation of point-in-time snapshot.

Access Control

The backup role provides the required privileges to perform backup on a sharded cluster that has access control enabled.

Changed in version 3.0.9: The backup role provides additional privileges to back up the system.profile collections that exist when running with database profiling. Previously, users required an additional read access on this collection.


To create these backups of a sharded cluster, you will stop the cluster balancer and take a backup of the config database, and then take backups of each shard in the cluster using mongodump to capture the backup data. To capture a more exact moment-in-time snapshot of the system, you will need to stop all application writes before taking the filesystem snapshots; otherwise the snapshot will only approximate a moment in time.

For approximate point-in-time snapshots, taking the backup from a single offline secondary member of the replica set that provides each shard can improve the quality of the backup while minimizing impact on the cluster.



The following procedure, which includes db.fsyncLock() and db.fsyncUnlock() operations, applies only to MongoDB instances using MMAPv1 storage engine.


Disable the balancer process.

Disable the balancer process that equalizes the distribution of data among the shards. To disable the balancer, use the sh.stopBalancer() method in the mongo shell. For example:

use config

For more information, see the Disable the Balancer procedure.


If you do not stop the balancer, the backup could have duplicate data or omit data as chunks migrate while recording backups.


Lock replica set members.

Lock one member of each replica set in each shard so that your backups reflect the state of your database at the nearest possible approximation of a single moment in time. Lock these mongod instances in as short of an interval as possible.

To lock or freeze a sharded cluster, issue db.fsyncLock() on a member of each replica set in the cluster. Ensure that the oplog has sufficient capacity to allow these secondaries to catch up to the state of the primaries after finishing the backup procedure. See Oplog Size for more information.


Backup one config server.

Run mongodump against a config server mongod instance to back up the cluster’s metadata. The config server mongod instance must be version 2.4 or later and must run with the --configsvr option. You only need to back up one config server.

Use mongodump with the --oplog option to backup one of the config servers.

mongodump --oplog

Backup replica set members.

Back up the “frozen” replica set members of the shards using mongodump and specifying the --oplog option. You may back up the shards in parallel. Consider the following invocation:

mongodump --oplog --out /data/backup/

You must run mongodump on the same system where the mongod ran. mongodump writes the output of this dump as well as the oplog.bson file to the /data/backup/ directory.


Unlock replica set members.

Use db.fsyncUnlock() to unlock the locked replica set members of each shard. Allow these members to catch up with the state of the primary.


Re-enable the balancer process.

Re-enable the balancer with the sh.setBalancerState() method.

Use the following command sequence when connected to the mongos with the mongo shell:

use config