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

# Glossary

Disaster Recovery terms, grouped by section and explained in tables.

A quick review of the terms we use when talking about Disaster Recovery. If you come across one and aren't sure what it means, look it up here.

### The plan

| Term          | What it is                                                                                                         |
| ------------- | ------------------------------------------------------------------------------------------------------------------ |
| Plan          | The Disaster Recovery configuration for a subscription: its source, its destination, and its replication settings. |
| Primary site  | The source environment you protect, the one in production.                                                         |
| Recovery site | The destination environment, in another zone, where the replica lives ready to be activated.                       |
| Replica       | The live copy of the environment that is kept in the Recovery site according to the configured frequency.          |

### The protection

| Term                  | What it is                                                                                   |
| --------------------- | -------------------------------------------------------------------------------------------- |
| Replication frequency | How often the copy is updated (every 1, 3, 6, 12, or 24 hours); it defines your loss window. |
| Loss window (RPO)     | The changes you could lose in the worst case, equivalent to the time between replicas.       |
| Restore point         | A saved state you can return to; you keep from 1 to 24.                                      |
| Exclusion             | Machines or disks you decide to leave out of the plan because they don't need protection.    |

### The recovery

| Term                | What it is                                                                                          |
| ------------------- | --------------------------------------------------------------------------------------------------- |
| Failover            | Move services to the Recovery site when the Primary site becomes unavailable.                       |
| Failback            | Return to the Primary site when it is restored, bringing back the changes made during the failover. |
| Switchover mode     | How traffic is redirected to the Recovery site: via DNS (available) or via IP (coming soon).        |
| Recovery time (RTO) | How long it takes for the service to be operational again after failover is activated.              |
| Simulation (drill)  | A parallel test of the plan, without affecting production, that leaves evidence for audit.          |

### Next steps

* Go back to [Concepts.](https://docs.plenit.com/docs-en/productos/disaster-recovery/concepts.md)
* See the reference at [Details.](https://docs.plenit.com/docs-en/productos/disaster-recovery/detalles.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/glossary.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.
