恢复 MarkLogic 服务器问题
Recovering MarkLogic server Issue
我们有一个 MarkLogic 9.x 服务器和 4.1.x 数据中心，我们想练习灾难恢复。 activity 假设服务器完全不可恢复，我们需要建立一个全新的服务器，全新安装 ML Server & Data Hub，然后从备份中恢复所有数据库。将数据库复制到生产中的另一台服务器不是一种选择。
查看 ML doco 和知识库，我无法找到如何完成此操作。
可以吗？如果可以，是否还需要特定顺序的数据库还原或不需要还原的数据库？假设服务器上的所有数据库在服务器丢失之前都有可用的完整备份。
恢复备份相当简单，假设您在灾难恢复群集中具有相同的拓扑结构和林命名约定。
Admin Guide: Backing Up and Restoring a Database
中描述了启动备份和恢复的过程
您没有提到这些是完整备份、增量备份，还是日志存档是否已启用和可用，但在 Concepts Guide: High Availability and Disaster Recovery
中进行了讨论
MarkLogic supports online backups and restores, so you can protect and restore your data without bringing the system offline or halting queries or updates. Backups are initiated via administration calls, either via the web console or an XQuery script. You specify a database to backup and a target location. Backing up a database backs up its configuration files, all the forests in the database, as well as the corresponding security and schemas databases. It's particularly important to backup the security database because MarkLogic tracks role identifiers as xs:long values and the backup forest data can't be read without the corresponding roles existing in the security database.
You can also choose to selectively backup an individual forest instead of an entire database. That's a convenient option if only the data in one forest is changing.
The topics in this section are as follows:
你会想要恢复你的内容数据库（也许还有模块，但应该有可用的代码并且能够部署），但不建议恢复一些内置数据库，例如应用程序服务：
https://help.marklogic.com/Knowledgebase/Article/View/why-shouldnt-you-restore-the-app-services-database-from-another-cluster
Best Practice:
The "App-Services" database is one of the default MarkLogic databases, used to track configuration file timestamp information local to the cluster on which it resides. It is not recommended to restore "App-Services" databases across MarkLogic clusters.
以及关于安全数据库的额外预防措施：
https://help.marklogic.com/Knowledgebase/Article/View/restoring-security-database
Note: It is recommended that a backup of the security database from the new cluster is created and saved before performing the restore of a Security database from a different cluster.
我们有一个 MarkLogic 9.x 服务器和 4.1.x 数据中心，我们想练习灾难恢复。 activity 假设服务器完全不可恢复，我们需要建立一个全新的服务器，全新安装 ML Server & Data Hub，然后从备份中恢复所有数据库。将数据库复制到生产中的另一台服务器不是一种选择。
查看 ML doco 和知识库，我无法找到如何完成此操作。
可以吗？如果可以，是否还需要特定顺序的数据库还原或不需要还原的数据库？假设服务器上的所有数据库在服务器丢失之前都有可用的完整备份。
恢复备份相当简单，假设您在灾难恢复群集中具有相同的拓扑结构和林命名约定。
Admin Guide: Backing Up and Restoring a Database
中描述了启动备份和恢复的过程您没有提到这些是完整备份、增量备份，还是日志存档是否已启用和可用，但在 Concepts Guide: High Availability and Disaster Recovery
中进行了讨论MarkLogic supports online backups and restores, so you can protect and restore your data without bringing the system offline or halting queries or updates. Backups are initiated via administration calls, either via the web console or an XQuery script. You specify a database to backup and a target location. Backing up a database backs up its configuration files, all the forests in the database, as well as the corresponding security and schemas databases. It's particularly important to backup the security database because MarkLogic tracks role identifiers as xs:long values and the backup forest data can't be read without the corresponding roles existing in the security database.
You can also choose to selectively backup an individual forest instead of an entire database. That's a convenient option if only the data in one forest is changing.
The topics in this section are as follows:
你会想要恢复你的内容数据库（也许还有模块，但应该有可用的代码并且能够部署），但不建议恢复一些内置数据库，例如应用程序服务： https://help.marklogic.com/Knowledgebase/Article/View/why-shouldnt-you-restore-the-app-services-database-from-another-cluster
Best Practice: The "App-Services" database is one of the default MarkLogic databases, used to track configuration file timestamp information local to the cluster on which it resides. It is not recommended to restore "App-Services" databases across MarkLogic clusters.
以及关于安全数据库的额外预防措施： https://help.marklogic.com/Knowledgebase/Article/View/restoring-security-database
Note: It is recommended that a backup of the security database from the new cluster is created and saved before performing the restore of a Security database from a different cluster.