Restore a Self-Managed Sharded Cluster恢复自我管理的分片群集

Restore the CSRS primary mongod data files.还原CSRS主mongod数据文件。

Select the tab that corresponds to your preferred backup method:选择与首选备份方法对应的选项卡：

Drop the local database.删除local数据库。

Use db.dropDatabase() to drop the local database:使用db.dropDatabase()删除local数据库：

use local
db.dropDatabase()

Insert the filtered file list into the local database.将筛选后的文件列表插入本地数据库。

This step is only required if you are restoring from a namespace-filtered snapshot.仅当您从命名空间筛选的快照进行还原时，才需要此步骤。

For each shard, locate the filtered file list with the following name format: <shardRsID>-filteredFileList.txt. This file contains a list of JSON objects with the following format:对于每个分片，使用以下名称格式找到筛选后的文件列表：<shardRsID>-filteredFileList.txt。此文件包含以下格式的JSON对象列表：

{
   "filename":"file1",
   "ns":"sampleDb1.sampleCollection1",
   "uuid": "3b241101-e2bb-4255-8caf-4136c566a962"
}

Add each JSON object from each shard file to a new db.systems.collections_to_restore collection in your local database. 将每个分片文件中的每个JSON对象添加到local数据库中的新db.systems.collections_to_restore集合中。You can ignore entries with empty ns or uuid fields. When inserting entries, the uuid field must be inserted as type UUID().您可以忽略ns或uuid字段为空的条目。插入条目时，uuid字段必须以UUID()类型插入。

Run the filtered file restore command.运行筛选文件还原命令。

This step is only required if you are restoring from a namespace-filtered snapshot.仅当您从命名空间筛选的快照进行还原时，才需要此步骤。

After inserting all entries, run the following commands:插入所有条目后，运行以下命令：

use admin
db.runCommand({"_configsvrRunRestore":1})

For any planned or completed shard hostname or replica set name changes, update the metadata in config.shards.对于任何计划或已完成的分片主机名或副本集名称更改，请更新config.shards中的元数据。

You can skip this step if all of the following are true:如果以下所有条件都为真，则可以跳过此步骤：

• No shard member host machine hostname has or will change during this procedure.在此过程中，没有分片成员主机主机名已经或将要更改。
• No shard replica set name has or will change during this procedure.在此过程中，没有或不会更改分片副本集名称。

Issue the following find() method on the shards collection in the Config Database. 对配置数据库中的shards集合发出以下find()方法。Replace <shardName> with the name of the shard. 将<shardName>替换为分片的名称。By default the shard name is its replica set name. 默认情况下，分片名称是其副本集名称。If you added the shard using the addShard command and specified a custom name, you must specify that name to <shardName>.如果您使用addShard命令添加了分片并指定了自定义namename<shardName>。

use config
db.shards.find( { "_id" : "<shardName>" } )

This operation returns a document that resembles the following:此操作返回一个类似于以下内容的文档：

{
   "_id" : "shard1",
   "host" : "myShardName/alpha.example.net:27018,beta.example.net:27018,charlie.example.net:27018",
   "state" : 1
}

Use the updateOne() method to update the hosts string to reflect the planned replica set name and hostname list for the shard. 使用updateOne()方法更新hosts字符串，以反映分片的计划副本集名称和主机名列表。For example, the following operation updates the host connection string for the shard with "_id" : "shard1":例如，以下操作使用"_id" : "shard1"更新分片的host连接字符串：

db.shards.updateOne(
  { "_id" : "shard1" },
  { $set : { "host" : "myNewShardName/repl1.example.net:27018,repl2.example.net:27018,repl3.example.net:27018" } }
)

Repeat this process until all shard metadata accurately reflects the planned replica set name and hostname list for each shard in the cluster.重复此过程，直到所有分片元数据准确反映集群中每个分片的计划副本集名称和主机名列表。

use config
db.shards.find({})

Restart the mongod as a new single-node replica set.将mongod重新启动为新的单节点副本集。

Shut down the mongod. Uncomment or add the following configuration file options:关掉mongod。取消注释或添加以下配置文件选项：

replication:
  replSetName: myNewCSRSName
sharding:
  clusterRole: configsvr

If you want to change the replica set name, you must update the replSetName field with the new name before proceeding.如果要更改副本集名称，则必须在继续之前用新名称更新replSetName字段。

Start the mongod with the updated configuration file:使用更新的配置文件启动mongod：

mongod --config /path/to/mongodb/mongod.conf

If you have mongod configured to run as a system service, start it using the recommended process for your system service manager.如果您已将mongod配置为作为系统服务运行，请使用系统服务管理器推荐的流程启动它。

After the mongod starts, connect to it using the mongo shell.mongod启动后，使用mongo shell连接到它。

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

Initiate the replica set using rs.initiate() with the default settings.使用默认设置的rs.initiate()启动副本集。

rs.initiate()

Once the operation completes, use rs.status() to check that the member has become the primary.操作完成后，使用rs.status()检查成员是否已成为主成员。

Add additional replica set members.添加其他副本集成员。

For each replica set member in the CSRS, start the mongod on its host machine. 对于CSRS中的每个副本集成员，在其主机上启动mongod。Once you have started up all remaining members of the cluster successfully, connect a mongo shell to the primary replica set member. 成功启动集群的所有剩余成员后，将mongo shell连接到主副本集成员。From the primary, use the rs.add() method to add each member of the replica set. 从主副本开始，使用rs.add()方法添加副本集的每个成员。Include the replica set name as the prefix, followed by the hostname and port of the member's mongod process:将副本集名称作为前缀，后跟成员mongod进程的主机名和端口：

rs.add("config2.example.net:27019")
rs.add("config3.example.net:27019")

If you want to add the member with specific replica member configuration settings, you can pass a document to rs.add() that defines the member hostname and any members settings your deployment requires.如果要添加具有特定副本member配置设置的成员，可以将一个文档传递给rs.add()，该文档定义了成员主机名和部署所需的任何members设置。

rs.add(
 {
   "host" : "config2.example.net:27019",
   priority: <int>,
   votes: <int>,
   tags: <int>
 }
)

Each new member performs an initial sync to catch up to the primary. Depending on factors such as the amount of data to sync, your network topology and health, and the power of each host machine, initial sync may take an extended period of time to complete.每个新成员执行rs.add()初始同步以赶上主成员。根据要同步的数据量、网络拓扑和健康状况以及每台主机的功率等因素，初始同步可能需要很长时间才能完成。

The replica set may elect a new primary while you add additional members. 在添加其他成员时，副本集可能会选择一个新的主副本。Use rs.status() to identify which member is the current primary. 使用rs.status()确定哪个成员是当前的主成员。You can only run rs.add() from the primary.您只能从主服务器运行rs.add()。

Configure any additional required replication settings.配置任何其他所需的复制设置。

The rs.reconfig() method updates the replica set configuration based on a configuration document passed in as a parameter. rs.reconfig()方法根据作为参数传入的配置文档更新副本集配置。You must run reconfig() against the primary member of the replica set.您必须对副本集的主要成员运行reconfig()。

Reference the original configuration file output of the replica set as identified in step A. Review Replica Set Configurations and apply settings as needed.参考步骤A中标识的副本集的原始配置文件输出。查看副本集配置并根据需要应用设置。

Restore the shard primary mongod data files.恢复分片主mongod数据文件。

Select the tab that corresponds to your preferred backup method:选择与首选备份方法对应的选项卡：

Create a temporary user with the __system role.创建一个具有__system角色的临时用户。

During this procedure you will modify documents in the admin.system.version collection. 在此过程中，您将修改admin.system.version集合中的文档。For clusters enforcing authentication, only the __system role grants permission to modify this collection. 对于强制身份验证的集群，只有__system角色授予修改此集合的权限。You can skip this step if the cluster does not enforce authentication.如果集群不强制身份验证，则可以跳过此步骤。

1. Authenticate as a user with the userAdmin role on the admin database or userAdminAnyDatabase role:使用admin数据库上的userAdmin角色或userAdminAnyDatabase角色作为用户进行身份验证：

   use admin
   db.auth("myUserAdmin","mySecurePassword")

2. Create a user with the __system role:创建一个具有__system角色的用户：

   db.createUser(
     {
       user: "mySystemUser",
       pwd: "<replaceMeWithAStrongPassword>",
       roles: [ "__system" ]
     }
   )

   Passwords should be random, long, and complex to ensure system security and to prevent or delay malicious access.密码应该是随机的、长的和复杂的，以确保系统安全，防止或延迟恶意访问。

3. Authenticate as the privileged user:以权限用户身份进行身份验证：

   db.auth("mySystemUser","<replaceMeWithAStrongPassword>")

Drop the local database.删除local数据库。

Use db.dropDatabase() to drop the local database:使用db.dropDatabase()删除local数据库：

use local
db.dropDatabase()

Remove the minOpTimeRecovery document from the admin.system.versions collection.从admin.system.versions集合中删除minOpTimeRecovery文档。

To update the sharding internals, issue the following deleteOne() method on the system.version collection in the admin database:要更新分片内部，请在admin数据库中的system.version集合上发出以下deleteOne()方法：

use admin
db.system.version.deleteOne( { _id: "minOpTimeRecovery" } )

Optional: For any CSRS hostname or replica set name changes, update shard metadata in each shard's identity document.可选：对于任何CSRS主机名或副本集名称更改，请更新每个分片标识文档中的分片元数据。

You can skip this step if all of the following are true:如果以下所有条件都为真，则可以跳过此步骤：

• The hostnames for any CSRS host did not change during this procedure.在此过程中，任何CSRS主机的主机名都没有更改。
• The CSRS replica set name did not change during this procedure.在此过程中，CSRS副本集名称没有更改。

The system.version collection on the admin database contains metadata related to the shard, including the CSRS connection string. If either the CSRS name or any member hostnames changed while restoring the CSRS, you must update this metadata.admin数据库上的system.version集合包含与分片相关的元数据，包括CSRS连接字符串。如果在还原CSRS时更改了CSRS名称或任何成员主机名，则必须更新此元数据。

Issue the following find() method on the system.version collection in the admin database:对admin数据库中的system.version集合发出以下find()方法：

use admin
db.system.version.find( {"_id" : "shardIdentity" } )

The find() method returns a document that resembles the following:find()方法返回一个类似于以下内容的文档：

{
  "_id" : "shardIdentity",
  "clusterId" : ObjectId("2bba123c6eeedcd192b19024"),
  "shardName" : "shard1",
  "configsvrConnectionString" : "myCSRSName/alpha.example.net:27019,beta.example.net:27019,charlie.example.net:27019" }

The following updateOne() method updates the document such that the host string represents the most current CSRS connection string:以下updateOne()方法更新文档，使host字符串表示最新的CSRS连接字符串：

db.system.version.updateOne(
  { "_id" : "shardIdentity" },
  { $set :
    { "configsvrConnectionString" : "myNewCSRSName/config1.example.net:27019,config2.example.net:27019,config3.example.net:27019"}
  }
)

Restart the mongod as a new single-node replica set.将mongod重新启动为新的单节点副本集。

Shut down the mongod. Uncomment or add the following configuration file options:关掉mongod。取消注释或添加以下配置文件选项：

replication:
  replSetName: myNewShardName
sharding:
  clusterRole: shardsvr

If you want to change the replica set name, you must update the replSetName field with the new name before proceeding.如果要更改副本集名称，则必须在继续之前用新名称更新replSetName字段。

Start the mongod with the updated configuration file:使用更新的配置文件启动mongod：

mongod --config /path/to/mongodb/mongod.conf

If you have mongod configured to run as a system service, start it using the recommended process for your system service manager.如果您已将mongod配置为作为系统服务运行，请使用系统服务管理器推荐的流程启动它。

After the mongod starts, connect to it using the mongo shell.mongod启动后，使用mongo shell连接到它。

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

Initiate the replica set using rs.initiate() with the default settings.使用默认设置的rs.initiate()启动副本集。

rs.initiate()

Once the operation completes, use rs.status() to check that the member has become the primary.操作完成后，使用rs.status()检查成员是否已成为主成员。

Add additional replica set members.添加其他副本集成员。

For each replica set member in the shard replica set, start the mongod on its host machine. Once you have started up all remaining members of the cluster successfully, connect a mongo shell to the primary replica set member. 对于分片副本集中的每个副本集成员，在其主机上启动mongod。成功启动集群的所有剩余成员后，将mongo shell连接到主副本集成员。From the primary, use the rs.add() method to add each member of the replica set. 从主副本开始，使用rs.add()方法添加副本集的每个成员。Include the replica set name as the prefix, followed by the hostname and port of the member's mongod process:将副本集名称作为前缀，后跟成员mongod进程的主机名和端口：

rs.add("repl2.example.net:27018")
rs.add("repl3.example.net:27018")

If you want to add the member with specific replica member configuration settings, you can pass a document to rs.add() that defines the member hostname and any members settings your deployment requires.如果要添加具有特定副本member配置设置的成员，可以将一个文档传递给rs.add()，该文档定义了成员主机名和部署所需的任何members设置。

rs.add(
 {
   "host" : "repl2.example.net:27018",
   priority: <int>,
   votes: <int>,
   tags: <int>
 }
)

Each new member performs an initial sync to catch up to the primary. Depending on factors such as the amount of data to sync, your network topology and health, and the power of each host machine, initial sync may take an extended period of time to complete.每个新成员执行初始同步以赶上主成员。根据要同步的数据量、网络拓扑和健康状况以及每台主机的功率等因素，初始同步可能需要很长时间才能完成。

The replica set may elect a new primary while you add additional members. Use rs.status() to identify which member is the current primary. 在添加其他成员时，副本集可能会选择一个新的主副本。使用rs.status()确定哪个成员是当前的主成员。You can only run rs.add() from the primary.您只能从主服务器运行rs.add()。

Configure any additional required replication settings.配置任何其他所需的复制设置。

The rs.reconfig() method updates the replica set configuration based on a configuration document passed in as a parameter. rs.reconfig()方法根据作为参数传入的配置文档更新副本集配置。You must run reconfig() against the primary member of the replica set.您必须对副本集的主要成员运行reconfig()。

Reference the original configuration file output of the replica set as identified in step A. Review Replica Set Configurations and apply settings as needed.参考步骤“A. 查看副本集配置并根据需要应用设置”中标识的副本集的原始配置文件输出。

Remove the temporary privileged user.删除临时权限用户。

For clusters enforcing authentication, remove the privileged user created earlier in this procedure:对于强制身份验证的集群，请删除此过程前面创建的权限用户：

1. Authenticate as a user with the userAdmin role on the admin database or userAdminAnyDatabase role:使用admin数据库上的userAdmin角色或userAdminAnyDatabase角色作为用户进行身份验证：

   use admin
   db.auth("myUserAdmin","mySecurePassword")

2. Delete the privileged user:删除权限用户：

   db.removeUser("mySystemUser")