> 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

Replication keeps a live copy of your environment at the Recovery site, updated according to the frequency you choose. What is replicated are the full subscription items, not just the data; you have it in [What is Disaster Recovery?.](/docs-en/productos/disaster-recovery/concepts/what-it-is.md) 

Here you see how you decide the pace and scope.

### How often it is replicated

The frequency defines your **loss window**: in the worst case, you would lose the changes made since the last replication. The more frequent it is, the less you lose.

| Frequency      | At most you lose    |
| -------------- | ------------------- |
| 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 that replication starts during a lower-activity period.

> #### 📘 Match the frequency to the value of the data
>
> An environment with data that changes every minute calls for a short window. For data that barely changes during the day, a daily replication is enough. 
>
> Adjust the frequency to how much work your client can afford to lose, not by default to the highest one.

### How many restore points you keep

Each replication leaves a **restore point**: a state you can return to. You keep from 1 to 24, and having several gives you room to choose which point in time to recover to.

The clearest example is ransomware: if you only keep the latest point, it may already be encrypted. With several points, you can go back to one from before the infection.

### What you can leave out

Not everything needs replication. You can **exclude specific machines or disks** from the plan, for example a temporary data disk or a secondary machine, to replicate only what really supports the business.

### Where to go next

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