Backups
A nightly unit dumps the database, keeps a fortnight locally, and mirrors both the dumps and the evidence tree off-box.
An unset destination is a failure
Once any document is archived, an unset backup destination makes the unit fail rather than log and exit zero.
The archive is what the attestation attests to, and an attestation that exists on one disk is one failure away from not existing.
What is encrypted and what is not
| Contents | Encrypted | Why |
|---|---|---|
| Database dumps | Yes, symmetric AES-256, before leaving the box | They carry other people's email addresses, and object storage is a third party holding them |
| The evidence tree | No | Other companies' public pricing pages, no personal data, and content-addressed, so encrypting it would break the deduplication that keeps it small |
Only the encrypted dump is uploaded. The plaintext dump stays on the box beside the database it came from, where encryption would add nothing.
If no passphrase exists and the destination is object storage, the run fails rather than sending the dump in clear. The waiver is an environment variable, and it is deliberately awkward.
Copy, never sync
Off-box is where a longer history belongs, so the local fortnightly sweep must not reach through and delete it.
A missed night catches up on the next run rather than leaving a hole.
A separate credential
Vitna's own bucket and Vitna's own token, not shared with the other project on the box. Sharing one would mean rotating either breaks the other, and a compromise of one exposes both.
