From 4e36c5002c90db38caa30cde1bbafd86d1355375 Mon Sep 17 00:00:00 2001 From: Jean-Paul Calderone <exarkun@twistedmatrix.com> Date: Thu, 20 Jan 2022 18:44:08 -0500 Subject: [PATCH] This is going to be a design for a different system now. --- docs/source/designs/backup-recovery.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/source/designs/backup-recovery.rst b/docs/source/designs/backup-recovery.rst index b271a8c..d8a46d8 100644 --- a/docs/source/designs/backup-recovery.rst +++ b/docs/source/designs/backup-recovery.rst @@ -10,8 +10,9 @@ ZKAP Database Backup / Recovery **Contacts:** Jean-Paul Calderone **Date:** 2021-11-08 -This is a design for a system in which *another component* can perform consistent backups of the internal ZKAPAuthorizer database which can be used to recover that database in the event primary storage of that database is lost. -The system does *not* allow ZKAPAuthorizer to maintain backups *on its own*. +This is a design for a system in ZKAPAuthorizer continuously maintains a remote backof of its own internal state. +These backups are made onto the storage servers the Tahoe-LAFS node into which ZKAPAuthorizer is loaded is connected to. +These backups can be used to recover that database in the event primary storage of that database is lost. Rationale --------- -- GitLab