> 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/servers-2/concepts/backup-and-data-protection.md).

# Backup and Data Protection

Backups are included with every server. They're your safety net: if something goes wrong, restore

Each server includes **backups**. They are your safety net: if an update goes wrong, someone deletes something they shouldn't, or ransomware gets in, you restore and keep going.

### How backups work

Backups are made **automatically, scheduled**, without you having to remember: every **hour**, every **day** and every **week**.

They are configured **per disk and per server**, and the **retention** — how long you keep each backup — is configurable.

> #### 📘 Scheduled backup vs. snapshot
>
> The **backup** is automatic and saves versions of your disks according to the schedule.
>
> The **snapshot** is a **manual snapshot of the entire machine** that you take at a specific moment — for example, just before a risky change — so you can roll back if something goes wrong.

### Ransomware protection

Your backups are stored as **read-only copies**: once created, they cannot be modified or encrypted from the server. If ransomware reaches the machine, it can't touch the backups, and you have somewhere to restore from.

### You control and restore

We include and run the backup engine; **you decide** the schedules and retention, and **you restore** when needed. It fits the shared responsibility model: the infrastructure is ours, the control of your backups is yours.

The step-by-step guide to configure backups, create a snapshot, or restore is in How-to.

### Backup is not high availability

> #### 🚧 Backup recovers; it does not keep things running
>
> Backup is your safety net to **recover** data and state. Keeping the service available when a machine goes down is something else: **continuity design**, with multiple servers and the right architecture.
>
> Backup and continuity complement each other, they do not replace each other.

### Next steps

* Configure backups, create a snapshot, or restore in [How-to.](https://docs.plenit.com/docs-en/productos/servers/how-to.md)
* Review what you operate and what we operate in [What is a Server?.](https://docs.plenit.com/docs-en/productos/servers/concepts/what-it-is.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/servers-2/concepts/backup-and-data-protection.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.
