> 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/file-storage/concepts/quota-and-backups.md).

# Quota and backups

Two things that are usually a problem in consumer storage are solved here: space control and data protection.

### Quota: the space you purchase

You choose the subscription quota based on what the customer needs, and scale it up as they grow. To avoid surprises with usage, you set alerts by thresholds.

| Usage alert | What is it for                  |
| ----------- | ------------------------------- |
| 80%         | Start planning the expansion    |
| 90%         | Act before you run out of space |
| 95%         | Minimum margin, expand now      |

> #### 📘 Set the alerts when you sign up
>
> Space always runs out at the worst moment.
>
> Configuring thresholds from the start turns an urgent problem into a calm alert with time to react.

### Backups included

Backups are included by default, with nothing for you to configure, with this retention:

| Frequency  | Retained         |
| ---------- | ---------------- |
| Every hour | The last 5 hours |
| Daily      | 14 days          |
| Weekly     | 8 weeks          |

This protects you against accidental deletions, file corruption, and ransomware scenarios: you can revert to an earlier copy before the problem. Restoring is easy and you do it when you need it.

> #### 👍 Protection is not an extra
>
> In many usage-based services, backup is paid separately or does not exist.
>
> Here it is included, and it is a solid argument when you explain to a customer why this storage is enterprise-grade.

### Where to follow

* What the service is and what sets it apart: [What is File Storage?](https://docs.plenit.com/docs-en/productos/file-storage/concepts/what-it-is.md)
* Who has access to the data: [Users, groups, and permissions.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/users-groups-and-permissions.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/file-storage/concepts/quota-and-backups.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.
