Extract
Into a temporary folder. A cut or corrupted archive fails here.
For Minecraft server admins
A backup you never restored
is a hope, not a backup.
Restore Check does the restore drill for you: it extracts the backup into a temporary folder, checks every world and region file, the plugin jars and configs, then really starts the server. You get a report; the temporary copy is deleted.
$
cobblekit restore-check /backups/server-2026-10-17.tar.gz
Same single file as Preflight and Merge. Folders, .zip, .tar and .tar.gz backups. Add it to a weekly cron job.
Worlds
level.dat readable, every region file's chunk table checked against its real size.
Plugins
Every jar opened, every plugin config parsed as YAML.
Start
The restored server starts on a free local port; a probe checks which plugins run.
Report, then cleanup
REPORT.md, report.json and the server log. Exit code 0 only if everything passed.
Tested, not promised
Damaged on purpose, then checked
Each backup, and who noticed the problem
"Archive test" is tar -tzf / unzip -t: what most backup scripts check, if anything. It was run on the same files.
What it cannot do
- It checks the structure of every region file, not the content of every chunk: a chunk with a valid size but corrupted data is only caught if the server loads it at startup.
- Databases outside the server folder (MySQL for LuckPerms, CoreProtect…) are not in the backup and not checked.
- It needs free disk space for one extracted copy, and RAM for one test start (or use
--no-start).