Backups and recovery

Database and volumes

The complete state of Fahrtenbuch lives in the PostgreSQL database and the Docker volumes defined in docker-compose.yml.

• Create a consistent database backup before every upgrade or migration.
• Store copies off-host and test the restore from time to time.
• docker compose down keeps the volumes; docker compose down -v deletes them, including the database and backups. Never use -v for a routine restart.

System-wide backup

Administration › Backup & restore exports all user profiles and settings, vehicles, trips, all GPS points and upload batches, tags and assignments, change records, archived data and the central system settings as a JSON file, with a SHA-256 checksum.

Not included, for security reasons: password hashes, TOTP secrets, passkeys, refresh sessions, reset, pairing and push tokens.

Restoring

1. Choose the export file and Check system restore. The import runs inside a database transaction that is rolled back, so nothing is changed yet; you see the number of new and updated users, vehicles, trips and points, and any notes.
2. Optionally choose Restore central system settings – this overwrites map, tracking and pairing defaults.
3. Type the confirmation phrase and Restore checked system backup.

The restore merges data: existing users are matched by ID or e-mail address; the home address of existing users is not changed. Newly created user accounts are disabled and need a new password, because passwords are not part of the backup.

Personal backup

Each user can download and restore a backup of their own data under Profile › Backup & restore (see profile).

The Android app has its own backup for local data: see app backup.