> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles.md).

# Details

Detailed Disaster Recovery information: the plan, replication parameters, what is replicated, and requirements and limits.

The Disaster Recovery reference, with details of the plan, replication parameters, and service requirements and limits.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>The plan</strong></td><td>How a recovery plan is structured and what it includes.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/servicios-cloud-disaster-recovery-el-plan.md">Plans and Blocks</a></td></tr><tr><td><strong>Replication parameters</strong></td><td>The frequencies, number of copies, and available failover modes.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/replication-parameters.md">Replication Parameters</a></td></tr><tr><td><strong>What is replicated</strong></td><td>Details of which infrastructure elements are replicated and which you can exclude.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/what-gets-replicated.md">What Is Replicated</a></td></tr><tr><td><strong>Requirements and limits</strong></td><td>The prerequisites and service limits.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/requirements-and-limits.md">Requirements and Limits</a></td></tr></tbody></table>


---

# 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.plenit.com/docs-en/productos/disaster-recovery/detalles.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.
