> 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/servicios-cloud-disaster-recovery-el-plan.md).

# Plans and Blocks

Every plan you create appears in **My plans** and is represented with three blocks that summarize at a glance what you protect, how, and where. For the concept, go to [What is Disaster Recovery?](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/what-it-is.md)

### The three blocks of the plan

| Block         | What it shows                                                         |
| ------------- | --------------------------------------------------------------------- |
| Primary site  | The source subscription you protect, its status, and its zone         |
| Replica       | The failover mode, the number of copies, and the configured frequency |
| Recovery site | The destination environment kept in the other zone, and its status    |

Reading the plan from left to right is reading the flow: where the replica comes from, with which policy it travels, and where it remains ready to be activated.

### Statuses

While the plan is being prepared, you'll see it in configuration status; when the replica is operational, the plan protects the environment.

| Status      | What it means                                                         |
| ----------- | --------------------------------------------------------------------- |
| Configuring | The plan is being prepared and the first replica has not yet finished |
| Active      | The source subscription is operational as Primary site                |

> #### 🚧 Pending statuses to complete
>
> We collect here the statuses shown by the panel today. We will complete the list with all possible statuses before publishing.<br>

### Events and notifications

The Disaster Recovery subscription records what happens in its section of **Events**, where you track the progress of replicas, failovers, and drills. It's the place to look when you want to know what has happened with a plan.

### Where to follow

* What you configure in the replica: [Replication parameters.](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/replication-parameters.md)
* What is copied from the environment: [What is replicated.](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/what-gets-replicated.md)


---

# 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/servicios-cloud-disaster-recovery-el-plan.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.
