> 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 If your requirements change or the initial configuration wasn't suitable, you can adjust your Disaster Recovery replication policy from the subscription itself: how often it replicates, how many copies are kept, and how failover works. This guide walks through the reconfiguration. > #### 👍 What you get > > Your Disaster Recovery replication policy adjusted to your needs: frequency, restore points, and failover type. ### Before you start * Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment. * Have a protected Servers or Remote Desktop subscription. * Have a **Disaster Recovery**. > #### 📘 Pause and Stop are not the same > > When you stop a replication, you encounter two different states: the **Pause** temporarily stops replication and no new replicas are created until you reactivate it; the **Stop** stops it and, in addition, lets you change the subscription configuration. > > To reconfigure the policy you need to stop it, not just pause it. ### Step 1. Open the Disaster Recovery subscription In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Disaster Recovery** and open the subscription. You can also get there from the organization, in **Subscriptions**. {/\* 📸 CAPTURE 1 · Disaster Recovery subscription \*/} ![Access to the Disaster Recovery subscription](https://REEMPLAZA-URL/disaster-recovery-frecuencia-01.png) ### Step 2. Stop the replication In the center, locate the replication status, open its **(…)** menu and select **Stop**. Confirm with **Yes, Stop**. {/\* 📸 CAPTURE 2 · replication (…) menu · Stop and confirmation \*/} ![Stopping the replication for reconfiguration](https://REEMPLAZA-URL/disaster-recovery-frecuencia-02.png) ### Step 3. Start the reconfiguration With the replication stopped, click **Reconfigure** to open the wizard. {/\* 📸 CAPTURE 3 · Reconfigure button \*/} ![Start of the reconfiguration wizard](https://REEMPLAZA-URL/disaster-recovery-frecuencia-03.png) ### Step 4. Select the source Choose the **source** subscription from which the replication will be made and click **Next**. {/\* 📸 CAPTURE 4 · source subscription selection \*/} ![Selection of the replication source](https://REEMPLAZA-URL/disaster-recovery-frecuencia-04.png) ### Step 5. Define the destination Choose whether you want to **overwrite** the existing destination subscription or **create a new one**, and click **Next**. {/\* 📸 CAPTURE 5 · destination · overwrite or new subscription \*/} ![Selection of the replication destination](https://REEMPLAZA-URL/disaster-recovery-frecuencia-05.png) > #### 🚧 Overwrite leaves the replication on hold > > If you choose to overwrite the destination subscription, the replication is put on hold until the new replication finishes, and during that time it is not operational. > > Do this during an appropriate maintenance window if your environment depends on replication continuity. ### Step 6. Configure the recovery policy Define the values of the new policy: * **Replication frequency**: 1, 3, 6, 12, or 24 hours. * **Start time**: if you want the replication to start at a specific time. * **Restore points**: between 1 and 24 copies. * **Failover mode**: DNS or IP. When you're done, click **Finish**. {/\* 📸 CAPTURE 6 · policy · frequency, time, points and failover type \*/} ![Replication policy configuration](https://REEMPLAZA-URL/disaster-recovery-frecuencia-06.png) The criteria for choosing these values (what frequency according to how much work can be lost, how many points to retain) are in [Replication parameters.](/docs-en/productos/disaster-recovery/detalles/replication-parameters.md) ### Step 7. Check that the reconfiguration has started After finishing the wizard, the replication status changes to **Configuring**, and you can follow the associated jobs in the right-hand sidebar. The subscription continues replicating with the new policy. {/\* 📸 CAPTURE 7 · Configuring status and ongoing jobs \*/} ![Status of the new replication](https://REEMPLAZA-URL/disaster-recovery-frecuencia-07.png) ### Conclusion Reconfiguring the replication policy is a guided wizard with a few steps: you stop the replication, define source and destination, and adjust frequency, restore points and failover type. What is worth keeping in mind is that while replication is stopped no new copies are created, and overwriting the destination leaves protection on hold until the new replication finishes, so choose an appropriate maintenance window. If the policy is not what you need, repeat the wizard with the correct values. ### Next steps * Review how to return to the source after a failover in [How to perform a failback.](/docs-en/productos/disaster-recovery/how-to/how-to-perform-a-failback.md) * Test the plan without affecting production with a [drill.](/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 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/how-to/how-to-run-a-drill.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.