Data safety: recovery that has been proven, not assumed #107
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-docs#107
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "%!s()"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
Backups exist and a weekly drill restores the git host. That is not yet the same as proven recovery. The identity provider is never restored, the disaster-recovery key has never been used, there is one daily dump with no point-in-time recovery, one operator holds every key, and one cloud credential can delete both the service and its backups.
This epic makes recovery something that has been shown to work, before anyone's data depends on it.
Tasks
Done when
A full restore of git data, the portal database and the identity provider has been run from off-site copies using only the escrowed key, and the time it took is recorded.
Horizon: Now.