Backups and restores

The Backups tab makes a full copy of your server files as one archive. Use it before doing anything risky (version upgrades, big plugin changes, world edits) and you're one click from undoing a disaster.

Make a backup

Stop the server. This isn't strictly required, backups work while running, but a backup taken mid-write can catch a world file half-saved. For anything important, stop first.
Backups tab → Create Backup. Give it a name you'll recognize later ("before 1.22 update", not "backup 2").
Wait for it to finish. Large servers take a few minutes. Start the server after it completes.

Download a copy

Every backup has a Download button. Get anything you actually care about onto your own PC too. Backups on the node don't help if the node dies.

Restore

Backups tab → three-dot menu on the backup → Restore. Confirm. The server needs to be stopped first.

Two things to understand before you do that:

Restore overwrites current files with the backup's contents. There is no undo. If you want the option to go back to today, take a backup of the current state before restoring the old one.
Restore replaces files, it doesn't diff them. Everything the backup contains becomes the current state.

You have a limit, and rotation is automatic

Your plan includes a set number of backups. When you hit the limit and create a new one, the panel deletes the oldest backup automatically to make space . If there's a backup you must keep forever, click its lock icon. Locked backups are skipped by rotation and can't be deleted by accident.

If you downloaded a backup and lost the panel copy

Upload the archive back via Files or SFTP, right-click → Unarchive into a fresh folder, then stop the server and move the contents into place. If this makes you nervous, open a ticket and we'll do it with you.