How to Back Up Your Minecraft Server

Q: My backup is too large to download. What can I do?

Exclude the logs/ directory and old backups stored inside the server folder. If the world is very large (10 GB or more), use rsync over SSH for incremental transfers that only copy changed files. On a panel, ask your host about off-site storage options.

Backups are the one thing every server owner knows they should do and half of them skip until it is too late. A corrupted world or a bad plugin update can wipe months of work in seconds. A backup brings it all back. Here is how to do it properly.

What to back up

A complete Minecraft server backup includes:

World folders. These are the large ones: world, world_nether and world_the_end (names may vary). They contain every block, every chest and every entity.
Plugin data. The plugins/ folder holds configuration files and databases for each plugin. Player ranks, economy balances, homes, warps and bans live here.
Server configuration. Files like server.properties, bukkit.yml, spigot.yml and paper-global.yml contain your server settings.
The server jar. Not critical (you can download it again), but including it means the backup is a complete snapshot you can start immediately.

In short: back up everything in the server directory. Exclude logs/ if space is a concern; logs are useful for debugging but not for recovery.

Backups through the panel

If your server runs on a Pterodactyl-based panel (like HostValues), backups are built in. Go to the Backups tab and click "Create Backup". The panel compresses your entire server into an archive. You can download it, and restoring replaces the current files with the backup's contents.

Most hosting providers allow a set number of backups. Once you reach the limit, creating a new backup requires deleting an old one. Keep your most recent backup and one from a week ago as a minimum. If your provider allows more, keep daily backups for the past week and weekly backups for the past month.

Manual backups over SFTP

Connect to your server with FileZilla or WinSCP and download the entire server directory to your local machine. Store it somewhere safe: an external drive, a cloud storage service, or both. Manual backups work everywhere but require you to remember. Automating is better.

Automated backups on a VPS

On a VPS with root access, automate backups with a cron job:

#!/bin/bash
BACKUP_DIR="/home/backups/minecraft"
SERVER_DIR="/home/minecraft/server"
DATE=$(date +%Y-%m-%d_%H-%M)
mkdir -p "$BACKUP_DIR"
tar -czf "$BACKUP_DIR/backup-$DATE.tar.gz" -C "$SERVER_DIR" .
find "$BACKUP_DIR" -name "*.tar.gz" -mtime +14 -delete

This compresses the server into a dated archive and deletes backups older than 14 days. Add it to cron:

crontab -e
# Add this line:
0 4 * * * /home/minecraft/backup.sh

The backup runs at 4 AM every day. Adjust the time to your server's quietest period.

Scheduled backups in the panel

Pterodactyl supports scheduled tasks. Go to the Schedules tab, create a new schedule, set the time (for example, every day at 5:00), and add an action: "Create Backup". The panel handles the rest. You can also add a second action that sends a console command like say Server backup starting in 1 minute before the backup, so players know what is happening.

When to back up

Always create a backup before:

Updating the server version (1.21 to 26.x, or any minor update).
Installing or updating plugins.
Making major world changes (WorldEdit operations, resetting the Nether).
Changing server configuration files.

A daily automatic backup on top of these manual ones ensures you never lose more than 24 hours of progress.

How to restore a backup

Always stop the server first. Then restore:

Panel: Go to Backups, find the snapshot, click Restore. The panel replaces current files.
SFTP: Delete or rename the current server directory, upload the backup files, start.
VPS: Extract the archive: tar -xzf backup-2026-09-04.tar.gz -C /home/minecraft/server, then start.

Restoring while the server runs causes file conflicts and can corrupt data.

Testing your backups

A backup you have never tested is a backup you hope works. Once a month, restore a backup to a temporary location and start a test server from it. If the world loads and player data is intact, your system works. If not, fix the process before you actually need it.

Every HostValues Minecraft server includes panel-based backups. For automated off-site backups, a VPS gives you the scripting flexibility to store copies anywhere.

How often should I back up my server?

Daily automatic backups are the minimum for any server with active players. For busy servers with dozens of players building every day, twice daily is safer. Always create an extra manual backup before making changes like version updates or plugin installs.

Can I restore just part of a backup?

Yes. If you only need to restore a specific world, extract just that folder from the backup archive and replace it on the server. The same applies to individual plugin data files. You do not have to restore everything at once.

My backup is too large to download. What can I do?

Exclude the logs/ directory and old backups stored inside the server folder. If the world is very large (10 GB or more), use rsync over SSH for incremental transfers that only copy changed files. On a panel, ask your host about off-site storage options.

Does restoring a backup affect player inventories?

Yes. A backup is a snapshot of the entire server state at that moment. Restoring it rolls everything back: world changes, player inventories, balances, homes, all of it. Any progress made after the backup was taken is lost. This is why frequent backups matter: the more recent the backup, the less is lost.