> 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/how-to/how-to-run-a-drill.md).

# How to Run a Disaster Recovery Drill

Validate your Disaster Recovery plan in an isolated environment without affecting production.

### Prerequisites

Before starting the drill, make sure the following conditions are met:

* **Active plan:** The Disaster Recovery plan must be configured and active.
* **At least one available backup:** At least one previously completed restore point must exist to start the servers.
* **No tasks in progress:** No configuration changes should be in progress, and no actual recovery should be running for the plan at that time.

### Step by step

{% stepper %}
{% step %}

### Select the Disaster Recovery Plan

Go to the Disaster Recovery section of the platform, open the Drills tab, and click the button to start a new drill. Select the plan you want to test.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FFMc0wHmCP2pkebJ2YNzB%2FCAPTURA%201%20%C2%B7%20Seleccionar%20el%20Plan%20de%20Disaster%20Recovery.jpg?alt=media&amp;token=d57702d7-b385-4995-8bdb-084392d99c8b" alt="Menú del plan de Disaster Recovery con la opción Drill"><figcaption><p>Option <strong>Drill</strong> in the plan menu.</p></figcaption></figure>
{% endstep %}

{% step %}

### Enter the name and restore point

Give the drill a descriptive name so you can easily identify it, and choose the date and time of the backup (restore point) from which you want to start the test servers.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F2Ypo9dBHSeTcjw6vTsA3%2FCAPTURA%202%20%C2%B7%20Indicar%20el%20nombre%20y%20el%20punto%20de%20restauraci%C3%B3n.jpg?alt=media&amp;token=96477bfe-b07c-48ab-9de0-6f99557cf885" alt="Formulario para indicar el nombre del simulacro y el punto de restauración"><figcaption><p>Drill name and restore point selector.</p></figcaption></figure>
{% endstep %}

{% step %}

### Review and confirm the creation

Review the summary of the selected details (plan, name, and recovery point), then confirm to begin deployment.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FTjav2E8NFAZvL5fkL89c%2FCAPTURA%203%20%C2%B7%20Revisar%20y%20confirmar%20la%20creaci%C3%B3n.jpg?alt=media&amp;token=0a688b3c-7a3a-4099-99a3-f6abc4e9e115" alt="Confirmación para desplegar el simulacro"><figcaption><p>Confirmation of drill deployment.</p></figcaption></figure>
{% endstep %}

{% step %}

### Deploy the test environment

The platform will automatically begin creating the servers. During this step, you’ll see the status as in progress while resources are prepared and configured in an isolated environment so they don’t interfere with your production systems.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fm42dX1Rt6LTkbwV4ec2o%2FCAPTURA%204%20%C2%B7%20Despliegue%20del%20entorno%20de%20prueba.jpg?alt=media&amp;token=277c9b70-5d5a-4f38-9cf9-5b99aa63d200" alt="Proceso de preparación del simulacro"><figcaption><p>Drill preparation process.</p></figcaption></figure>
{% endstep %}

{% step %}

### Drill operational and verification

Once deployment is complete, the drill will be marked as operational. You can then access the test servers using their IP addresses or directly through the console to verify that the operating system starts properly, the applications work correctly, and the data is up to date.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F23vekiq0iC3j8mAv6HGb%2FCAPTURA%205%20%C2%B7%20Simulacro%20operativo%20y%20comprobaciones.jpg?alt=media&amp;token=b13085ce-560c-453e-93cf-6338133f2f9b" alt="Simulacro operativo con servidores y direcciones IP disponibles"><figcaption><p>Operational drill with servers and IP addresses available.</p></figcaption></figure>
{% endstep %}

{% step %}

### Start ending the drill

Once you’ve completed all the checks and confirmed that the plan works as expected, go to the drill options and select the delete option.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F1pqJwTYi9JWHUx1qGYCU%2FCAPTURA%206%20%C2%B7%20Iniciar%20la%20finalizaci%C3%B3n%20del%20simulacro.jpg?alt=media&amp;token=0ef1b8ef-4817-4951-bacf-aef73df92d0e" alt="Menú de opciones del simulacro con la acción Delete"><figcaption><p>Options menu with the action <strong>Delete</strong>.</p></figcaption></figure>
{% endstep %}

{% step %}

### Confirm the deletion

A confirmation window will appear asking you to confirm that you want to end the test and delete the temporary servers that were created. Confirm the action.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F0CWnNHqUwXu7T9uOh2MJ%2FCAPTURA%207%20%C2%B7%20Confirmar%20la%20eliminaci%C3%B3n.jpg?alt=media&amp;token=87cc37cd-5d56-466a-bce4-c29690b6870c" alt="Confirmación para eliminar el simulacro"><figcaption><p>Confirmation of drill deletion.</p></figcaption></figure>
{% endstep %}

{% step %}

### Deletion in progress

The system will shut down the servers and release the resources used during the test without affecting your backups or production servers.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FqKTb4FXKBLx9q2kBYegE%2FCAPTURA%208%20%C2%B7%20Proceso%20de%20eliminaci%C3%B3n%20en%20curso.jpg?alt=media&amp;token=78b25a4b-401a-41d6-af52-1df5f6220d1c" alt="Proceso de eliminación del simulacro en curso"><figcaption><p>Deletion in progress.</p></figcaption></figure>
{% endstep %}

{% step %}

### Deletion complete

The drill will appear as successfully deleted in the list, leaving the environment completely clean.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FaIYOfVEfr9MsuICgTzzj%2FCAPTURA%209%20%C2%B7%20Finalizaci%C3%B3n%20de%20la%20eliminaci%C3%B3n.jpg?alt=media&amp;token=5ca681ad-3812-4b4a-a9a7-0f9fce3716c9" alt="Lista de simulacros vacía tras la eliminación"><figcaption><p>List of drills with no active environments.</p></figcaption></figure>
{% endstep %}

{% step %}

### Review the event log

Finally, go to the Events or History tab to review the complete test log (start, deployment, uptime, and deletion). This log serves as formal evidence that the continuity plan was tested successfully.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F9lDMmVOfLaDekTtoNNtw%2FCAPTURA%2010%20%C2%B7%20Consulta%20del%20registro%20de%20eventos.jpg?alt=media&amp;token=8c59013f-9cb4-4562-b79e-620b87dd9229" alt="Historial de eventos del simulacro"><figcaption><p>Drill event history.</p></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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/how-to/how-to-run-a-drill.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.
