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

# Backup

The environment backup is managed from the **Servers subscription** associated, with the same backup model as the Servers product. For the concept, go to [Backup and data protection.](/docs-en/productos/servers/concepts/backup-and-data-protection.md)

### Two modes, two levels of protection

The key difference between the two modes is **where** the backup is stored, and that determines what each one protects you against.

| Mode                    | Where it is stored                         | It protects you against                                  | Scheduling          |
| ----------------------- | ------------------------------------------ | -------------------------------------------------------- | ------------------- |
| On-Primary (default)    | In the same data center as the environment | Deletions, errors, and ransomware within the environment | Fixed, not editable |
| On-Secondary (optional) | Distributed across two data centers        | The above and, in addition, the outage of a data center  | Set by the customer |

> #### 📘 Why two copies
>
> The default copy lives alongside the environment, so it restores quickly in the event of a problem with the environment itself. The distributed copy adds a second location, which provides resilience if an entire data center goes down.

### On-Primary scheduling (to be validated)

| Frequency  | Detail             |
| ---------- | ------------------ |
| Every hour | The last few hours |
| Daily      | One copy a day     |
| Weekly     | One copy a week    |

### Restoration

| Aspect          | Detail                                  |
| --------------- | --------------------------------------- |
| Where           | Servers subscription, Backup subsection |
| What you choose | Disk and restore point                  |
| Result          | The disk is restored on the server      |

> #### 🚧 Backup recovers, it does not keep it running
>
> 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.

### Best practices

* If the customer cannot afford to lose the environment if a data center goes down, consider the distributed mode across two data centers.
* Check that the environment has been deployed long enough to have restore points before relying on backup.
* Do not confuse backup with continuity: to keep the service running without interruptions, the design is different.


---

# 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/remote-desktop/details/backup.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.