Most Minecraft worlds are not lost to a hardware failure. They are lost to a griefer with creative mode, a WorldEdit command with the wrong coordinates, a mod update that eats chunks, or someone deleting the wrong folder at two in the morning. All four of those are survivable with a backup and unrecoverable without one. This guide covers making backups on a Loafhosts server, scheduling them so you stop having to remember, keeping one safe from rotation, getting a copy off the server entirely, and the part people skip until it is too late, which is testing that a restore actually works.
What Is In a Backup
A server backup captures your server’s files as they are at that moment. For a Minecraft server that means the world folder with all its chunks and player data, your server.properties, your plugin or mod jars and their configs, and the operator, whitelist and ban lists. In other words, everything needed to bring the server back exactly as it was.
What it does not capture is anything living outside the server, so a separate database used by a plugin is not included unless you back that up too.
Note: A backup is a point in time. Anything that happens after it is not in it
Warning: A backup stored only on the same server is not a backup. If you would be sunk by losing the whole server, download a copy as well
Making a Backup in the Panel
Open your server in the LoafHub panel and pick Backups from the sidebar. The page lists every backup you have with its size and creation time, and a button to create a new one.
- Open your server in the panel and go to Backups
- Click to create a backup and give it a name you will recognise later
- Wait for it to finish, larger worlds take longer
- Confirm it appears in the list with a size against it
Name backups for the reason you took them, not the date. “Before ATM9 update” tells you what it is a month later; “Backup 4” does not.
Tip: Take a manual backup immediately before any modpack install, version change, or large plugin update
Note: Backups are stored against your server and count toward its storage, which is why old ones rotate out as new ones are made
Scheduling Automatic Backups
The backup you do not have to remember is the one that saves you. The panel’s Schedules feature can run a backup on a repeating timer, so open your server, go to Schedules, create a schedule, set when it should run, and add a task with the action set to backup.
- Open your server in the panel and go to Schedules
- Create a schedule and set the times it should run
- Add a task and choose backup as the action
- Save, and confirm the schedule shows its next run time
A schedule can hold more than one task, which is how you build a safe routine: send a warning to chat, then take the backup, then restart. Daily is enough for most servers. A busy server where a lost day would hurt is worth doing more often.
Tip: Put a
saycommand task before the backup so players know why the server is about to be busy for a momentWarning: Automatic backups rotate. If a specific backup matters, lock it, or it will eventually be replaced by a newer one
Locking a Backup So It Never Rotates
Rotation is what keeps your storage from filling up, and it is also how people lose the one backup they cared about. The panel lets you lock a backup, which marks it as protected so automatic rotation skips it. Lock the backup you took before a risky change, and lock a known-good copy of a world you would not want to rebuild.
Unlock it once you are confident the change went fine and you no longer need the fallback.
Tip: Lock the pre-update backup, verify the update over a few days, then unlock it and let it rotate normally
Note: A locked backup still counts against your storage, so do not lock everything
Getting a Copy Off the Server
A backup that lives only where the server lives shares that server’s fate. For anything you truly cannot lose, download a copy. Each backup in the list can be downloaded, which gives you an archive you can keep on your own machine or in your own cloud storage.
You can also inspect what is inside a backup before restoring it. The panel can show a backup’s contents, which is how you confirm a particular world folder or config file is really in there rather than finding out during a restore.
Tip: Keep at least one downloaded copy of a world you would be upset to lose, stored somewhere other than the server
Note: Check a backup’s contents before you rely on it, especially the first one you take after changing your setup
Restoring Without Making It Worse
A restore replaces your current server files with the ones from the backup. That is the point, and it is also the risk, because anything built since the backup was taken disappears.
- Stop the server first
- Take a fresh backup of the current state, even the broken one, so a restore of the restore is possible
- Choose the backup you want and restore it
- Start the server and check the world, player inventories, and your plugins or mods
Step two is the one people skip. If you restore straight over a broken server and then discover the backup was older than you thought, you have lost both states.
Warning: Restoring overwrites the current server. Everything built since that backup is gone
Warning: Stop the server before restoring. Restoring under a running server can produce a mix of old and new files and a corrupted world
Doing It By Hand From the Console
If you want to snapshot the world without the panel, Minecraft has its own save commands. These are also worth knowing because they are what a safe file-level copy needs.
| Command | What it does |
|---|---|
save-all flush | Writes everything in memory to disk immediately |
save-off | Stops the server writing to the world, so files stay still while you copy |
save-on | Turns saving back on |
The sequence is save-off, then save-all flush, then copy the world folder, then save-on. Copying a world folder while the server is writing to it is how you get a backup that looks fine and is quietly corrupt.
Warning: Never leave
save-offon. If the server crashes while saving is disabled you lose everything since the last saveTip: The panel’s backup already handles this correctly, the manual sequence is for when you are copying files yourself
How Often, and How Many
There is no universal answer, but the useful question is “how much progress am I willing to redo”. A creative build server that changes constantly wants daily backups and a locked copy before any big change. A small survival world played twice a week is fine with less. Modded servers deserve more attention than vanilla, because a mod update is the single most common way a world breaks.
| Server type | Suggested rhythm |
|---|---|
| Small survival with friends | Daily automatic, keep a few |
| Busy public server | Daily automatic, plus manual before any change |
| Heavily modded | Daily automatic, locked backup before every mod or pack update |
| Creative or build showcase | Daily automatic, plus a downloaded copy of finished builds |
Tip: Whatever schedule you pick, test one restore. An untested backup is a guess
Frequently Asked Questions
How do I back up my Minecraft server?
Open your server in the LoafHub panel, go to Backups, and create one. It captures the world, your configs, and your plugins or mods. To make it automatic, create a schedule under Schedules with a task whose action is set to backup.
How do I automatically back up my Minecraft server?
Use Schedules. Create a schedule with the times you want, add a task, and set its action to backup. You can chain tasks in one schedule, so a common pattern is a chat warning, then the backup, then a restart.
Will restoring a backup delete my players’ items?
Restoring returns everything to how it was at the moment the backup was taken, including player inventories. Anything gained after that point is lost, which is why you should take a fresh backup of the current state before restoring.
How do I stop a backup from being deleted?
Lock it. Locked backups are skipped by automatic rotation, so they stay until you unlock them. This is what you want for a backup taken before a modpack update or a version change.
Do I have to stop the server to take a backup?
You do not have to stop it to create one in the panel, but you should stop it before restoring. If you are copying world files by hand instead, run save-off and save-all flush first so the files are not being written while you copy, then save-on afterwards.
Are my backups stored somewhere else?
Backups live with your server, which means they protect you from mistakes rather than from losing the server itself. For anything critical, download a copy from the Backups page and keep it somewhere you control.
What is the difference between a backup and the world manager?
A backup is a full snapshot of the whole server including configs and plugins. World tools manage the world files themselves. For recovering from a bad update or a griefing incident, a backup is the one you want.