A backup is useful only if you can trust it when restore day comes. Check the six controls below to see where your current Paper/Purpur recovery process is strong and where it still has gaps.
A scheduled ZIP proves only that an archive was created. A safer recovery process also verifies file integrity, rehearses restoration, accounts for data outside the server directory, protects against loss of the host itself, and reduces the chance of snapshotting partially flushed world data.
Do not rely on a normal filesystem copy during heavy writes. Coordinate Minecraft saves first, for example through RCON with save-off, save-all flush and save-on; make sure saving is re-enabled after failures, then verify the archive and test a restore on a separate directory.
No. A ZIP can exist while files are missing, changed or unreadable. Keep a per-file integrity manifest, verify the completed archive independently, and rehearse the documented restore process before an emergency.
No. PaperVault creates and verifies filesystem backups, but you still need to copy important archives away from the Minecraft VPS and separately dump any MySQL, MariaDB or PostgreSQL data used by plugins.
PaperVault 1.0.0 is for self-managed Paper or Purpur servers on a Linux VPS or dedicated host with Python 3.11+ and filesystem access. It is an administrator CLI toolkit, not an in-game plugin or a managed-host control-panel add-on.
For a manual audit, use the free backup checklist and safe restore guide.
This checker is guidance, not a guarantee that a backup will restore successfully. Always test recovery on a non-production copy before relying on it.