High-level steps involved in the Restore and Recovery process
Pre-restore
The current topology and configuration of the MongoDB cluster is gathered.
The following validations are performed:
The restore and recovery of a replica set or a standalone MongoDB cluster is targeted to a single node only.
Restore and recovery is not targeted to an Aribter node.
Restore of multiple shard's data is not targeted to a single shard.
Whether the option is enabled.
The target cluster is shutdown and the WiredTigerLogs files that are present in the journal folder at the database path are removed.
Restore
The data moves in parallel streams.
Post-restore or recovery
The target cluster's configuration parameters along with the configuration parameters of the source cluster that was backed up are used to start the MongoDB services.
The mongod services are started on each node on a local host in maintenance mode without enabling the authentication.
The minimum required operations are run in the maintenance mode on the local host, the service is shutdown and restarted with authentication.
Sharding, replication, and authentication is enabled and the MongoDB cluster is initiated.
The oplogs are replayed on the MongoDB cluster nodes.
Note:
The restored node is now the primary node in the replica set.
Only the nodes that are backed up and selected for recovery are recovered. The other cluster members must be added manually to the recovered cluster.
You must select the .