> 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/concepts/the-replica.md).

# The Replica

What the replica keeps, how often it is updated, how many points you retain, and what you can leave out

Replication maintains a live copy of your environment at the Recovery site, updated at the frequency you choose. It replicates the subscription’s complete resources, not just the data; you can find more in [What is Disaster Recovery?.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/what-it-is.md)

Here’s how to choose the timing and scope.

### How often replication runs

The frequency determines your **recovery point objective**: in the worst case, you would lose changes made since the last replication. The more frequently replication runs, the less you lose.

| Frequency      | Maximum data loss   |
| -------------- | ------------------- |
| Every 1 hour   | 1 hour of changes   |
| Every 3 hours  | 3 hours of changes  |
| Every 6 hours  | 6 hours of changes  |
| Every 12 hours | 12 hours of changes |
| Every 24 hours | 1 day of changes    |

You also choose the **start time**, so replication starts during a period of lower activity.

> #### 📘 Match the frequency to the value of the data
>
> An environment with data that changes every minute needs a short interval. For data that barely changes throughout the day, daily replication is more than enough.
>
> Set the frequency according to how much work your customer can afford to lose, rather than automatically choosing the highest frequency.

### How many recovery points to keep

Each replication creates a **recovery point**: a state you can return to. You can keep 1 to 24, and having several gives you options for choosing the point in time to recover to.

Ransomware is a clear example: if you keep only the latest point, it may already be encrypted. With several points, you can return to one from before the infection.

### What you can exclude

Not everything needs to be replicated. You can **exclude specific machines or disks** from the plan—for example, a temporary data disk or a secondary machine—so that only what truly supports the business is replicated.

### Before you enable it

* The source subscription must be in a single availability zone. If resources are spread across AZ-MAD1 and AZ-MAD2, it won’t appear as a source.
* Once Disaster Recovery is enabled, servers in the subscription can no longer be moved between zones. Choose each server’s zone before creating the plan.
* Disaster Recovery and Multi-AZ cannot be combined in the same environment.
* If the subscription has active snapshots, delete them before creating the plan.

### Where to go next

* Activate the standby and return to the original: [Failover and failback.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md)
* Test that replication works without touching production: [Drills.](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/concepts/the-replica.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.
