InvRewind vs Minecraft Backup
InvRewind
github.comMinecraft Backup
github.comSide by side
| Figure | InvRewind | Minecraft Backup |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Linux | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Minecraft Backup Software | 7.0 (#17) | 8.0 (#8) |
| License | The repository states that the project is licensed under GNU GPL v3.0. | The repository identifies its license as the MIT License. |
| Maker | The repository says it was made by MukulX. | The GitHub profile identifies the repository owner as Nicolas Chan and lists San Francisco. |
Plans
In their own words
InvRewind
InvRewind is a free, open-source inventory backup and restore plugin for Minecraft Java servers running Paper, Purpur, or Folia. It can back up player data when players die, change worlds, join, quit, or reach scheduled intervals. Administrators can create backups on demand through a GUI or force backups for one player or everyone. The restore interface can recover selected inventory, armor, offhand, ender chest, XP, or location data, and backups can be exported as shulker boxes. Storage options are YAML, SQLite, and MySQL; the documentation describes YAML for small servers, SQLite for medium servers, and MySQL for large or multi-server setups. Database operations run asynchronously, and Folia region-based threading is supported. Operators can choose fields such as health and hunger and configure per-type retention limits. Scheduled backups are disabled in the example configuration, which shows a 30-minute interval when enabled. The project is licensed under GNU GPL version 3.0 and directs support requests to GitHub Issues.
Minecraft Backup
Minecraft Backup is a Linux script for backing up Minecraft server world folders. It can create tar archives or use the restic backend, and connects to servers managed with screen or tmux, as well as servers with RCON or Docker RCON enabled. The script works with vanilla servers and does not require plugins. Backups can be scheduled with cron; the README includes an hourly example. For older backups, users can choose no deletion, sequential deletion of the oldest backup, or thin retention. Thin retention keeps the last 24 hourly and 30 daily backups, then uses available space for weekly backups. Backups are stored locally, and restoration uses tar extraction for tar files or restic restore for restic backups. The script can post backup status messages in Minecraft chat. It requires tar and a compression program such as the default gzip; RCON also requires xxd. Player data can become out of sync with world data during backups, potentially duplicating or losing items. RCON is recommended because it waits for the server to confirm saving is complete. The README also warns that Minecraft bug MC-217729 can cause a backup to fail.