> 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/concepts/backup-and-data-protection.md). # Backup and data protection Every server includes **backups**. They are your safety net: if an update goes wrong, someone deletes what 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, right before a risky change — so you can roll back if something goes wrong. ### Protection against ransomware Your backups are stored as **read-only copies**: once made, they cannot be modified or encrypted from the server. If ransomware reaches the machine, it won't touch the backups, and you have something 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, control of your backups is yours. You can find the step-by-step guide to set up backups, create a snapshot, or restore in How-to. ### Backup is not high availability > #### 🚧 Backup recovers; it doesn't keep things running > > Backup is your safety net to **recover** data and state. Keeping the service available when a machine fails 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 * Set up backups, create a snapshot, or restore in [How-to.](/docs-en/productos/servers/how-to.md) * Review what you operate and what we operate in [What is a Server?](/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 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/servers/concepts/backup-and-data-protection.md?ask=&goal= ``` `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.