> 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

A quick review of the terms we use when talking about Disaster Recovery. If you come across any and it’s not clear to you, look it up here.

### The plan

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

### 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 replications.      |
| Restore point         | A saved state you can go back to; you keep from 1 to 24.                                        |
| Exclusion             | Machines or disks that you decide to leave out of the plan because they do not need protection. |

### Recovery

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

### Next steps

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