A Minecraft server backup protects your world, plugin data, and configurations from operating mistakes, faulty updates, damaged files, or unwanted player changes. The most reliable approach is a combination of automatic backups in the hosting panel, regular manual SFTP backups, and a tested recovery process.
What You Should Back Up
A useful backup does not only consist of the world folder. For Vanilla servers, the world plus server.properties is often enough; with Paper, Purpur, Spigot, or Bukkit, plugin configurations, plugin databases, and additional server files are added. Therefore, back up these paths in particular:
/world/ # Overworld
/world_nether/ # Nether
/world_the_end/ # End
/plugins/ # Plugin configs
/server.properties
If you changed the world name in server.properties, the three world folders will have different names accordingly. In that case, check the level-name entry before downloading or replacing files. You can find a complete explanation of the most important settings in the guide on configuring Minecraft server.properties correctly.
Why Backups Matter
Typical cases happen quickly: griefers have destroyed parts of the world, a plugin update unexpectedly changes data, someone accidentally deletes the wrong world, or a crash leaves damaged files behind. A backup is only helpful then if it is current, complete, and restorable.
Mojang also describes in the official Minecraft help that a manual backup can be used to preserve a Java Edition world or transfer it to another device: documentation at help.minecraft.net. The same principle applies to servers: the world files must exist as a consistent copy so a restore is reliably possible.
Check Automatic Backups at game-serverhosting
At game-serverhosting, you manage your paid Minecraft server through a dashboard with technical operations features. Open the Backups section there and check which backups are available for your server.
- Open the dashboard and select the Minecraft server
- Open the Backups tab
- Check existing backups, timestamps, and options
- Create a manual backup with 1 click if needed
- Check whether automatic daily backups are active for your server
The exact availability and retention can depend on the setup, plan, or panel configuration. Therefore, do not rely only on the assumption that a backup exists; check the list of backups regularly in the dashboard.
Create a Manual Backup via SFTP
A manual SFTP backup is useful before larger changes: version changes, plugin updates, world changes, importing a map, or changes to critical configurations. Ideally, stop the server first so no world files are written during the download. If stopping is not possible, perform the backup during a quiet phase and avoid major in-game actions in parallel.
Download the relevant folders and files with an SFTP client. Create a clearly named local folder, for example with date, server name, and purpose: 2026-07-22-survival-before-pluginupdate. Also keep a short note about which server version, mod or plugin versions, and which change were planned. If you later want to import your own map, the process in the guide Upload and Switch a Minecraft World will help.
Backup Plugin: DriveBackupV2
A backup plugin can supplement scheduled backups, but it does not replace checked panel or SFTP backups. Pay special attention to the storage destination, permissions, available capacity, and whether the plugin is compatible with your server software.
# config.yml
backup-schedule-list:
- type: Backup
schedule: "0 */6 * * *" # Every 6 hours
create-before-backup: true
This schedule creates a backup every six hours. Adjust it to your player activity: a small private server usually needs less frequent backups than a public server with lots of daily building progress. Also check whether old backups are automatically deleted or rotated so storage does not fill up unnoticed.
Restore a Backup
A restore should be controlled. Inform players beforehand if progress may be lost and note the time of the backup. Then proceed as follows:
- Stop the server
- Back up the current state separately in case you need to compare later
- Extract the backup and replace files
- Check permissions and file paths
- Start the server
- Check the console for errors
- Test in-game whether the world, inventories, plugins, and important settings are correct
Do not partially replace world folders if you want a clear rollback. Mixed states from old chunks, new plugin data, and outdated configurations can create errors that are difficult to understand.
Best Practices
| What | How often | Why |
|---|---|---|
| World backup | Daily | Back up game progress |
| Plugin backup | Before updates | Rollback possible |
| Full backup | Weekly | Complete recovery |
A backup directly before a server version change is also worthwhile. If you switch between Vanilla, Paper, Purpur, Forge, or Fabric, read the guide Change Minecraft Server Version beforehand because the version, loader, and plugin ecosystem can affect recovery.
Plan Storage Space Realistically
A Minecraft world is typically 500 MB - 5 GB. Backups compressed: 30-50% less. Recommendation: keep at least 5 backups.
These values are rough guidance from the original guide, not a guarantee for every server. Large explored worlds, many players, map plugins, Dynmap data, or modpacks can require significantly more storage. Therefore, regularly check the actual size of your backups.
Check the Result
A backup is only reliable once you have checked it. Open the backup file or backup folder, check the expected world folders, and roughly compare the file size with the live server. After a test restore, you should log in and check the spawn, important builds, Nether, End, inventories, and central plugin functions.
Troubleshooting
The server does not start after the restore
Check the console and the latest log files. Common causes are incorrectly replaced folders, missing plugin files, incompatible server versions, or damaged configuration files. First restore the last working backup.
My world is empty after the restore
Check level-name in server.properties. If the server points to another world name, Minecraft creates a new world at startup. Either rename the folder accordingly or correct the entry.
Plugins lose data after the rollback
Plugin data is often located under /plugins/, but sometimes also in databases or external storage destinations. Before updates, therefore, back up not only the world, but also plugin configurations and data folders.
The backup is too large
Do not blindly delete files from the active world. First check whether old local backups, map render data, or plugin cache files are using the storage. After that, you can define a rotation strategy.
Checks, Limits, and a Safe Rollback
The guide “Create and Restore a Minecraft Server Backup” applies to the server type described in the article and the version state visible at the time of checking. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer any values unchecked to another game, loader, or server version.
Before making changes to the world, save, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.
| Checkpoint | Expected result | Abort and rollback |
|---|---|---|
| Server start | The server reaches the ready state without a new error message. | If startup errors occur, revert the change and restore the last backup. |
| Connection test | A test account can connect via the address shown in the panel. | If version or connection errors occur, compare version, port, and allowances again. |
| Function test | The specifically changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore backed-up files. |
A successful single test is not a guarantee of performance or availability. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.
FAQ
How often should I back up my Minecraft server?
For active servers, a daily world backup is a good minimum standard. Before updates, version changes, or major configuration changes, you should also create a manual backup.
Is an automatic backup in the dashboard enough?
For many everyday situations it is helpful, but you should also occasionally download a manual SFTP backup. That makes you less dependent on a single backup source.
Do I need to stop the server before a backup?
For the most consistent manual backup, yes. If world files are written while copying, the backup may be incomplete or harder to restore.
Which files are most important for a restore?
At minimum, the world folders and server.properties. For plugin servers, you should also back up /plugins/ because configurations and often game-relevant data are stored there.
Should I test backups after creating them?
Yes. At least check whether the expected files are present. Even better is a test restore during a maintenance window or on a separate copy.