> 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/servers/how-to/como-recuperar-un-servidor-en-otra-zona-de-disponibilidad-desde-un-backup.md).

# How to recover a server in another availability zone from a backup

In this tutorial you will learn how to recover a server in the other Madrid availability zone when the zone in which it was deployed becomes unavailable.

The process consists of **deploying a new server in the available zone and restoring the affected server’s backup to it**. You do not need to keep a second server deployed permanently to use this recovery model.

{% hint style="info" %}

### 🔥 What you get

An operational server in the other availability zone, with the data recovered from one of the available restore points.
{% endhint %}

### Before you begin: what you are actually doing

This is a **manual recovery** scenario, not an automatic failover.

If, for example, your server is deployed in MAD1 and that zone becomes unavailable, you can deploy a new server in MAD2 and use the backup to restore the service there.

**You are not moving the original server from MAD1 to MAD2.** You are creating a new server in the available zone and recovering the protected information onto it from the backup.

Also keep in mind that the server will be recovered with the data corresponding to the **restore point you select**. Changes made after that point will not be included in the recovery.

Region backups are protected in a location independent of the two Madrid availability zones, so you can use them to recover the service in the other zone.

### Prerequisites

Before starting the recovery:

* Check that there is a valid restore point for the affected server.
* Identify the availability zone in which the server was deployed and use the other zone as the recovery target.
* Make sure you have identified the configuration the server you are going to recover needs: capacity, network, disks, and any dependencies required to provide the service again.
* Decide which restore point you are going to use, taking into account how far back you need to recover the data.

If you need to review how backups and restore points work, see [**How to restore a disk backup**](https://docs.plenit.com/docs-en/productos/servers/how-to/how-to-restore-a-disk-backup.md).

### Step 1. Deploy a server in the other availability zone

From the **Servers**service, click **Create Server**.

Configure the new server with the resources needed to run the service you want to recover.

In **Location**, select:

* **Region:** Madrid.
* **Availability zone:** the zone other than the one in which the affected server was deployed.

For example, if the original server was in **MAD1**, select **MAD2**.

📸 *Creation of the recovery server with MAD2 selected as the availability zone.*

Also configure the network that the server will use according to the recovery design you have planned for that service.

Complete the configuration and create the server.

### Step 2. Select the restore point

Access the **restore points** for the server or disk you want to recover.

Review the available backups and select the restore point that matches the moment to which you need to recover the data.

📸 *List of available restore points and selection of the backup that will be used for recovery.*

{% hint style="warning" %}
**Important:** check the date and time before starting the restoration. The recovered content will correspond to the state stored at that point.
{% endhint %}

### Step 3. Restore the backup on the new server

Restore the backup as a **new disk attached to the server you just deployed in the other availability zone**.

Select the new MAD2 server as the destination (or MAD1 if you are performing the recovery in the opposite direction) and confirm the restoration.

📸 *Backup restoration selecting the server deployed in the other zone as the destination.*

To review all the options available during the restoration and the detailed procedure, see [**How to restore a disk backup**](https://docs.plenit.com/productos/servers-1/how-to/how-to-restore-a-disk-backup).

If the server has multiple disks that you need to recover, repeat the process with the corresponding restore points.

### Step 4. Check the recovered server

Once the restoration is complete, check that:

* The new server is in **ON** state and deployed in the planned availability zone.
* The restored disks appear attached to the server.
* The operating system correctly recognizes the recovered disks.
* The server uses the network planned for the recovery scenario.

📸 *Server deployed in the new zone with the restored disk attached.*

Do not assume the service has been recovered just because the server is powered on. You still need to check the application dependencies.

### Step 5. Validate the service before putting it back into production

Check that the application or service works correctly on the recovered server.

Pay special attention to elements that may depend on the previous infrastructure, such as network configuration, firewall or NAT rules, addressing, DNS, and connections with other servers or services.

Finally, verify that:

* The application or service starts correctly.
* The components that need to communicate have connectivity.
* The data matches the selected restore point.
* The service is accessible again in the way expected by your customer.

### Conclusion

You have recovered a server in a different availability zone from the one where it was originally deployed, using one of its backups.

This model allows you to use the second zone as a **recovery target without permanently keeping a second server deployed**. Recovery is manual and the recovered state will depend on the restore point selected.

#### Related tutorials

* [**How to restore a disk backup**](https://docs.plenit.com/productos/servers-1/how-to/how-to-restore-a-disk-backup)
* [**How to deploy servers in multiple availability zones**](https://docs.plenit.com/productos/servers/how-to/como-desplegar-servidores-en-multiples-zonas-de-disponibilidad)
* [**How to enable High Availability (HA) on the network between two availability zones**](https://docs.plenit.com/productos/servers/how-to/como-habilitar-alta-disponibilidad-ha-en-la-red-entre-dos-zonas-de-disponibilidad)


---

# 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/servers/how-to/como-recuperar-un-servidor-en-otra-zona-de-disponibilidad-desde-un-backup.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.
