Server health and backups

Server health

Server health runs live checks each time it is opened:

• the database, and a test write to the storage drive, with its free space and storage layout;
• the schema: whether every database upgrade step this release knows has run (see The database);
• encryption at rest: off, on with everything sealed, or on with data still to seal (and any backups still holding plaintext);
• backups: green with a recent verified backup, amber with none yet, an old one, no schedule or a failed copy, red when the last attempt failed or was refused;
• the public address phones use, and whether it answers as this server;
• submissions on disk that are not in the index, and the start-up re-index;
• phones waiting for approval;
• quality-check runs of the last day, the database's size, and versions: the engine, the form runtime, and the Joripo Collect app offered;
• the recent warnings and errors, kept across restarts (the newest 500).

A data-loss risk (a storage root on a container's disposable disk in production) is reported here and loudly in the log.

Backups

Backups shows the newest verified backup (when, size, files, submissions), every backup with its SHA-256, whether it was copied to the second disk, the room left on the disk and how backups are set up, with a download of each and Back up now (in the background). A backup marked plaintext was made before encryption at rest was switched on; one marked older key holds data sealed under a key that has since been rotated. Every download and every Back up now is recorded.

How backups work, and the restore runbook: Backups and restore.