# How many Rust server backups should you keep on the host?

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md)

Decide which dates you need to restore. Measure the space those copies take, then add room for a new backup while the old ones are still there. Check which drive the backup job writes to as it runs.

## Estimate space for your backup copies

Use the size of a finished full backup. Enter the total space set aside for these copies, including space they already occupy. Leave room for the game and temporary files outside that amount.

**Worked example** Seven full copies at 8 GB use 56 GB. With 70 GB set aside, the next copy fits with 6 GB to spare before cleanup. Incremental or shared-block backups use a different calculation.

## Count recovery points by date

If you keep seven copies and normally back up once a day, two extra before-change copies can push out two older daily points. Look at actual dates in the backup list. Keep a separate copy of a point you must retain beyond that window, such as the last good save before a map change.

Decide how far back you need to go to catch a problem you might notice late. A copy from this morning is useful after a crash. It gives you no way back to a configuration that was already missing by then.

## Measure the space your method actually uses

For separate full archives, use the stored size of the largest recent completed archive you expect to keep taking. Eight 2 GB archives take about 16 GB. If a ninth is written in the same place before an old one is removed, allow another 2 GB. If the backup job also stages a working copy, check its location and peak size while a job runs. If Rust saves to the same drive, leave room for the game to write its next save and logs as well.

For backups that share data between snapshots, compare the total stored size before and after several comparable runs. A full restore can be much bigger than the additional space one snapshot used. Include a busy day in your measurements and measure again after a map or plugin change. Where the staging and backup folders are on different drives, check the space each drive needs separately.

| Example on one drive | Room |
| --- | --- |
| Eight archives around 2 GB each | 16 GB in use |
| Next archive before cleanup | 2 GB free |
| Temporary files, new saves and logs | Add what you measured on this drive |

## Check the next backup before relying on the estimate

Lowering retention can remove older copies. Before changing the count, copy any point you need to a separate location and open it there. If space is tight, make the copy on another drive. Leave the running world and its rotated saves in place.

After the next job, check its recorded completion, the oldest needed date, and how much free space remains. If the next backup can finish but leaves too little room for the game to save, move backup storage or revise the history you retain.

## Sources

- [Facepunch guide to world saves and rotated copies](https://wiki.facepunch.com/rust/Getting-Started_w-Server)
- [Restic documentation on keeping and removing backup history](https://restic.readthedocs.io/en/stable/060_forget.html)
- [Restic backup and restore documentation](https://restic.readthedocs.io/en/stable/manual_rest.html)

## Related resources

- [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md)
- [How often should you back up a Rust server?](https://rustsc.com/learn/recovery/rust-backup-frequency-and-manual-checkpoints/index.html.md)

---

HTML version: https://rustsc.com/learn/recovery/keep-enough-rust-backups-without-filling-disk/
