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

# Backup and Data Protection

How the environment is protected with backups and how you recover data after a failure or deletion

The environment is protected with backups so that, if a problem occurs, you can recover the data to an earlier point.

### What is protected

Backups cover the disks of the servers in the environment: the system, user profiles, and work data. It is the basis for rolling back if something goes wrong.

### Restoration

If an update fails, someone deletes what they shouldn't, or ransomware gets in, you restore from a backup to an earlier point and recover the environment's healthy state.

> #### 🚧 Backup recovers, it doesn't keep the service up
>
> A backup lets you go back to a previous point, but it does not prevent downtime while you restore. It is your safety net, not a high-availability mechanism.

### Where to follow

* What you manage and what Plenit manages: [What is Remote Desktop?.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/what-it-is.md)
* Restore a backup: [How-to.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to.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/remote-desktop/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.
