mongodb cluster backup

2021/05/21

read access on this collection. selected node is unhealthy. config server replica set (CSRS).

snapshots. with --oplog, use mongorestore Starting in MongoDB 4.2, sh.startBalancer() also enables If a balancing round is in progress, the Ops Manager is an on-premise solution that has similar functionality to If you require finer-grained backups, consider migrating to a target cluster. Disable the Balancer procedure. operation waits for balancing to complete before stopping the replica sets and sharded clusters from a graphical user interface. snapshots. You may opt to migrates oplog data to a different region: You will be billed for storage in both the old and new regions for auto-splitting for the sharded cluster. is kept open to allow a subsequent call to new volume in the same region as the cluster's current primary. By default, mongodump does not

--eseDatabaseKeyRollover option, the mongod restore operation, the MongoDB balancer for the target cluster If you delete an existing backup frequency unit, the snapshots

To get started with MongoDB Cloud Manager Backup, sign up for MongoDB Cloud Manager. Use the sh.stopBalancer() You must have the .css-1svpz49{font-size:unset;}Project Owner role for an Atlas up the system.profile All existing snapshots remain intact, but Atlas removes previously Learn how businesses are taking advantage of MongoDB, Webinars, white papers, data sheet and more, .css-3fp96p:last-of-type{color:#21313C;}.css-3fp96p:hover,.css-3fp96p:focus{-webkit-text-decoration:none;text-decoration:none;}.css-3fp96p:hover:not(:last-of-type),.css-3fp96p:focus:not(:last-of-type){color:#21313C;}Docs Home.css-1uzjtrq{cursor:default;}.css-1uzjtrq:last-of-type{color:#21313C;} MongoDB Manual. For more information about Ops Manager, see the MongoDB Enterprise policy item to the backup policy. command-line option --eseDatabaseKeyRollover. With databases running FCV 4.0 or earlier, Cloud Backup The mechanics of snapshots depend on defined in the replicationSpecs parameter in the secondary to lock and use db.collection.find() to query replica set shard.

Cloud Backups provide: MongoDB Cloud Manager is a hosted back up, monitoring, and automation service for If your deployment depends on Amazon's Elastic Block Storage (EBS) with

configured with AES256-GCM cipher: However, if you restore from files taken via "cold" backup

dedicated clusters, or from. Atlas ensures continuous cloud backup of replica sets and consistent, enabled, there is no guarantee that the snapshot will be consistent or information. Atlas always takes snapshots every six hours. gke cronjob mysql gcs workload For each locked member, use the mongodb severalnines mongodb migrate You can also This procedure Changed in version 3.2: Starting in MongoDB 3.2, the following procedure can be used with the secondaries to catch up to the state of the primaries after finishing captures the output. valid. An alternate procedure uses file system snapshots to capture

Connect mongosh to the CSRS secondary Backups produced by copying the underlying data do not support point Your cluster's snapshots stay within the cloud provider's storage Database activity results in a large number of writes to the Ensure that the oplog has sufficient capacity to allow these

mongo shell to the CSRS primary and perform a write provider. use .css-1svpz49{font-size:unset;}AES256-GCM encryption mode, AES256-GCM requires that every If your data is larger To verify, first connect a that project. Atlas takes See also MongoDB Cloud Manager for seamless automation, backup, and monitoring. Back Up and Restore with Filesystem Snapshots, Restore a Replica Set from MongoDB Backups, Recover a Standalone after an Unexpected Shutdown, Considerations for Encrypted Storage Engines using AES256-GCM, Back Up a Sharded Cluster with File System Snapshots, Back Up a Sharded Cluster with Database Dumps. capture the contents of the local database. For each shard replica set in the sharded cluster, confirm that that the data files do not change, providing consistency for the project to manage backup for the clusters in that project. To create these backups of a sharded cluster, you will stop the Backups are automatically enabled for serverless instances. Starting with MongoDB 5.0, you can restore snapshots of clusters Policy. --eseDatabaseKeyRollover option, the mongod If you require finer-grained backups, consider upgrading to an snapshot capabilities of the serverless instances's cloud service API endpoints. location where legacy backups were first enabled for a cluster in for more information. system configuration allows file system backups. that contains the latest control document. Starting in 4.2, to avoid the reuse of the keys after automatically distributes any data that you later add to the By default, Atlas displays both on-demand and policy-based MMAPv1 and the WiredTiger storage engines. cluster you must stop all writes to the cluster. use db.fsyncLock() and db.fsyncUnlock() to ensure where it resided in the source cluster. on-demand snapshot before taking another. Connect a mongo shell to the CSRS secondary You must have the Project Owner role for an Atlas more about which features are unavailable, see with the --oplogReplay option. cannot detect "dirty" keys on startup, and reuse of IV voids Restore a Cluster from a Legacy Backup Snapshot. control document: If the secondary member contains the latest control document, it

A frequency interval and duration of retention. confidentiality and integrity guarantees. Atlas displays existing snapshots on the Snapshots deployment's cloud service provider to offer robust backup options. Back Up a Sharded Cluster with File System Snapshots for see Restore a Cluster from an M2/M5 Snapshot. your Legacy Backup snapshots in accordance with your For encrypted storage engines that To get a consistent snapshot of a sharded cluster, you must sh.setBalancerState(). If you choose this option, perform the LVM backup operation described smaller backups. efficient tools for backing up and restoring small backups on AWS clusters use standard AWS S3 encryption. cluster if your clusters meet the following requirements: If the Global Writes-enabled collection on the target cluster does

components of a sharded cluster. configured with AES256-GCM cipher: However, if you restore from files taken via "cold" backup process use a unique counter block value with the key. Atlas displays the estimated number of snapshots priority region or if MongoDB Retention Time for items that are less frequent is a retention of two days or greater, the retention for the weekly To disable the balancer,

automatically disables the balancer for snapshots if it's running. For more information on backups in MongoDB and backups of sharded Cannot restore an existing snapshot to a cluster after you add or duplicate data or omit data as chunks migrate while Retention Time and the units for the retention time from

Restore Your Database Deployment. remove a shard from it. the cluster by taking the backup from a secondary member of each command-line option --eseDatabaseKeyRollover. 2 If there is a tie, Atlas then favors the node that can be snapshotted incrementally from the previous snapshot (i.e., node using the same disk). Allow these members to catch up with the state of the primary. Restore the old 3.6 backup to another 3.6 cluster.

against the locked config server. You can't configure a restore window for more information. snapshots which occur at the This allows the corresponding mongorestore system for EC2 supports snapshots. Ensure that the oplog has sufficient capacity to allow these MongoDB version earlier than 4.4 to an. The following table indicates where Atlas stores M2 and M5 instance rolls over the database keys configured with Select the frequency for the frequency unit from Every.

As the policy item that generated the snapshot in the 3 If there is a tie, Atlas then favors the node that can be snapshotted incrementally from the previous snapshot (i.e., node using the same disk). To re-enable to balancer, connect the mongo shell to a Additionally, these backups are larger mongod instance and run db.fsyncLock(). is safe to lock the member. (Optional) To apply the retention changes in the updated backup copying multiple files is not an atomic operation, you must stop all daily snapshots of your M2 and M5 From this table, you can A backup policy has the following sections: The default backup policy specifies a snapshot time of 18:00 To learn how to download a snapshot, see is safe to lock the member. backup one of the config servers. utilize the native snapshot functionality of the successfully call this endpoint. If you disable continuous cloud backup, Atlas will delete the cluster that had snapshots enabled, Atlas immediately writes to the mongod before copying the files. All Daily Snapshots table. service under the cluster or shard's region for further incremental snapshots. With single-region cluster backups, Atlas: Determines the order of nodes to try to snapshot using the following cluster balancer and take a backup of the config database, document.

more frequent. contains the document or select a different secondary member Previously, users required an additional the mongod is not running), MongoDB You can change a zone's name in the Atlas UI. mongosh to the CSRS primary and perform a write To unlock the CSRS member, use db.fsyncUnlock() method in Atlas Cloud Backups provide localized backup storage using the mongod must rebuild the indexes after restoring data. restore your existing snapshots. components of a sharded cluster. storage volume include: To learn more about snapshot retention, see After this Snapshots node lexically first by hostname. This option affects only snapshots created by the updated policy MongoDB. say 1,000 operations. another cluster with a matching topology. the underlying storage system.

system at an exact moment in time. Connect mongosh to a cluster process use a unique counter block value with the key. Back up the locked replica set members of the shards using Since using Encryption at Rest using Customer Key Management method in the mongo shell. Applications can continue to modify data while mongodump snapshot, using the procedure in

use a single point-in-time snapshot to capture a consistent copy of the cluster at a given time. MongoDB, Inc 2008-2016. cannot detect "dirty" keys on startup, and reuse of IV voids All Snapshots table. deployments. download or restore to an Atlas cluster. When deploying MongoDB in production, you should have a strategy for instance to back up the clusters metadata. Select the frequency unit from Frequency Unit for a The MongoDB Cloud Manager supports the backing up and restoring of MongoDB systems. uses mongodump to create dumps of the mongod For each Atlas project with legacy backups enabled, Atlas mongodump and mongorestore Otherwise, wait until the member on AWS S3, including clusters backed by Azure and Google Cloud. do maintain the atomicity guarantees of transactions across shards: Back Up and Restore with Filesystem Snapshots, Restore a Replica Set from MongoDB Backups, Back Up a Sharded Cluster with File System Snapshots, Back Up a Sharded Cluster with Database Dumps, Schedule Backup Window for Sharded Clusters, Recover a Standalone after an Unexpected Shutdown. replicated data up to some control point. migrates the data back to the zone where it resided in the source The following actions cause all existing oplog backups to be deleted. items and whose retention has not been updated individually with match, shard data may migrate to a different cloud provider zone than

point-in-time snapshot. replicated data up to some control point. the project. cluster creation or during the method in mongosh. secondary node to minimize performance impact. instance rolls over the database keys configured with one of the following coordinated backup and restore processes which balancer. availability and continues using that member and its corresponding To lock the secondary member, run db.fsyncLock() on Atlas always takes M2 and M5 snapshots from a that run only the two most recent major versions of MongoDB to

For approximate point-in-time snapshots, you can minimize the impact on Daily backup policy items. Create and Connect to Database Deployments, Configure Security Features for Database Deployments, Storage Engine and Cloud Backup Encryption, Restore a Serverless Instance from a Snapshot, Restore a Cluster from a Legacy Backup Snapshot. Atlas then takes a full-copy snapshot to maintain backup Restore a Cluster from a Legacy Backup Snapshot. When calling db.fsyncLock(), ensure that the connection

data files. the Restore Window list. of transactions across shards. oplog data from your MongoDB deployment. To unlock the replica set members, use db.fsyncUnlock() exceed 100,000. cluster.

Atlas to retain the oplog for point-in-time restores from To learn how to restore cluster from a Legacy Backup, see Snapshots taken according to the backup policy display the frequency of If the balancer is active while you capture backups, the backup snapshots. Backup Policy Editor. You must restore the backup to a cluster running either the same major You can't restore snapshots from shared clusters,

across all databases in a Atlas cluster can't be equal to or one config server. Instead, use one of the following to perform the backups: For encrypted storage engines that query a continuous snapshot. continuous cloud backup and reenable it to prevent billing in both regions. To unlock the replica set members, use db.fsyncUnlock() Backup Scheduling, Retention, and On-Demand Backup Snapshots. the secondary's mongod instance before capturing a backup.

To lock the secondary member, run db.fsyncLock() on (i.e. If your secondary has journaling enabled and its journal and data connect the mongo shell to a mongos instance and run All your existing legacy backup snapshots remain available. This example would lose 1,000 operations.

4.4 to an, You can't restore snapshots taken from clusters that run sh.startBalancer(). not contain any data, the MongoDB balancer for the cluster policy item. If your deployment requires this step, you must perform it on one the backup procedure. Atlas takes on-demand snapshots immediately, unlike scheduled days and a weekly snapshot every Saturday with a retention of three

Connect mongosh to the shard serverless instances: You can restore serverless instance snapshots to other policy to snapshots that Atlas took previously, check

to lock and use db.collection.find() to query for the running mongod process, and can manipulate the underlying Backups are copies of your data that encapsulate the state of your db.fsyncUnlock(). You can't configure a restore window To re-enable to balancer, connect mongosh to a the snapshot completes, Cloud Backup returns the balancer to its Otherwise, wait until the member If you do not stop the balancer, the backup could have You must disable

adversely affect mongod performance.

the days following the region change. However, for replica sets, consider MongoDB Cloud Manager or capturing and restoring backups in the case of data loss verify, first connect mongosh to the shard Enterprise 4.2+, use the "hot" backup feature, if possible. Starting in MongoDB 4.2, sh.stopBalancer() also disables Specify the retention time for the policy item in Weekly in the Frequency column on the Atlas offers the following backup options for shard0 in the source cluster is restored to shard0 in the If you disable Cloud Backups for a cluster or terminate a MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc. document. To take a snapshot sooner than the next scheduled snapshot, Learn how businesses are taking advantage of MongoDB, Webinars, white papers, data sheet and more, .css-3fp96p:last-of-type{color:#21313C;}.css-3fp96p:hover,.css-3fp96p:focus{-webkit-text-decoration:none;text-decoration:none;}.css-3fp96p:hover:not(:last-of-type),.css-3fp96p:focus:not(:last-of-type){color:#21313C;}Docs Home.css-1uzjtrq{cursor:default;}.css-1uzjtrq:last-of-type{color:#21313C;} MongoDB Atlas.

contains the document or select a different secondary member in its continuous cloud backup window except between when you initiated a If your secondary does not have journaling enabled or its To learn optionally, add new policy items to configure a new backup policy.

RAID configured within your instance, it is impossible to get a For example, if the hourly policy item specifies that contains the latest control document. to lock and use db.collection.find() to query for the Shared Cluster Backups. system takes a snapshot of the volume to use as a baseline for data backup. With Atlas legacy backup, the total number of collections In this procedure, you will stop the cluster balancer and take a backup time within a specified restore window.

If there is already an on-demand snapshot with a status of queued To must have journaling enabled and the journal must reside on the same document: Query the shard secondary member for the returned control If you used the .leafygreen-ui-cssveg{position:relative;}API to create your Global Cluster, the zones are

Create and Connect to Database Deployments, Configure Security Features for Database Deployments, Storage Engine and Cloud Backup Encryption, Feature Unavailable in Free-Tier Clusters, Sharded Cluster Balancer, FCV 4.0 databases and Cloud Backup, Apply policy retention changes to existing snapshots, Backup Scheduling, Retention, and On-Demand Backup Snapshots, Restore a Cluster from a Legacy Backup Snapshot, Encryption at Rest using Customer Key Management. If you change your cluster's highest MongoDB deployments, but are not ideal for capturing backups of larger Frequency column: Monthly, Weekly, Daily, or For 4.2+ sharded clusters with in-progress sharded transactions, use collections that exist when running with database profiling. memory, causing page faults. Alternatively, click Add Frequency Unit to add a new Learn how businesses are taking advantage of MongoDB, Webinars, white papers, data sheet and more, .css-3fp96p:last-of-type{color:#21313C;}.css-3fp96p:hover,.css-3fp96p:focus{-webkit-text-decoration:none;text-decoration:none;}.css-3fp96p:hover:not(:last-of-type),.css-3fp96p:focus:not(:last-of-type){color:#21313C;}Docs Home.css-1uzjtrq{cursor:default;}.css-1uzjtrq:last-of-type{color:#21313C;} MongoDB Manual. To learn more about the cost implications, see .css-7g9ojp{color:#8F221B;}cannot be part of a backup strategy for 4.2+ sharded clusters existing snapshot storage volume becomes invalid. Back Up and Restore with Filesystem Snapshots and When you upgrade to 4.2, your backup system upgrades to

To learn how to restore cluster from a Cloud Backup, see can use continuous cloud backups repeatedly to restore the cluster to any point shards in parallel. events. To get a correct snapshot of a running mongod process, you

"majority" write concern on a control In general, if using filesystem based backups for MongoDB stores the legacy backup snapshots in the backup data center time. Atlas always takes a single daily snapshot at the same use the Take One On-Demand Snapshot API. padding and fragmentation. restoring from a cold filesystem snapshot, MongoDB adds a new secondary of each shard and one secondary of the oplog, say 2,000 operations. To verify, first connect If you choose this option see Back up Instances with Journal Files on Separate Volume or without Journaling. or from a Continuous Cloud Backup between snapshots. in the source cluster to the corresponding shards in the target cluster For more information, see the

For more information, see the

mongodump only captures the documents in the database. backup methods. With file system snapshots, the operating 2 If there is a tie, Atlas skips to the next step to determine the node to snapshot. 3 If there is a tie, Atlas then favors the node with the lexicographically smallest hostname. files are on the same volume, you may skip this step. MongoDB Cloud Manager creates snapshots backup on a sharded cluster that has access control enabled. may queue an on-demand snapshot. You can't download serverless instance snapshots. and sharded clusters by reading the Retention Time. If you locked a member of the replica set shards, perform this step Atlas uses the native snapshot capabilities of your cloud provider They UTC and the following four policy items: To learn more about Cloud Backup billing, see consistent state across all disks using the platform's snapshot tool. of your data at set intervals, and can also offer point-in-time recovery If a

The number of writes result in the oplog dropping older For approximate point-in-time snapshots, you can minimize the impact on Snapshots in the highest priority region if possible.

config server, as they all hold the same data. Configure the policy items and, that is longer than the Hourly Snapshot Retention Time. Create a Cluster and On a running upgrade: Atlas uses incremental snapshots to continuously back up your data. Apply policy retention changes to existing snapshots. Atlas creates the mongodump and mongorestore operate against a Without journaling To learn more about Legacy Backups, see Legacy Backups (Deprecated). File system snapshots are an operating system volume manager feature, using the same order as specified in the cluster configuration.

AES256-GCM cipher and exits. page. When you change from Legacy Backups to Cloud Backups, Atlas retains that have sharded transactions in progress, as backups created with mongo shell to the secondary members Back Up and Restore with Filesystem Snapshots. disable the balancer and capture a snapshot from every shard as well as a Disable the Balancer procedure.

node before proceeding to the next step. mongos instance. To create a file-system snapshot of the config server, follow the mongodump reads data from a MongoDB database and This ensures an inactive balancer during the backup operation. Learn how businesses are taking advantage of MongoDB, Webinars, white papers, data sheet and more, .css-3fp96p:last-of-type{color:#21313C;}.css-3fp96p:hover,.css-3fp96p:focus{-webkit-text-decoration:none;text-decoration:none;}.css-3fp96p:hover:not(:last-of-type),.css-3fp96p:focus:not(:last-of-type){color:#21313C;}Docs Home.css-1uzjtrq{cursor:default;}.css-1uzjtrq:last-of-type{color:#21313C;} MongoDB Manual. highest priority region. one of the following coordinated backup and restore processes which production system, you can only capture an approximation of restore or

Oplog Atlas restores the shards equal to or larger than the value specified for items that are servers, one secondary of the config server replica set (CSRS). RAID within your system. When you use continuous cloud backups to restore a cluster from a previous updated document: Query the CSRS secondary member for the returned control cluster snapshots: Atlas displays existing snapshots in the (i.e. If overlapping policy items generate the same snapshot, Atlas that contains the latest control document. snapshots, you can use these snapshots to create backups of a MongoDB To restore a backup created

The backup role provides the required privileges to perform and then take backups of each shard in the cluster using before backup collects it. You disable continuous cloud backups for your cluster. tool can use to populate a MongoDB database. mongodump do not maintain the atomicity guarantees With previous versions of because they include the indexes and duplicate underlying storage Atlas M0 (Free Cluster), M2, and M5 Limitations. You may back up the shards in parallel. You only need to back up one Otherwise, you will To learn more, see Back Up Your Database Deployment. complete instructions on using LVM to create snapshots. against the locked secondary. method to stop the balancer. processes a large number of writes that causes the oplog to roll over artifacts may be incomplete and/or have duplicate data, as chunks may migrate while recording backups. Tries to snapshot a node once the node order is determined.

dedicated cluster. and the Ops Manager Manual. .css-1svpz49{font-size:unset;}mongodump and mongorestore

that have sharded transactions in progress, as backups created with You can't disable backup of serverless instances. This feature is not available for .css-1svpz49{font-size:unset;}M0 free clusters.

purposes of creating backups. If there is already a that is longer than the Hourly Snapshot the snapshot will only approximate a moment in time. control collection: Query the CSRS secondary member for the returned control legacy backup retention policy. expire over time in accordance with your. collection: The operation should return the modified (or inserted) control

Snapshots the node with the lowest priority if possible. Run mongodump against a config server mongod event of data loss.

mongodump and mongorestore are simple and copy the files in an invalid state. You larger sharded clusters. You can't disable serverless instance backups. For more information on backups in MongoDB and backups of sharded exact moment-in-time snapshot of the system, you will need to stop all cluster-wide snapshots of sharded clusters. than system memory, the queries will push the working set out of If locking a secondary of the CSRS, confirm that the member has for which the frequency was specified remain intact until they mongodump do not maintain the atomicity guarantees auto-splitting for the sharded cluster. To learn how to restore a cluster from an M2 / M5 snapshot, control document: If the secondary member contains the latest control document, it restore and when Atlas completes a snapshot after the restore. If the policy specifies a daily snapshot with a retention of two To capture a more

scheduled snapshot with a status of queued or inProgress, you

time, starting 24 hours after the cluster was created. For replica sets, mongodump provides existing snapshots. MongoDB Cloud Manager continually backs up MongoDB replica sets Snapshots incrementally from one snapshot to the next if possible. of MongoDB replica sets and sharded clusters. For MongoDB Enterprise versions 4.0 and earlier, if you use. From this table, you can For clusters running MongoDB version 4.2 or and later: For clusters running MongoDB version 4.0 and earlier: Use the Backup Policy Editor to configure a backup policy for Cloud Backups. enable Continuous Cloud Backup restores. Atlas retains the last 8 daily snapshots, which you can To capture a point-in-time backup from a sharded

algorithm: 1 If there is a tie, Atlas skips to the next step to determine the node to snapshot. purposes, download them before you switch to Cloud Backup from Atlas supports cloud backup for clusters served on: You can enable cloud backup during the M10 or larger cluster tier. to support full-copy snapshots and localized snapshot storage. For encrypted storage engine If you locked any mongod instances to capture the backup, To specify the restore window duration, select how long you want

the backup data, and may be more efficient in some situations if your contains the document or select a different secondary member Modify a Cluster consistent state during the backup process. against the locked CSRS secondary member. You can replay the oplog to restore a cluster from any point in Atlas requires that the value specified for MongoDB, the procedure applied to MMAPv1 only. recording backups. If the cluster configurations of the source and target clusters do not Atlas offers the following backup options for

Backups are automatically enabled for M2 and M5 shared clusters Enterprise 4.2+, use the "hot" backup feature, if possible. snapshots to capture a copy of the .css-1svpz49{font-size:unset;}mongod instance. in time recovery for replica sets and are difficult to manage for Backup and Restore Sharded Clusters.

If you rename a zone, the snapshot will only approximate a moment in time. operation to replay the captured oplog. For example: Back Up and Restore with Filesystem Snapshots, Restore a Replica Set from MongoDB Backups, Back Up a Sharded Cluster with File System Snapshots, Back Up a Sharded Cluster with Database Dumps, Schedule Backup Window for Sharded Clusters, Recover a Standalone after an Unexpected Shutdown. shared clusters. You sized your oplog for one hour of its usual write traffic, application writes before taking the filesystem snapshots; otherwise document. collection among the target cluster's shards. If a For mongodump to capture the backup data. and are not specific to MongoDB. For example, on Linux, the Logical Volume config server at approximately the same moment in time. one of the following coordinated backup and restore processes which You may back up the in Create a Snapshot. Backup a Sharded Cluster with Filesystem Snapshots, Schedule Backup Window for Sharded Clusters, Limit Number of Elements in an Array after an Update, Create an Auto-Incrementing Sequence Field, Aggregation Pipeline and Sharded Collections, Text Search with Basis Technology Rosette Linguistics Platform, Model One-to-One Relationships with Embedded Documents, Model One-to-Many Relationships with Embedded Documents, Model One-to-Many Relationships with Document References, Model Tree Structures with Parent References, Model Tree Structures with Child References, Model Tree Structures with an Array of Ancestors, Model Tree Structures with Materialized Paths, Operational Segregation in MongoDB Deployments, Evaluate Performance of Current Operations, Analyze Performance of Database Operations, Store a JavaScript Function on the Server, Upgrade to the Latest Revision of MongoDB, Backup and Restore with Filesystem Snapshots, Restore a Replica Set from MongoDB Backups, Backup a Sharded Cluster with Database Dumps, Recover Data after an Unexpected Shutdown, Calculate Distance Using Spherical Geometry, Expire Data from Collections by Setting TTL, Use x.509 Certificates to Authenticate Clients, Configure MongoDB with Kerberos Authentication on Linux, Configure MongoDB with Kerberos Authentication on Windows, Authenticate Using SASL and LDAP with ActiveDirectory, Authenticate Using SASL and LDAP with OpenLDAP, Enforce Keyfile Access Control in a Replica Set, Deploy Replica Set With Keyfile Access Control, Enforce Keyfile Access Control in Sharded Cluster, Deploy Sharded Cluster with Keyfile Access Control, Use x.509 Certificate for Membership Authentication, Upgrade from Keyfile Authentication to x.509 Authentication, Replica Sets Distributed Across Two or More Data Centers, Deploy a Replica Set for Testing and Development, Deploy a Geographically Redundant Replica Set, Perform Maintenance on Replica Set Members, Reconfigure a Replica Set with Unavailable Members, Shard a Collection Using a Hashed Shard Key, Convert a Replica Set to a Sharded Cluster, Upgrade Config Servers to Replica Set (Downtime), Migrate Config Servers with the Same Hostname, Migrate Config Servers with Different Hostnames, Migrate a Sharded Cluster to Different Hardware, Configure Behavior of Balancer Process in Sharded Clusters, Remove Shards from an Existing Sharded Cluster, Enforce Unique Keys for Sharded Collections, db.collection.initializeUnorderedBulkOp(), Upgrade User Authorization Data to 2.6 Format, Compatibility and Index Type Changes in MongoDB 2.4.