Backups

Create

Create backup under Backups packs all your server files into an archive. You can give it a name; if you leave it empty, the date and time are used. How many backups you may keep at once is shown at the top under Backup slots; if all are in use, delete an old one first. Each backup shows its status: Waiting, Running, Done, Failed.

The cleanest way is to create a backup while the server is stopped. While it is running, the world may be in the middle of being written, and that can show up when you restore. A backup of a running server can also briefly cost performance.

Automatic

You set up a backup at a fixed time under Schedules, action Create backup. If all slots are in use, the run fails and the error appears in the list; nothing is deleted automatically.

Restore

Restore replaces all current server files with the state of the backup. Anything added since then is gone afterwards. To confirm, you type "restore". The dialog first offers Back up first in case you want to keep the current state, and recommends stopping the server for it. The server is briefly unavailable while restoring.

Upload from elsewhere

Upload archive takes a .tar.gz or .tgz from outside: a server you are moving from another provider, or a single-player world. The archive appears as a backup in the list and can be restored like any other. ZIP does not work here; upload a ZIP in the file manager and extract it there.

Where they are stored

Backups are stored on the same node your server runs on. They are not copied to a data centre at another location.