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

# Drills

How to test the recovery plan without affecting production and what evidence it leaves you.

A recovery plan only matters if you know it works. The **drill** (drill) lets you test it without touching the real environment.

### What is a drill

The drill brings up the replicated environment **in parallel**, to verify that recovery would actually work, without interrupting production or changing the plan. It is a full failover rehearsal under controlled conditions.

### Why it doesn't affect production

* The test environment uses a **different public IP**, so it doesn't interfere with the real service or redirect your users' traffic.
* When it's finished, the **drill environment is deleted**, without leaving any dangling resources.

### What it helps you with

* **Validate** that the plan restores what you expect, before you actually need it.
* **Generate evidence**: the drill produces useful reports for auditing, security, and compliance.

> #### 📘 An untested DR is an assumption
>
> Many recoveries fail on the very day of the disaster because of a detail nobody checked.
>
> Running drills regularly turns your plan into something demonstrable: you don't just say you can recover, you show it with reports.

### Where to follow

* The real operation the drill rehearses: [Failover and failback.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md)
* What is replicated and how often: [Replication.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/the-replica.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/drills.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.
