> 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/concepts/what-it-is.md).

# What Is Disaster Recovery?

A complete replica of your Servers or Remote Desktop subscription in the other region, ready to activate if the primary environment goes down.

Disaster Recovery replicates a Servers or Remote Desktop subscription in the other region, ready to be activated if the primary environment becomes unavailable. If the subscription is in Madrid, the replica is stored in Paris; if it is in Paris, the replica is stored in Madrid. It is our business continuity layer for your customers' critical environments.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fx1JkoFSE7EM9zBrMlUDa%2Fdiagram-dr-replication-zones.png?alt=media&amp;token=a4e33990-2007-48a7-921d-2acd517298a2" alt="Diagrama de Disaster Recovery: el Primary site en producción replica cada 1-24 h al Recovery site, en otra zona y en espera"><figcaption><p>Disaster Recovery maintains a replica of your environment in the other region. If the primary site goes down, you activate failover and operate from the recovery site</p></figcaption></figure>

### Disaster Recovery is not a backup

This distinction is important because they solve different problems.

|                           | Backup                                | Disaster Recovery                                                                 |
| ------------------------- | ------------------------------------- | --------------------------------------------------------------------------------- |
| What it protects          | The data                              | The entire system, ready to run                                                   |
| What it stores            | Copies of files and disks             | Complete replicated infrastructure (compute, disks, networks, IPs, firewall, VPN) |
| How it recovers           | By restoring the data, step by step   | By activating the replicated environment                                          |
| Time to resume operations | Slow: the environment must be rebuilt | Fast: the environment is already set up                                           |

> #### 📘 Backup and Disaster Recovery complement each other
>
> Backup gives you back your data. Disaster Recovery restores your operations: the machine, its network, configuration and service, ready to resume work. In critical environments, one is not a substitute for the other.

### What is replicated

Disaster Recovery doesn't just copy the data. It replicates the elements needed to get the environment running again just as it was.

* Instances and their compute configuration.
* Disks and their contents.
* Networks and subnets.
* Private IPs, which are preserved in the replica. Public IPs are not migrated: they are different in the other region.
* The firewall, port forwarding rules and VPN.

You can adjust the scope: the source is a Servers subscription, with the option to **exclude specific machines or disks** that you don't need to replicate.

### How it fits in

Disaster Recovery builds on what you already have and creates its own subscription.

* It protects [Servers](https://docs.plenit.com/docs-en/productos/servers.md) and [Remote Desktop subscriptions.](https://docs.plenit.com/docs-en/productos/remote-desktop.md)
* It replicates the environment in the other region: Paris if the source is in Madrid, and Madrid if it is in Paris.
* It is managed through its own Disaster Recovery subscription, with its own card on the dashboard.

### What you decide and what we do

| You decide                                                | We do                                                             |
| --------------------------------------------------------- | ----------------------------------------------------------------- |
| Which subscription to protect and what to exclude         | Replicate the environment in the destination region               |
| Replication frequency and which recovery points to retain | Maintain the contingency infrastructure                           |
| When to activate failover and failback                    | Recreate compute, networking and configuration at the destination |
| When to run a drill                                       | Generate service events and notifications                         |

### You activate failover

> #### 🚧 Not automatic high availability
>
> Disaster Recovery drastically reduces recovery time, but it does not switch over automatically.
>
> You decide when to move services to the standby site (failover) and when to return to the original environment (failback).
>
> It’s continuity ready to activate, not automatic failover.

### Where to go next

* What gets copied and how often: [Replication.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/the-replica.md)
* Switching to the standby site and back: [Failover and failback.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md)
* Testing the plan without affecting production: [Drills.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/drills.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/concepts/what-it-is.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.
