> 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/what-gets-replicated.md).

# What Is Replicated

The environment elements that Disaster Recovery replicates and what you can leave out of the plan

Disaster Recovery replicates the entire subscription infrastructure, not just the data. That is the difference with a backup, which you have explained in[ What is Disaster Recovery?](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/what-it-is.md). Here is the breakdown of what is included.

### Elements that are replicated

| Item                                | Replicated |
| ----------------------------------- | ---------- |
| Compute instances and configuration | Yes        |
| Disks and their contents            | Yes        |
| Networks and subnets                | Yes        |
| Private IPs                         | Yes        |
| public IPs                          | Yes        |
| Firewall                            | Yes        |
| Port forwarding rules               | Yes        |
| VPN                                 | Yes        |

That is why, when failover is activated, the environment works again exactly as it was: the machine, its network, and its configuration are replicated, so they do not need to be rebuilt.

### What you can exclude

Not everything needs protection. You can adjust the scope of the plan by leaving out what does not add value.

| Exclusion        | What is it for                                                       |
| ---------------- | -------------------------------------------------------------------- |
| Per machine (VM) | Leave out secondary servers or ones that do not support the business |
| Per disk         | Leave out temporary or nonessential data disks                       |

> #### 📘 Replicate only what supports the business
>
> Excluding nonessential items keeps the replica lighter and more focused.
>
> Review which machines and disks are truly critical before including everything by default.

### Where to follow

* How often it is replicated and how many recovery points you keep: [Replication parameters.](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/replication-parameters.md)
* How the replicated environment is activated: [Failover and failback.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/failover-and-failback.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/what-gets-replicated.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.
