On this page
- Back up the files you need to recover
- Use save commands when copying live world files
- Choose a backup plugin that fits your restore plan
- DriveBackupV2: scheduled copies with remote storage
- UltraBackup: a command-based restore option
- AutoBackupV2: incremental ZIP files
- Use Docker for a separate backup container
- Keep an offsite copy and test a restore
- Questions server owners ask about backups
- How often should I back up a Minecraft server?
- Does a Pterodactyl backup include plugins?
- Why does Multicraft only back up my world?
- How do I restore a Minecraft server backup?
- Can I back up a live server?
Key takeaways
5- Back up worlds, plugins, configs and any database data needed to rebuild your server.
- Check what your panel includes and where it stores backups; Multicraft usually backs up world files only.
- Choose a backup tool whose listed Minecraft versions match your server, and review its restore method.
- Keep a copy off the server and set a retention limit that fits your storage.
- Test a restore on a staging server before depending on a backup during an outage.
This guide is for Paper server owners who want backups that can actually recover a server, not just a pile of old files. You will decide what to include, choose an automatic backup method, keep a copy off the server and test a restore.
Back up the files you need to recover
A world-only copy may not bring back the server you had before a failure. Include your world folders, plugins, plugin configurations and other server configuration files. If your setup uses a database, decide how to back that up too. DriveBackupV2 can back up MySQL databases; check each other tool's documentation for database coverage before relying on it.
Keep more than one recent backup. A backup stored on the same server can be lost along with the server, so send copies to separate storage when your tool supports it. If your world is large, remember that keeping many copies takes storage. Chunky-generated worlds can be large too, as covered in our guide to pregenerating worlds and finding lag.
Use save commands when copying live world files
Java Edition provides /save-all, /save-off and /save-on. These commands require permission level 4. The save-off command pauses writes to world files while a copy is made, but player, advancement and statistic data are not covered by that pause. Follow it with /save-on when the copy is done.
A common live-copy sequence is to pause world saving, flush pending saves, copy the files, then turn saving back on. The flush argument saves everything immediately and can briefly freeze the server. Make sure the final step turns saving back on even if the copy fails.
Run the sequence from your server console or an RCON connection with permission level 4. Your copy script needs to issue the commands, copy the files and issue /save-on afterward. Schedule that script with your system's scheduler, such as cron, and check its logs and backup destination. The exact RCON wrapper and script depend on your server environment.
For a manual panel backup, stop or save the server as your host recommends, open the server's Backups tab and choose Create Backup. Check the ignored-files list before relying on the result. To automate it, open Schedules, create a schedule for the time you want, then add a Create Backup task. The host controls the backup limit and storage location, so ask them whether backups are stored offsite and what files are excluded.
Use the panel's backup page or a scheduled task if your host provides one. Multicraft's guide says its built-in backup usually includes world files only, not plugins or configuration, and stores the copy on the server. Use FTP to download a copy elsewhere and make a separate plan for plugins and configs.
Choose a backup plugin that fits your restore plan
These plugins differ in cloud upload, restore options and listed Minecraft versions. Check the project page for your exact server version before installing, and test the commands on a copy of your server.
| Plugin | Upload listed | Restore notes | Version listing |
|---|---|---|---|
| DriveBackupV2 | Google Drive, OneDrive, Dropbox, (S)FTP and S3-compatible storage | Can retain local and remote copies; check its wiki for restore steps | Modrinth lists 1.8 through 1.21.x |
| UltraBackup | Google Drive, SFTP or FTP | /restore <backup-file> shuts the server down; start it again manually | Modrinth lists 1.8.9 through 1.21.x |
| AutoBackupV2 | Cloud upload is not mentioned on its page | Creates ZIP files; restore by extracting and overwriting server files | Hangar lists 1.21 through 1.21.11 |
DriveBackupV2: scheduled copies with remote storage
DriveBackupV2 is a free plugin for Bukkit, Spigot, Paper and Purpur. It can upload backups to several cloud or file transfer services, back up remote (S)FTP sources and MySQL databases, and remove older local and remote copies according to retention limits.
To link Google Drive, use /drivebackup linkaccount googledrive and follow the prompts. Its default interval is 60 minutes. The delay setting controls the interval in minutes, and local-keep-count controls how many local backups to retain. The plugin also supports a day and time schedule. Review its automatic backup guide before changing these settings.
UltraBackup: a command-based restore option
UltraBackup is a free Paper and Spigot plugin with backup creation, optional Google Drive, SFTP or FTP upload, and restore commands. Its page lists exclusions and progress tracking. Restoring shuts down the server immediately, so plan to start it again manually.
Use /backup to create a copy. Its page documents /backup login and /backup code <CODE> for linking Google Drive, and /restore <backup-file> for a restore. Review the keep-last, exclude and upload settings before putting it into regular use.
AutoBackupV2: incremental ZIP files
AutoBackupV2 is a free Paper plugin that makes asynchronous incremental ZIP backups of worlds, plugins and configs, then removes old backups automatically. Cloud upload is not mentioned on its page. Restoring means extracting the ZIP and overwriting server files.
Its commands include /autobackup now to create a backup and /autobackup list to list backups. Hangar lists versions 1.21 through 1.21.11, so check the listing before installing on another version.
Use Docker for a separate backup container
If you run the itzg/minecraft-server Docker image, docker-mc-backup is a sidecar container that communicates over RCON and reads the same data volume. It can use tar, rsync, restic or rclone. Its default backup interval is 24 hours, and its RCON password default is minecraft, which you should change.
The container needs read-only access to the server's /data volume. For tar, rsync and rclone, backups go to /backups; restic uses a remote repository. Check the project instructions for the environment variables and storage destination that fit your setup.
Keep an offsite copy and test a restore
For a panel backup, ask the host whether storage is local or S3-compatible and whether you can download a copy. Pterodactyl's storage driver is configured by the panel operator, not an individual server owner. Its Backups tab offers restore and download actions for successful backups. A restore stops the server, and you may choose whether to delete current files before restoring.
For Multicraft, download the on-server world archive using the FTP details provided in the panel. Its guide says older files are renamed as numbered archives and that new backups can overwrite the oldest once the host's limit is reached. Do not treat that single on-server archive as your only copy.
On a VPS or dedicated machine, copy backups to a different disk or remote destination. The Docker sidecar supports remote methods including restic and rclone, while DriveBackupV2 and UltraBackup list remote upload options. Keep credentials private and verify that the backup job reports success.
Restore a backup on a staging server before you need it in production. Check that the world loads, plugins and configs are present, and players can join. For a production recovery, take a fresh copy of the current files first, stop the server, restore the selected backup, then start it and check the console. Our guide to updating Paper safely also explains why having a tested rollback copy matters.
Questions server owners ask about backups
How often should I back up a Minecraft server?
Choose an interval based on how much player progress you can afford to lose. DriveBackupV2 defaults to hourly backups, while docker-mc-backup defaults to every 24 hours. Monitor how long each backup takes and how much storage your retention period uses.
Does a Pterodactyl backup include plugins?
Check the ignored-files list shown when creating a backup, and ask your host what the server backup includes. The panel can exclude files and folders, so do not assume plugins or configs are included without checking.
Why does Multicraft only back up my world?
Multicraft's guide says its built-in backup usually covers world files, not plugins or configs. Use FTP to download the world archive, and make a separate copy of plugins and configuration files.
How do I restore a Minecraft server backup?
Use the restore method for the tool that created the copy, and follow its instructions about stopping or restarting the server. Restore to a test server first when possible, then check the world, plugins and configs before using the backup for production recovery.
Can I back up a live server?
Java Edition's save commands can help coordinate a live world-file copy. /save-off pauses world-file writes, but does not cover player, advancement or statistic data; use a backup tool that handles its own save sequence or plan for all needed files.
Frequently asked questions
How often should I back up a Minecraft server?
Choose an interval based on how much player progress you can afford to lose. DriveBackupV2 defaults to hourly backups, while docker-mc-backup defaults to every 24 hours. Monitor how long each backup takes and how much storage your retention period uses.
Does a Pterodactyl backup include plugins?
Check the ignored-files list shown when creating a backup, and ask your host what the server backup includes. The panel can exclude files and folders, so do not assume plugins or configs are included without checking.
Why does Multicraft only back up my world?
Multicraft's guide says its built-in backup usually covers world files, not plugins or configs. Use FTP to download the world archive, and make a separate copy of plugins and configuration files.
How do I restore a Minecraft server backup?
Use the restore method for the tool that created the copy, and follow its instructions about stopping or restarting the server. Restore to a test server first when possible, then check the world, plugins and configs before using the backup for production recovery.
Can I back up a live server?
Java Edition's save commands can help coordinate a live world-file copy. /save-off pauses world-file writes, but does not cover player, advancement or statistic data; use a backup tool that handles its own save sequence or plan for all needed files.
