> 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-perform-a-failback.md).

# How to Perform Failback in Disaster Recovery

Return operations to the original subscription after a failover and choose the failback type that fits your scenario: keep changes, return quickly, or reconfigure the replica.

After a failover, you temporarily work on the backup site. Failback is the way back to the original environment, and depending on your situation you have three ways to do it: keeping the backup changes, returning quickly without replicating, or reconfiguring the replication from scratch.

This guide helps you choose and carry out the right one.

> #### 👍 What you get
>
> The operation returned to your original subscription after a failover, with the appropriate failback method for your scenario and replication ready for the next incident.

### Choose your option

* **Option 1 — Return without losing changes**: if you have continued working on the backup site and need to keep that data before returning to the source.
* **Option 2 — Return quickly to the source**: if the failover was a test or a mistake, or you can already resume normal operation without redoing the configuration.
* **Option 3 — Reconfigure replication**: if you want to completely redefine the direction of replication or create a new destination.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Having a protected Servers or Remote Desktop subscription, and its subscription of **Disaster Recovery**.
* That the Disaster Recovery subscription is **in failover state**.

> #### ❗️ Overwriting erases the destination data
>
> In the replication steps you can choose **overwrite** the destination subscription.
>
> If you do, any data on it will be lost. This is normal when redoing the replication, but make sure the destination is correct before confirming.
>
> Server activation and replication may take some time depending on disk volume and infrastructure load.

Throughout the guide, an example is used with **Madrid** as the primary site and **Paris** as the backup site (Recovery site), so the direction of replication is clear at all times.

### Option 1. Return to the original site without losing changes

Use it when you have worked on the backup and want to return to the source with that data. The process is: replicate from the backup to the source, perform failback, and then set up replication again from the source to the backup.

#### 1.1 Reconfigure replication from the backup to the source

In **My Plans**, check that the **Recovery Site** is **active** and the **Primary Site** to **inactive**, and click **Reconfigure** to open the replication wizard. Select as **source** the backup subscription (in the example, Paris) 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-4064d9712cac326d25826e6c2a7e71a50e776b66%2FCAPTURA%201%20%C2%B7%20My%20Plans%20%C2%B7%20estados%20active-inactive%20%C2%B7%20bot%C3%B3n%20Reconfigurar.jpg?alt=media" alt=""><figcaption><p>Site status and replication reconfiguration</p></figcaption></figure>

Select as **destination** the source subscription (in the example, Madrid) 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-f3af7869154bca2fd7fd67e38f5c33b4b0776b65%2FCAPTURA%202%20%C2%B7%20selecci%C3%B3n%20de%20origen%20y%20destino%20de%20la%20r%C3%A9plica.jpg?alt=media" alt=""><figcaption><p>Source and destination of replication for failback</p></figcaption></figure>

Define the **frequency** of the replicas, **how many** are kept and the **Failover mode** (DNS or IP), and click **Finish**. Replication starts and you can follow its progress in the interface until it remains **active**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-7acf02da0c2f269f69200d13d65dcbe6fe45271f%2FCAPTURA%203%20%C2%B7%20frecuencia%2C%20puntos%20de%20restauraci%C3%B3n%20y%20tipo%20de%20conmutaci%C3%B3n.jpg?alt=media" alt=""><figcaption><p>Frequency, retention, and failover configuration</p></figcaption></figure>

#### 1.2 Start failback

With replication active and the data up to date at the source, click **Failback**. Select the **restore point** to return to and click **Confirm**; confirm again for it to take effect.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-44722fcad4c58e580424dc084af542e31d047400%2FCAPTURA%204%20%C2%B7%20Failback%20%C2%B7%20selecci%C3%B3n%20del%20punto%20de%20restauraci%C3%B3n.jpg?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-63eb49bd4e47e75ca2050d5107af80acf5651c7d%2FCAPTURA%204bis%20%C2%B7%20Failback%20%C2%B7%20selecci%C3%B3n%20del%20punto%20de%20restauraci%C3%B3n.jpg?alt=media" alt=""><figcaption><p>Failback and restore point selection</p></figcaption></figure>

You will see a notice that failback is in progress and operations are being updated on the Primary Site. When finished, the **Primary Site** becomes **active** and the **Secondary Site** to **inactive**.

#### 1.3 Leave replication ready for the next incident

To protect the environment again, click **Reconfigure** and create the replication from the source to the backup (in the example, from Madrid to Paris): select source and destination, define frequency, first replication, restore points and **Failover mode**, and click **Finish**. With that, DR is operational again.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-8142c9e5fb784f26d21341eb5647cc49a06b7aee%2FCAPTURA%205%20%C2%B7%20reconfiguraci%C3%B3n%20de%20la%20r%C3%A9plica%20origen%20%E2%86%92%20respaldo.jpg?alt=media" alt=""><figcaption><p>Reconfiguring replication to keep DR protected</p></figcaption></figure>

### Option 2. Quickly return to the source after a test or error

Use it when the failover was temporary and you do not need to replicate changes from the backup before returning.

In **My Plans**, check that the services are active in the secondary subscription and that the primary is inactive. Click **Activate** in the primary subscription and accept the startup. The servers start (this may take depending on the volume) until the service becomes active.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-292fe623599dcaf3f564dc9e9b35579f43515b8e%2FCAPTURA%206%20%C2%B7%20activaci%C3%B3n%20de%20la%20suscripci%C3%B3n%20primaria.jpg?alt=media" alt=""><figcaption><p>Activation of the servers in the primary subscription</p></figcaption></figure>

Then, send the traffic back to the source: click **Switch DNS** in the primary subscription. A warning reminds you that traffic is redirected and some connections may be lost; click to continue. Traffic passes through the original subscription again.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-d5f3be63d607df4d90125104966af30252f6bdcc%2FCAPTURA%207%20%C2%B7%20Switch%20DNS%20%C2%B7%20aviso%20de%20cambio%20de%20tr%C3%A1fico.jpg?alt=media" alt=""><figcaption><p>Switch DNS to return traffic to the source</p></figcaption></figure>

> #### 🚧 The backup remains active: close it with replication
>
> After the Switch DNS, the backup subscription (in the example, Paris) remains active in addition to the source.
>
> To make it inactive again and return to the protected setup, configure replication from the source to the backup, as in Option 1.3.

### Option 3. Completely reconfigure replication

Use it when you need to redefine the source and destination of replication after failover. Open the full replication wizard from **Reconfigure** and decide which direction protection will take:

* **Paris as the source and Madrid as the destination**: if you continue operating on the backup and replicate back to the source.
* **Madrid as the source and Paris as the destination**: if you have already returned to the primary environment and restore the usual setup.

Select the **source** and click **Next**. Choose the **destination**, where you can:

* **Overwrite** the current copy: replaces the destination data (the most common option).
* **Create a new destination subscription**: keeps the current one, but adds an associated cost.

If you overwrite, a warning appears that the destination data will be lost. Click **Next**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-0c8f7ebf22e128b2fbe4fc45d0e5178b463dae08%2FCAPTURA%208%20%C2%B7%20selecci%C3%B3n%20de%20destino%20%C2%B7%20sobrescribir%20o%20nueva%20suscripci%C3%B3n.jpg?alt=media" alt=""><figcaption><p>Replication destination selection</p></figcaption></figure>

Define the **frequency** (from 1 to 24 hours), **when** the first replication is launched, the number of **restore points** (from 1 to 24, default 12) and the **Failover mode** (DNS or IP). Click **Finish** to start replication.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-7664c618c65afe93f3c98dd3d1492bef0872bc7e%2FCAPTURA%209%20%C2%B7%20frecuencia%2C%20retenci%C3%B3n%20y%20tipo%20de%20conmutaci%C3%B3n%20de%20la%20nueva%20r%C3%A9plica.jpg?alt=media" alt=""><figcaption><p>New replication configuration</p></figcaption></figure>

### Conclusion

Failback has three paths, and the key is to choose the right one for your case: if you worked on the backup and do not want to lose anything, first replicate back to the source (Option 1); if it was a test or a mistake, return quickly by activating the source and changing the DNS (Option 2); and if you need to redefine protection, reconfigure the entire replication (Option 3).

In all of them, two precautions: make sure the destination is correct before overwriting, and finish by leaving the replication from the source to the backup so the environment is protected again for the next incident.

### Next steps

* Review how the switch to the backup is activated in [Failover and failback.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md)
* Adjust the frequency and restore points in [Replication parameters.](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles/replication-parameters.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-perform-a-failback.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.
