From 23d30b4816d2711ead4da9df34b2b104695ecb2a Mon Sep 17 00:00:00 2001
From: Jean-Paul Calderone <exarkun@twistedmatrix.com>
Date: Mon, 24 Jan 2022 10:41:23 -0500
Subject: [PATCH] mention litestream

---
 docs/source/designs/backup-recovery.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/source/designs/backup-recovery.rst b/docs/source/designs/backup-recovery.rst
index 7c9c07d..c861377 100644
--- a/docs/source/designs/backup-recovery.rst
+++ b/docs/source/designs/backup-recovery.rst
@@ -8,7 +8,6 @@ ZKAP Database Backup / Recovery
 *Delete the bits in italics*
 
 **Contacts:** Jean-Paul Calderone
-**Date:** 2021-11-08
 
 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.
@@ -123,8 +122,9 @@ SQLite3 has a (W)rite (A)head (L)og mode where it writes out all database change
 All changes could be captured this way and then uploaded to the backup location.
 The set of files will be smaller than new copies of the database and save on bandwidth and storage.
 
-This requires making sure to use the database in the correct mode.
-It is likely also sensitive to changes made outside of the control of the ZKAPAuthorizer implementation.
+This idea is implemented by https://litestream.io/ as a stand-alone process which supports an SFTP server as a backend.
+A Tahoe-LAFS client node can operate as this SFTP server
+(though ours currently does not).
 
 Application-Specific Change Journal
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
GitLab