> 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-configure-replica-frequency-and-copies.md).

# How to Configure the Frequency and Number of Replica Copies in Disaster Recovery

Adjust the replication policy of your Disaster Recovery subscription: how often it replicates, how many restore points you keep, and the failover type.

If your requirements change or the initial configuration was not appropriate, you can adjust your Disaster Recovery replication policy from the subscription itself: how often it replicates, how many copies are retained, 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 begin

* 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 subscription of **Disaster Recovery**.

> #### 📘 Pause and Stop are not the same
>
> When stopping a replica, 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, allows you to 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 enter the subscription. You can also get there from the organization, in **Subscriptions**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-de98c1f3a6c9e01d49826ab276a52be18593dd8d%2FCAPTURA%201%20%C2%B7%20suscripci%C3%B3n%20de%20Disaster%20Recovery.jpg?alt=media" alt="Acceso a la suscripción de Disaster Recovery"><figcaption><p>Access to the Disaster Recovery subscription</p></figcaption></figure>

### Step 2. Stop the replica

In the center, locate the replica status, open its menu **(…)** and select **Stop**. Confirm with **Yes, Stop**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-24d5bf0679aa4a195c5a5939010a9f22a22eb494%2FCAPTURA%202%20%C2%B7%20men%C3%BA%20(%E2%80%A6)%20de%20la%20r%C3%A9plica%20%C2%B7%20Stop%20y%20confirmaci%C3%B3n.jpg?alt=media" alt="Detención de la réplica para reconfigurarla"><figcaption><p>Stopping the replica to reconfigure it</p></figcaption></figure>

### Step 3. Start the reconfiguration

With the replica stopped, click **Reconfigure** to open the wizard.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-eab9c7a0473f506bde41f771b73a107727e48a95%2FCAPTURA%203%20%C2%B7%20bot%C3%B3n%20Reconfigurar.jpg?alt=media" alt="Inicio del asistente de reconfiguración"><figcaption><p>Start of the reconfiguration wizard</p></figcaption></figure>

### Step 4. Select the source

Choose the **source** from which the replica will be made and click **Next**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-a8f863239512063b6d74cd30a6d682cc67502bfd%2FCAPTURA%204%20%C2%B7%20selecci%C3%B3n%20de%20la%20suscripci%C3%B3n%20de%20origen.jpg?alt=media" alt="Selección del origen de la réplica"><figcaption><p>Selection of the replica source</p></figcaption></figure>

### Step 5. Define the destination

Choose whether you want to **overwrite** the existing destination subscription or **create a new one**, and click **Next**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-2c4bdfc00134b6e647026169d9570cdb9b6b4602%2FCAPTURA%205%20%C2%B7%20destino%20%C2%B7%20sobrescribir%20o%20nueva%20suscripci%C3%B3n.jpg?alt=media" alt="Selección del destino de la réplica"><figcaption><p>Selection of the replica destination</p></figcaption></figure>

> #### 🚧 Overwriting leaves the replica on hold
>
> If you choose to overwrite the destination subscription, the replica is put on hold until the new replication finishes, and during that time it is not operational.
>
> Do it during an appropriate maintenance window if your environment depends on the continuity of the replica.

### 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 replica to start at a specific time.
* **Restore points**: between 1 and 24 copies.
* **Failover type**: DNS or IP.

When you're done, click **Finish**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-23500a5b2b4fe3a90ade1dc934a64d48024f2930%2FCAPTURA%206%20%C2%B7%20pol%C3%ADtica%20%C2%B7%20frecuencia%2C%20hora%2C%20puntos%20y%20tipo%20de%20conmutaci%C3%B3n.jpg?alt=media" alt="Configuración de la política de replicación"><figcaption><p>Replication policy configuration</p></figcaption></figure>

The criteria for choosing these values (which frequency based on how much work can be lost, how many points to keep) are in [Replication parameters.](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/replication-parameters.md)

### Step 7. Check that the reconfiguration has started

After finishing the wizard, the replica status changes to **Configuring**, and you can follow the associated jobs in the right-hand sidebar. The subscription continues replicating with the new policy.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-0620c1f3bb0f041bc236ad7bedafcd68f516e3df%2FCAPTURA%207%20%C2%B7%20estado%20Configurando%20y%20trabajos%20en%20curso.jpg?alt=media" alt="Estado de la nueva replicación"><figcaption><p>Status of the new replication</p></figcaption></figure>

### Conclusion

Reconfiguring the replica policy is a guided wizard with a few steps: you stop the replica, define source and destination, and adjust frequency, restore points, and failover type.

What you should keep in mind is that while the replica is stopped no new copies are created, and that overwriting the destination leaves protection on hold until the new replication finishes, so choose an appropriate maintenance window.

If the policy is not the one you need, repeat the wizard with the correct values.

### Next steps

* See how to return to the source after a failover in [How to perform a failback.](https://docs.plenit.com/docs-en/productos/disaster-recovery/how-to/how-to-perform-a-failback.md)
* Test the plan without affecting production with a [exercise (drill).](https://docs.plenit.com/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 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-configure-replica-frequency-and-copies.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.
