Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Z
ZKAPAuthorizer
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Administrator
ZKAPAuthorizer
Commits
118d6c7d
Commit
118d6c7d
authored
3 years ago
by
Jean-Paul Calderone
Browse files
Options
Downloads
Patches
Plain Diff
This other kind of journal idea
parent
4e36c500
Branches
Branches containing commit
No related tags found
1 merge request
!293
Design document for replication and recovery system
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/source/designs/backup-recovery.rst
+15
-0
15 additions, 0 deletions
docs/source/designs/backup-recovery.rst
with
15 additions
and
0 deletions
docs/source/designs/backup-recovery.rst
+
15
−
0
View file @
118d6c7d
...
...
@@ -57,6 +57,7 @@ so that I can use all of the storage that I paid for before I lost my device.
* At least 500 GiB-months of unused storage-time can be recovered.
* At least 50 GiB-months of error-state ZKAPs can be recovered.
* At least 100 vouchers can be recovered.
* Recovery using ZKAPAuthorizer with schema version N can be performed with a backup at schema version <= N.
Backed Up ZKAPs
~~~~~~~~~~~~~~~
...
...
@@ -74,6 +75,8 @@ so that I can use the system without always worrying about whether I have protec
* In particular, no extra steps are required for ZKAP or voucher backup.
* Changes to a database at schema version N can be backed up even when the backup contains state from schema version <= N.
*Gather Feedback*
-----------------
...
...
@@ -123,6 +126,18 @@ The set of files will be smaller than new copies of the database and save on ban
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.
Application-Specific Change Journal
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ZKAPAuthorizer itself could write a log in an application-specific format recording all changes it makes to the database.
This log could be uploaded to the backup location or executed against data stored in the backup location.
This log will be smaller than new copies of the database and save on bandwidth and storage.
This involves non-trivial implementation work in ZKAPAuthorizer to capture all changes and record them in such a log.
It also requires logic to play back the log to recover the state it represents.
It may also be sensitive to changes made outside of the control of the ZKAPAuthorizer implementation -
though with enough effort it can be made less sensitive than the other log playback based approaches.
Application SQL Log
~~~~~~~~~~~~~~~~~~~
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment