{% extends "base.jinja2" %} {% block title %}Backups - DarkflameServer{% endblock %} {% block content %}
Loading…
| Backup | Made | Size | Check | Actions |
|---|---|---|---|---|
| Loading… | ||||
A backup is the database only. These files next to the server change rarely; keep a copy of them somewhere safe (not with the downloadable backups). Two-factor secrets in the database are encrypted with the two-factor key, so a backup restored without that key locks out everyone who uses two-factor login.
A backup contains every account's password hash and email address. Downloading one asks for your
password (and two-factor code) again, and is written to the audit log and sent to security webhooks. Every new backup is checked before older
ones are deleted; Verify checks one again (read-only: integrity check and row counts for SQLite, a complete dump for MySQL).
To restore, stop all servers, then for SQLite put the file in place of the database and delete the database's
-wal and -shm files (left over, they corrupt the restored copy); for MySQL load the .sql file into
an empty database with mariadb/mysql. Start the servers: migrations bring an older backup up to date.