> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/zh/backup-dr.md).

# 备份与灾难恢复

快照、同步作业、恢复和灾难恢复指南。

* [配置用于导出虚拟机的卷](/knowledge-base/zh/backup-dr/configuring-a-vm-export-volume.md) — 如何配置 VergeOS NAS VM 导出卷以用于备份目的，包括 CIFS/NFS 共享、计划导出和同步……
* [导出虚拟机](/knowledge-base/zh/backup-dr/exporting-a-virtual-machine.md) — 了解如何从 VergeOS 导出虚拟机，并将其磁盘下载为 .raw 文件，以便在其他虚拟化环境中使用。
* [从远程系统快照恢复单个虚拟机](/knowledge-base/zh/backup-dr/recovering-a-single-vm-from-a-remote-cloud-snapshot.md) — 使用 VergeOS 站点同步和同步回传，从远程系统快照恢复单个虚拟机的分步说明……
* [RHEL 9 系列虚拟机在克隆或快照还原后无法启动](/knowledge-base/zh/backup-dr/rhel9-boot-failure-clone-snapshot-restore.md) — 如何修复 RHEL 9 系列虚拟机（AlmaLinux、Rocky Linux、CentOS Stream）在 VergeOS 中克隆或还原快照后出现的启动失败问题……
* [在 VergeOS 上设置 Storware](/knowledge-base/zh/backup-dr/setup-storware-vergeos.md) — 在 VergeOS 上为虚拟机保护设置 Storware 的指南，包括 NAS 服务配置和 NFS 设置。
* [快照同步错误说明](/knowledge-base/zh/backup-dr/snapshot-synchronization-errors-explained.md) — 参考指南，解释常见的 VergeOS 站点同步错误消息、其原因以及针对快照同步的建议解决方案……
* [VMware-备份-DR-指南](/knowledge-base/zh/backup-dr/vmwarebackupdrguide.md) — 在 VergeOS 中设置 VMware 备份和灾难恢复的综合指南，包括创建 VMware 服务、配置备份……


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/knowledge-base/zh/backup-dr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
