Minecraft Server Backup: How to Back Up & Restore

A Minecraft server backup is a copy of your world and settings that saves the project when something goes wrong: griefing, a corrupted world, a bad plugin or one careless command. You can make a copy automatically in the panel, manually over SFTP or with a plugin — and the rollback takes minutes if you've prepared in advance.

Why you even need a Minecraft server backup

Anyone who's run a server for longer than a couple of weeks eventually hits the "it's all gone" moment. The scenarios repeat over and over:

Griefing. Someone walked in with permissions or an exploit and flattened the spawn and other players' builds in ten minutes. Without a copy, you're rebuilding by hand, block by block.
A corrupted world. A sudden power loss or a killed process mid-write, and a region of the world breaks. Players fall into the void and chunks won't load.
A bad plugin or mod. You drop in a fresh jar, restart — and it clashes with the core, wipes entities or breaks the economy. You wish you could roll back to before the install.
A version update. You bumped Minecraft to a new version, something didn't carry over, and now there's nothing to revert to.
A command mistake. A single /fill or /setblock with the wrong coordinates can bury half the spawn in stone.

In every one of these cases, a backup is the only thing standing between "rolled back in five minutes" and "starting the world over and losing players." Plenty of these same situations also cause performance drops — if your server is lagging, the culprit is sometimes corrupted chunks too, and a clean copy of the world helps rule that out.

What exactly you should back up

A backup of "the whole server" is overkill — you can re-download the core and Java any time. What you need to back up is what can't be recovered: the unique data of your project.

What	Where it lives	Why
World and dimensions	`world/`, `world_nether/`, `world_the_end/`	Every build, the terrain, chests, entities
Plugins and mods	`plugins/` or `mods/`	The jars themselves and their versions
Configs	inside `plugins/`, `config/`	WorldGuard regions, LuckPerms permissions, warps, economy
Server settings	`server.properties`	Port, slots, view-distance, gamemode, seed
Databases	MySQL / SQLite	Balances, punishments, plugin data stored outside the world

One file worth calling out separately is server.properties — it's a single small file, but it holds the world seed and the gamemode, and losing it stings. And if your plugins write data to MySQL (banks, ban lists, statistics), a copy of the world folder isn't enough: the database has to be dumped separately, otherwise after a rollback the economy and punishments will drift out of sync with the builds.

Three ways to make a backup

1. Automatic backups in the panel

The most reliable option is scheduled backups right in your control panel. You set the frequency, and the system takes the copy on its own and keeps it separate from the live server. On Elysium these backups are automatic and free on every plan: they're created in the Pterodactyl panel, and a rollback is a couple of clicks. The main upside is that the copy sits outside your game process, so even a full server crash won't touch it.

2. Manually over SFTP

The classic route for full control. You connect over SFTP and download the world folders and configs to your computer or to the cloud. Before copying on a running server, always flush the world to disk, or some chunks will stay only in RAM:

save-off
save-all
# copy world / world_nether / world_the_end
save-on

save-off temporarily disables auto-saving, save-all forces the world to be written to disk, and save-on turns everything back on. That way the copy is guaranteed to be consistent.

3. Scheduled plugins

If your host can't do automatic backups, plugins come to the rescue — for Paper/Spigot, for example, there are solutions that archive the world on a timer and drop the copies into a separate folder. Their downside is that the archive stays on the same disk as the server: if you lose the disk, you lose both the original and the copy. So a plugin is an addition to an external backup, not a replacement for it.

The 3-2-1 rule

Keep 3 copies of your data, on 2 different types of media, with at least 1 off the server (the cloud or your PC). Then neither a disk failure nor a hacked panel will leave you without a world. For a home server this sounds like overkill, but it's exactly the "one copy right next to the original" that lets people down most often.

How to make a backup and roll back the world: step by step

Below is a working sequence for both creating a copy and restoring one. Save it so you're not improvising in a stressful moment.

Stop the server or pause saving. Stop the server, or run save-off and save-all in the console, so the world is written to disk in full and the copy doesn't come out corrupted.
Copy the data you need. Archive the world, world_nether and world_the_end folders, plus plugins/ or mods/ with their configs and the server.properties file. If you use MySQL, dump the database.
Store the copy somewhere safe. Download the archive over SFTP to your own computer or to the cloud. By the 3-2-1 rule, keep the copy on at least two different media and one of them off the server.
Rollback: stop the server. Before restoring, stop the server completely so it doesn't overwrite files while you're copying.
Replace the files from the backup. Delete or rename the current world folders and unpack the contents of the chosen backup in their place. Restore the plugins, configs and database dump if they changed.
Start it up and check. Boot the server, jump into the world and make sure builds, plugins and inventories are intact. Tell players which point in time the progress rolled back to.

How not to lose player progress

A world rollback always means losing everything built after the moment of the copy. To keep the grumbling to a minimum:

Roll back to the freshest working copy, not to "yesterday's just in case" — you lose less time.
Warn players ahead of time which point the world will return to: "we're rolling back to 2:00 PM, everything after that is gone."
If only a small area is damaged, don't roll back the whole world. A logger plugin like CoreProtect keeps a history of blocks and lets you undo a specific player's griefing surgically, preserving everyone else's progress.

Check that the backup actually works

A copy you've never restored is a hope, not insurance. At least once, restore the world from a backup on a test server and make sure the archive isn't corrupted and unpacks cleanly. "There's a backup, but it won't open" is its own painful genre of world-loss stories.

Where backups happen on their own

Regularity is the weak spot of manual copies: people forget about them right up until the day they're needed. So when choosing a host, automatic backups are worth treating as a must-have feature, not a bonus. On Elysium they're included free on every plan, run on a schedule and are stored separately from the server, while fast NVMe Gen4 takes a copy of the world in seconds, barely touching TPS. If you're just setting up a server, turn on automatic backups right away and make the first copy by hand, so you have a rollback starting point from day one. You can build a plan with automatic backups on the order page.

Frequently asked questions

How often should I back up my Minecraft server?

For an active server, at least once a day automatically. Before any risky action (updating the core, installing a new plugin or mod, editing the world by hand), make a separate manual copy. On large projects with heavy building it makes sense to back up every 6-12 hours.

Can I roll back just one region of the world without touching the rest?

Yes, but not with a regular backup. A full copy rolls back the entire world. For a targeted rollback of a damaged area, people use logger plugins like CoreProtect — they keep a history of blocks and let you undo a specific player's actions within a given radius without losing the rest of the server's progress.

Does a backup slow the server down while it's being created?

Briefly, yes, because archiving the world puts load on the disk. On slow HDDs this causes noticeable lag. On NVMe Gen4 with read speeds around 7 GB/s a copy is taken in seconds and TPS barely dips. That's why on fast disks you can back up more often with no risk to your players.

Are backups paid on Elysium?

No. Automatic backups are included free on every plan and run on a schedule right inside the Pterodactyl panel. Restoring takes a couple of clicks, and the copies themselves are stored separately from the live world, so a server crash won't touch them.

What do I do if there are no backups and the world is broken?

First, stop the server so you don't write over the damaged data. Then check whether the host or the players' folder has a copy. If a logger plugin is enabled, restore the blocks through it. Going forward, set up automatic backups — it's the only reliable protection against losing your world.

🚀

Launch your server in 2 minutes

Pick a plan, server software and modpack — we'll spin up your server on fast Ryzen nodes with NVMe and DDoS protection. Migration from your old host is free.

Create a server View plans