> 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/quickstart.md).

# Quick Start

Disaster Recovery creates a **plan** that replicates a Server or Remote Desktop subscription in another availability zone, ready to be activated in the event of an incident. 

You configure it with a three-step wizard: you choose the **source** (your Primary site), you choose the **destination** (your Recovery site) and define the **replication parameters**.

> #### **📘 What you get**
>
> A Disaster Recovery plan in **My plans**, with your source subscription as **Primary site**, a **replica** running and a **Recovery site** in the destination zone.
>
> The initial replica takes time depending on the volume of data.

#### Where Disaster Recovery lives

Disaster Recovery lives in its own subscription (DraaS), which you access from **Cloud Services → Disaster Recovery**. Inside, you have four tabs:

* **Summary**: the overview snapshot (plans, replicated servers, replicated GB and drills) for the period you choose.
* **My plans**: your plans, each with its Primary site, its replica and its Recovery site. Here you create new plans and launch failover.
* **Drills**: the simulations to test the plan without touching production.
* **Events**: the log of what happens (completed replications, errors), with filters by plan, date, subscription and user.

If you manage several environments, you can have **multiple DraaS subscriptions** and switch between them from the title selector.

<figure><img src="/files/7e746b8acd24e36ff839130c9023012ab6fec868" alt=""><figcaption><p><em>The Summary tab gives you the overview snapshot: plans, servers and replicated GB, and drills, for the period you choose.</em></p></figcaption></figure>

<figure><img src="/files/911dcf3b7b1d8fc5796b20aa9e02920779de5cb6" alt=""><figcaption><p><em>Different Subscriptions Dropdown</em></p></figcaption></figure>

#### Before you start

You need:

* Signed in to the Plenit platform.
* A **Server** or **Remote Desktop** subscription that you want to protect.

> #### **🚧 The source must be in a single zone**
>
> You can only protect a subscription whose elements are in a single availability zone.
>
> If the subscription spreads resources across multiple zones, it will not appear in the source list.

> #### **🚧 No active snapshots on the source**
>
> If the subscription has an active snapshot, the wizard won't let you register it and will warn you in Step 1.&#x20;
>
> Delete the source snapshots before creating the plan.

#### Start the registration

Depending on whether you already work with Disaster Recovery or it's your first time, you reach the wizard through one of these paths. All three end up in the same place.

| Situation                             | How you start                                                                                              |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| You already use Disaster Recovery     | Enter Disaster Recovery and click **New plan**, at the top right of **My plans**                           |
| It's your first time with the service | On the product page, click **I want to try it now**                                                        |
| From a specific customer              | Go to **Organization → Subscriptions** and choose **Disaster recovery** in "What do you want to register?" |

<figure><img src="/files/3af1006cbe88f2067cbb87554d03cc777f20305e" alt=""><figcaption><p><em>If you already use Disaster Recovery, you open the wizard with New plan, at the top right of My plans.</em></p></figcaption></figure>

<figure><img src="/files/a551f80880e200fae88ccc406ed6a79094d672bc" alt=""><figcaption><p><em>The first time, you reach the same wizard from the product page, with I want to try it now.</em></p></figcaption></figure>

#### Step 1. Choose the source and name the plan

In the wizard:

1. Type the **Plan Name**, which will help you identify it if you manage several.
2. Select the subscription you want to protect. Each card shows you what's inside (servers, disks, networks and IP; and in Remote Desktop, also users, licenses and applications), so you can choose with criteria. The one you select is set as your **Primary site**.
3. Move on to the next step.

<figure><img src="/files/3efd3bc47e0e10210f2306e0334e2a76b6b63618" alt=""><figcaption><p><em>Step 1. Name the plan and choose the subscription to protect, which is set as your Primary site.</em></p></figcaption></figure>

#### Step 2. Choose the destination

Select the **destination availability zone**, where your **Recovery site**Recovery site

<figure><img src="/files/72452cfb29de5542644c9e1b4e507ac0ed564423" alt=""><figcaption><p><em>Step 2. Choose the destination zone where your Recovery site is set.</em></p></figcaption></figure>

> #### **📘 SSH keys do not travel to the Recovery site**
>
> If you protect Linux machines, keep in mind that the SSH keys remain available in the Primary site panel, but **do not appear in the Recovery site panel** when a Disaster Recovery evacuation is performed.
>
> Keep this in mind when planning how you will access the machines after a failover.

#### Step 3. Configure the replication parameters

You define how and how often the environment is replicated:

1. **Replication frequency**: every 1, 3, 6, 12 or 24 hours.
2. **Start time**: what time you want the replication to start.
3. **Restore points**: how many states to keep, from 1 to 24. Each point is a moment you can return to, so more points give you more room to choose the moment to recover to.
4. **Failover mode**: how traffic is redirected to the Recovery site when you activate the backup.

| Failover mode | State       |
| ------------- | ----------- |
| DNS           | Available   |
| IP            | Coming soon |

Save to create the plan.

<figure><img src="/files/88262ab8339a8b15256cd43c520e07debcb7bec3" alt=""><figcaption><p><em>Step 3. Define the frequency, the start time, the restore points and the switchover mode.</em></p></figcaption></figure>

> #### **🚧 Old Windows servers: possible credential prompt**
>
> If you protect a Server subscription with Windows machines deployed some time ago, the wizard may ask you for the administrator password.
>
> It is used to update the agent and enable the operations that the Disaster Recovery process needs. Enter it to continue.

When you save, we start replicating the resources to the Recovery site.

#### Check the plan in My plans

The plan appears in **My plans**. At first, you will see it in status **Configuring**: the Recovery site shows its **step-by-step setup process**  (server preparation, creation and configuration of replica volumes, and synchronization of subscriptions). Each plan is organized into three blocks:

* **Primary site**: your source subscription, active, with its zone.
* **Replica**: the switchover mode, the number of copies and the periodicity you configured.
* **Recovery site**: the destination environment that is being prepared in the other zone.

<figure><img src="/files/21023976f72983248fb27ea733aa6789c47ed209" alt=""><figcaption><p><em>Just created, the plan appears in Configuring, with the Recovery site completing its setup in the other zone.</em></p></figcaption></figure>

When the replica finishes configuring and restore points are available, the plan changes to **Active** and is now protecting the environment.&#x20;

Then the **Replica** Replica **Recovery site** shows you the switchover mode, the number of copies and the last and next replication, and the **Failover** button for the day you need to activate the backup.

<figure><img src="/files/d71e7137b445648d160e75fc2194de489aee13b2" alt=""><figcaption><p><em>Already in Active, the plan protects the environment: the replica shows the last and next copy, and the Recovery site enables Failover.</em></p></figcaption></figure>

#### You already have Disaster Recovery active

From here on, from the Disaster Recovery subscription you can:

* Understand what is replicated and how often: [The replica.](/docs-en/productos/disaster-recovery/concepts/the-replica.md)
* Switch to backup and back when it's time: [Failover and failback.](/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md)
* Adjust the frequency and restore points: [How to configure the frequency and the number of copies.](/docs-en/productos/disaster-recovery/how-to/how-to-configure-replica-frequency-and-copies.md)
* Test the plan without affecting production, from the tab **Drills**: [How to run a drill.](/docs-en/productos/disaster-recovery/how-to/how-to-run-a-drill.md)
* Return to the source after a failover: [How to perform a failback.](/docs-en/productos/disaster-recovery/how-to/how-to-perform-a-failback.md)
* Follow what's happening in the tab [**Events**](/docs-en/platform/accounts/details/events.md): completed replications, errors, and who did what.


---

# 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/quickstart.md?ask=<question>&goal=<endgoal>
```

`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.