How Often Should You Back Up a Game Server?
A simple backup plan for game servers: how often to back up for your activity level, how many copies to keep, the 3-2-1 rule and testing restores.
4 min read · Updated Sep 23, 2026 · By GuavaHost Team
How often you should back up comes down to one question: how much progress could your players stand to lose? This guide turns that into a simple plan you can set up in a few minutes, covering how often to back up, how many copies to keep, the 3-2-1 rule, and the step almost everyone skips: testing a restore.
Start with the question that sets the schedule
The time between backups is the most you can ever lose. Back up once a day and a disaster at 11pm costs up to a day of building. Back up every 6 hours and it costs up to 6. So match the schedule to how much happens on your server, not to a number someone else picked.
A schedule for your kind of server
| Your server | How often | What to keep |
|---|---|---|
| A few friends, a few sessions a week | Once a day, or after each session | The last 7 days |
| An active group that plays most evenings | Twice a day | 3 to 7 days, plus one weekly copy |
| A busy public server, or one with an economy | Every 4 to 6 hours | 2 days of those, daily copies for 2 weeks, weekly copies for a month |
| A Rust server | Daily, plus one right before each wipe | The current wipe, plus your pre-wipe copy for plugin data and configs |
| Any server, before a risky change | A manual backup, every time | Until you are sure the change worked |
Risky changes include game updates, new mods or plugins, config edits, version changes and anything you are about to "just try". A manual backup takes seconds and it is the one that saves you most often.
Work within your backup slots
On GuavaHost, the Backups tab shows how many backups your plan can hold at once. That number decides your retention. If your plan holds 5 and you back up nightly, you always have the last 5 nights. If you back up every 6 hours, those same 5 slots cover barely more than a day, so busy servers need an off-server copy even more. When the slots are full, delete the oldest you no longer need, or a new backup cannot be created. Our backups guide covers the details.
The 3-2-1 rule
The classic rule for data you care about:
- 3 copies of your data,
- on 2 different kinds of storage,
- with 1 copy off-site.
For a game server that looks like this:
- The live server itself. Copy one.
- Backups in your panel. Copy two. Fast to restore, and the right tool for everyday mistakes.
- A downloaded copy on your own computer or cloud drive. Copy three, and the one only you control. It protects you from the things panel backups cannot, like deleting every backup by mistake, or losing access to the account.
Download a copy weekly, and always before anything big like a version upgrade. You can download a backup from the Backups tab, or pull the world folder over SFTP.
What a backup includes, and what it does not
A panel backup captures your server's files: the world, configs, plugins, mods and their data. It does not include MySQL databases you created on the Databases tab. Those live on a separate database server, not in your files. If your plugins keep player data, economies or permissions in a database, export it separately using the plugin's own export command or a MySQL client, and keep that export with your backups. See setting up a MySQL database.
Set it up once and let it run
- Open the Schedules tab and create a schedule, for example
Backup every 6 hours. - Set the timing. For every 6 hours, set the minute to
0and the hour to*/6. - Add a task and choose Create backup as the action.
- On Minecraft, add a Send command task that runs
save-alljust before the backup, so the world on disk is fully up to date. - Save, and check the Backups tab after the first run to confirm it worked.
Keep backups away from your scheduled restart time so the two do not overlap.
Test a restore before you need one
A backup you have never restored is a hope, not a plan. Every month or so:
- Download a recent backup.
- Open it on your own computer and check the world is actually there. A Minecraft world folder can be opened in single player, and for Valheim the
.dband.fwlpair should both be present. - Confirm the size looks right. A backup that is suddenly much smaller than the last one is worth investigating.
Game-specific safety nets
Some games keep their own rolling saves as well. Valheim keeps .old copies of the world, and Terraria writes a .wld.bak. They are useful for a corrupted save, but they sit on the same disk and only go back one save, so they do not replace real backups. See Valheim world backups, Terraria world files and Dragonwilds backups.
Common mistakes
- One backup, overwritten every night. If the problem goes unnoticed for two days, it is in the backup too.
- Every copy on the same server. Fine for everyday mistakes, not for bigger problems.
- Restoring without backing up first. A restore overwrites the current files. Take a fresh backup of the current state first, in case you change your mind.
- Forgetting the database. Your world comes back, but everyone's balance and ranks do not.
If a griefer has already hit your world, our guide to recovering a griefed server walks through picking the right backup.
Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.
- backups
- backup schedule
- 3-2-1 rule
- restore
- disaster recovery
Still need help? Our team is online 24/7 to answer questions.