Restore a Self-Managed Replica Set from MongoDB Backups从MongoDB备份还原自我管理副本集

Obtain backup MongoDB Database files.获取备份MongoDB数据库文件。

The backup files may come from a file system snapshot. The MongoDB Cloud Manager produces MongoDB database files for stored snapshots and point in time snapshots. 备份文件可能来自文件系统快照。MongoDB云管理器为存储的快照和时间点快照生成MongoDB数据库文件。For Ops Manager, an on-premises solution available in MongoDB Enterprise Advanced, see also the Ops Manager Backup overview.对于MongoDB Enterprise Advanced中提供的本地解决方案Ops Manager，另请参阅Ops Manager备份概述。

Considerations for Encrypted Storage Engines加密存储引擎的注意事项

For encrypted storage engines that use AES256-GCM encryption mode, AES256-GCM requires that every process use a unique counter block value with the key.对于使用AES256-GCM加密模式的加密存储引擎，AES256-GCM要求每个进程在键中使用唯一的计数器块值。For encrypted storage engine configured with AES256-GCM cipher: 对于配置了AES256-GCM密码的加密存储引擎：

• Restoring from Hot Backup从热备份恢复

  Starting in 4.2, if you restore from files taken via "hot" backup (i.e. the mongod is running), MongoDB can detect "dirty" keys on startup and automatically rollover the database key to avoid IV (Initialization Vector) reuse.从4.2开始，如果您从通过“热”备份（即mongod正在运行）获取的文件进行还原，MongoDB可以在启动时检测“脏”键，并自动滚动数据库键以避免IV（初始化向量）重用。

• Restoring from Cold Backup从冷备份恢复

  However, if you restore from files taken via "cold" backup (i.e. the mongod is not running), MongoDB cannot detect "dirty" keys on startup, and reuse of IV voids confidentiality and integrity guarantees.但是，如果您从通过“冷”备份获取的文件中还原（即mongod未运行），MongoDB在启动时无法检测到“脏”键，重复使用IV会使机密性和完整性保证失效。

  Starting in 4.2, to avoid the reuse of the keys after restoring from a cold filesystem snapshot, MongoDB adds a new command-line option --eseDatabaseKeyRollover. 从4.2开始，为了避免从冷文件系统快照恢复后重用键，MongoDB添加了一个新的命令行选项--eseDatabaseKeyRollover。When started with the --eseDatabaseKeyRollover option, the mongod instance rolls over the database keys configured with AES256-GCM cipher and exits.当使用--eseDatabaseKeyRollover选项启动时，mongod实例会滚动使用AES256-GCM密码配置的数据库键并退出。

Drop the local database if it exists in the backup.如果备份中存在local数据库，请删除该数据库。

If you are restoring from a filesystem backup (or any backup with the local database), drop the local database.如果要从文件系统备份（或任何具有local数据库的备份）还原，请删除local数据库。

mongod --dbpath /data/db <startup options>

use local
db.dropDatabase()

Start a new single-node replica set.启动新的单节点副本集。

Start a mongod instance as a new single-node replica set. 将mongod实例作为新的单节点副本集启动。Specify the path to the backup data files with --dbpath option and the replica set name with the --replSet option. 使用--dbpath选项指定备份数据文件的路径，使用--replSet选项指定副本集名称。For config server replica set (CSRS), include the --configsvr option. 对于配置服务器副本集（CSRS），请包含--configsvr选项。Include any other options as appropriate for your deployment.根据部署情况，包括任何其他选项。

You must also specify the same startup options that were used when the snapshot was created.您还必须指定创建快照时使用的启动选项。

mongod --dbpath /data/db --replSet <replName> <startup options>

Connect mongosh to the mongod instance.将mongosh连接到mongod实例。

From the same machine where one of the mongod is running (in this tutorial, mongodb0.example.net), start mongosh. 在运行mongod的同一台机器上（在本教程中为mongodb0.example.net），启动mongosh。To connect to the mongod listening to localhost on the default port of 27017, simply issue:要连接到默认端口27017上监听本地主机的mongod，只需发出：

mongosh

Depending on your path, you may need to specify the path to the mongosh binary.根据路径，您可能需要指定mongosh二进制文件的路径。

If your mongod is not running on the default port, specify the --port option for mongosh.如果mongod没有在默认端口上运行，请为mongosh指定--port选项。

Initiate the new replica set.启动新的副本集。

Use rs.initiate() on one and only one member of the replica set:对副本集的一个且仅一个成员使用rs.initiate()：

rs.initiate( {
   _id : <replName>,
   members: [ { _id : 0, host : <host:port> } ]
})

MongoDB initiates a set that consists of the current member and that uses the default replica set configuration.MongoDB启动一个由当前成员组成的集合，该集合使用默认的副本集配置。