> 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/faq.md).

# Frequently Asked Questions

Frequently asked questions about Disaster Recovery: what it is and how it differs from backup, replication, failover and failback, and drills.

Each answer links to the concept, guide, or reference with the details.

<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>What it is and how it differs from backup</strong></td><td>What Disaster Recovery is, how it differs from backup, and what gets replicated.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/what-it-is.md">What Is Disaster Recovery?</a></td></tr><tr><td><strong>Replication</strong></td><td>Frequency, data loss window, recovery points, and what to replicate.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/the-replica.md">The Replica</a></td></tr><tr><td><strong>Failover and failback</strong></td><td>How to switch to the standby site, whether it’s automatic, how traffic is switched, and how to return to the primary site.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md">Failover and Failback</a></td></tr><tr><td><strong>Drills</strong></td><td>How to test the plan without affecting production and why it’s useful.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/drills.md">Drills</a></td></tr></tbody></table>

### What it is and how it differs from backup

<details>

<summary>What is Disaster Recovery?</summary>

It replicates a Servers or Remote Desktop subscription to the other region (Paris if it’s in Madrid, Madrid if it’s in Paris) and keeps it ready to activate if the primary environment becomes unavailable. It’s the business continuity layer for your customers’ critical environments. Learn more in [What is Disaster Recovery?](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/what-it-is.md)

</details>

<details>

<summary>How is it different from backup?</summary>

Backup protects data, which you recover by restoring it step by step. Disaster Recovery replicates the entire infrastructure (compute, disks, networks, IPs, firewall, VPN) and recovers it by activating the replicated environment, which is already set up. Backup gives you your data back; Disaster Recovery restores your operations. For critical environments, they complement each other rather than replace one another.

</details>

<details>

<summary>What exactly gets replicated?</summary>

Instances and their compute configuration, disks and their contents, networks and subnets, private and public IPs, the firewall, port forwarding rules, and the VPN. This means that when you trigger failover, the environment works as it did before. For details, see What gets [replicated?](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/what-gets-replicated.md)

</details>

<details>

<summary>Which services does it work with?</summary>

It works with Servers and Remote Desktop subscriptions. Disaster Recovery builds on what you already have and creates its own subscription.

</details>

### Replication

<details>

<summary>How often is the environment replicated?</summary>

You choose the frequency (every 1, 3, 6, 12, or 24 hours), which defines your data loss window: in the worst case, you would lose changes made since the last replication. We recommend setting it according to how much work your customer can afford to lose, rather than defaulting to the highest frequency. You also choose the start time. Learn more in [Replication.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/the-replica.md)

</details>

<details>

<summary>How many recovery points can I keep?</summary>

From 1 to 24. Each replication creates a recovery point you can return to, and keeping several gives you options for choosing when to recover to; this is essential in the event of ransomware, when the latest point may already be encrypted and you need to go back to an earlier one. For details, see [Replication settings.](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/replication-parameters.md)

</details>

<details>

<summary>Do I have to replicate everything?</summary>

No. You can exclude specific machines or disks from the plan (for example, a temporary data disk or a secondary machine) so that you replicate only what supports the business and keep the replica leaner.

</details>

### Failover and failback

<details>

<summary>How do I switch to the standby environment if the primary one goes down?</summary>

Use failover: services move to the Recovery site, where the replicated environment is already set up and ready to start, making recovery fast. Traffic is redirected according to the plan’s switchover mode. [Learn more in Failover and failback.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md)

</details>

<details>

<summary>Is failover automatic?</summary>

No. Disaster Recovery does not switch over automatically: you decide when to declare a disaster and move to the Recovery site. This gives you control, but it means the plan requires a decision—it doesn’t trigger on its own.

</details>

<details>

<summary>How is traffic redirected to the standby site?</summary>

Through DNS: you change the destination that the service name points to so that it points to the Recovery site’s public IPs. The servers’ private IPs stay the same; the public IPs are different in the other region.

</details>

<details>

<summary>How do I return to the primary environment once it’s restored?</summary>

Use failback. Since you’ve been working in the Recovery site during failover, those are the changes you want to keep: first, the replica is reconfigured in the opposite direction to send the changes back to the Primary site, and only then is it reactivated. This way, you don’t lose the work done during the outage.

</details>

### Drills

<details>

<summary>Can I test the plan without affecting production?</summary>

Yes, with a drill: start the replicated environment in parallel to check that recovery would work, without interrupting production or changing the plan. It uses a different public IP, and the drill environment is deleted when you finish. Learn more in [Drills.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/drills.md)

</details>

<details>

<summary>Why should I run drills?</summary>

To validate that the plan recovers what you expect before you actually need it, and to generate evidence: the drill provides reporting that’s useful for audits, security, and compliance. An untested recovery plan is just an assumption; running it regularly makes it demonstrable.

</details>

### Next steps

<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>Quick Start</strong></td><td>Activate your first plan step by step.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/quickstart.md">Quick Start</a></td></tr><tr><td><strong>Concepts</strong></td><td>Understand the service’s design decisions.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts.md">Concepts</a></td></tr><tr><td><strong>How-to</strong></td><td>Step-by-step guides for configuring and testing your recovery plan.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/how-to.md">How to</a></td></tr><tr><td><strong>Details</strong></td><td>The plan, parameters, and requirements.</td><td><a href="https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles.md">Details</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/faq.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.
