> 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 A recovery plan is only worth it 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 truly work, without interrupting production or altering the plan. It is a full failover test 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 finished, the **drill environment is deleted**, leaving no dangling resources. ### What it is useful for * **Validate** that the plan recovers what you expect before you actually need it. * **Generate evidence**: the drill leaves useful reporting for auditing, security, and compliance. > #### 📘 A DR that isn't tested is an assumption > > Many recoveries fail right on disaster day, because of a detail nobody checked. > > Running drills periodically turns your plan into something demonstrable: you don't just say you recover, you show it with reports. ### Where to go next * The real operation that the drill rehearses: [Failover and failback.](/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md) * What is replicated and how often: [The replica.](/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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/drills.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.