Backups carry only what Anthias needs, and restores check the version

A backup you download from the Settings page now holds your settings and content and leaves out half-finished uploads, and a restore stops before changing anything if the backup's database is newer than the player can read. If you turned on HTTPS, keep your own copy of its certificate, because backups no longer include it.

From Anthias 2026.09.0, "Get backup" and "Upload & recover", under Backup & restore on the Settings page, work only with what Anthias runs on: the settings file anthias.conf, the database, the backups folder of database dumps, the default assets list and your content. Before, a backup took everything in ~/.anthias and ~/anthias_assets. Other files that sit in ~/.anthias, such as the certificate and key that bin/enable_ssl.sh installs in ~/.anthias/ssl, are no longer put in a backup, and a restore won't write them back. If you rely on those, keep your own copy.

Half-finished uploads and downloads in the content folder are left out too. They can be gigabytes of something nobody finished sending, and they only made the archive bigger.

Restores check the version

Each backup now records the Anthias release and the version of the database it came from. A backup whose database is newer than the restoring Anthias understands is refused before anything is written, with a message to upgrade Anthias to at least the release that made it. A backup from an older version restores, and its database is brought up to date right after. Backups made before 2026.09.0 carry no version, so they count as older and still restore.