> 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/detalles/replication-parameters.md).

# Replication Parameters

Frequency, start time, restore points, and failover mode that you define in a plan.

These are the parameters you define when creating the plan, in the replica setup step. To understand how to choose them, go to [Replication](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/the-replica.md) and [Failover and failback](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts/failover-and-failback.md) in Concepts.

### Replication frequency

How often the copy is updated at the Recovery site.

| Option         |
| -------------- |
| Every 1 hour   |
| Every 3 hours  |
| Every 6 hours  |
| Every 12 hours |
| Every 24 hours |

You also define the **start time**, so that the replica starts in the time window you prefer.

### Restore points

| Parameter | Value |
| --------- | ----- |
| Minimum   | 1     |
| Maximum   | 24    |

Each point is a state you can return to. Keeping more points gives you more room to choose when to recover to.

### Failover switching mode

Defines how traffic is redirected to the Recovery site when you activate the backup.

| Mode | How it redirects                                        | Status      |
| ---- | ------------------------------------------------------- | ----------- |
| DNS  | Changes the destination that the service name points to | Available   |
| IP   | Keeps the IP address on the backup site                 | Coming soon |

> #### 📘 For now, failover is via DNS
>
> IP-based mode is on the way.
>
> Meanwhile, plan recovery assuming DNS failover, which is the one available today.


---

# 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/detalles/replication-parameters.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.
