> For AI agents: the complete documentation index is available at /en/llms.txt, the full documentation bundle is available at /en/llms-full.txt.

# Retention & schedules

How long your backups are kept is controlled by a **prune** policy on the
server — it runs for you, and you do not need to configure anything
yourself. This page describes the default values and what they actually
give you in terms of restore points.

## Default retention \{#standardretention}

| Level                        | Count | What it gives you                                            |
| ---------------------------- | ----- | ------------------------------------------------------------ |
| **Latest** (`keep-last`)     | 3     | The 3 most recent backups are always kept, regardless of age |
| **Daily** (`keep-daily`)     | 14    | One point per day, \~2 weeks back                            |
| **Weekly** (`keep-weekly`)   | 4     | One point per week, \~1 month back                           |
| **Monthly** (`keep-monthly`) | 12    | One point per month, a full year back                        |
| **Yearly** (`keep-yearly`)   | 1     | One point is kept further back than a year                   |

With a daily backup routine (e.g. every night, as in
[Getting started](/en/proxmox-backup/kom-igang.md)) this setup gives you roughly **34 restore
points** available at the same time: fine-grained (daily) for the last few
weeks, sparser (weekly, then monthly) further back, and a single yearly
point as your safety net against losing your history entirely.

If you run backups less often (e.g. only weekly), the levels fill up
naturally based on your actual backups — prune counts unique backups per
calendar period, not calendar days as such, so you lose nothing by backing
up less often than daily.

:::note
This is the default setting for the service. Your actual retention may
differ if you have agreed on something else in your order — see your
order confirmation or contact **[hej@getgeek.se](mailto:hej@getgeek.se)** if you are unsure what
applies to your datastore.
:::

## Schedules on the server \{#scheman-pa-servern}

| Job                | Time             | Purpose                                                                            |
| ------------------ | ---------------- | ---------------------------------------------------------------------------------- |
| Prune              | Daily at 21:00   | Applies the retention policy above and removes backups that have fallen outside it |
| Garbage collection | Daily at 23:00   | Frees disk space from data no longer referenced by any kept backup                 |
| Verify             | Sundays at 18:15 | Reads through stored chunks and checks that they are intact (integrity check)      |

The weekly verify job is part of why GetGeek Proxmox Backup works well as
your offsite copy in a NIS2 context: it is not just a copy that exists, but
a copy that is actively checked for silent bit rot or storage errors. It
does not, however, replace your own restore drill — see [FAQ](/en/proxmox-backup/faq.md) for
our recommendation on that.

## Want a different retention? \{#vill-du-ha-en-annan-retention}

Retention is essentially your cost dial — more kept points mean more stored
data, and you pay per actual GB (see [Overview](/en/proxmox-backup/index.md)). If you want a
different profile than the default, contact **[hej@getgeek.se](mailto:hej@getgeek.se)** and we will
adjust it.
