Click the restore button on any backup row to open the restore dialog. You get three choices.
Restores every file from the backup to your server. The existing files in your backed-up directories are removed and replaced with the backup contents. Simple, comprehensive, no decisions required.
Pick exactly which files and folders to restore. Useful when you just need one config file or a specific world save from last Tuesday. The selected files are extracted to a staging directory first, then moved into place. This keeps things clean if something goes wrong mid-restore.
Restore to a different server that runs the same game. Handy for cloning setups or migrating between servers. Only servers with a matching game profile will appear in the list. Custom profile backups cannot be cross-restored.
All restores will stop your server. The server is shut down, files are written, and then the server is restarted automatically. Plan accordingly.
Before the restore even begins, Checkpoint™ verifies the SHA256 hash of the backup archive in storage. If the data does not match what was originally uploaded, the restore stops immediately and tells you why. Your server is never touched.
Once you confirm (and the integrity check passes), the restore goes through these stages:
You can watch this progress in real-time from the backups page. A progress indicator appears on the backup row showing which stage the restore is currently in.
The file selector shows a tree view of everything in the backup. Click folders to expand them. Check individual files or entire folders. When you check a folder, everything inside it is selected recursively.
If a folder is partially selected (some files checked, some not), the checkbox shows an indeterminate state. This is not a bug. It is doing its best.
You can only have one active restore per server at a time. If a restore is already running, the restore button will be disabled. Restores that hang for more than 45 minutes are automatically marked as failed.
Was this article helpful?
On this page