summaryrefslogtreecommitdiff
path: root/obnam.md
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2021-10-24 09:59:45 +0300
committerLars Wirzenius <liw@liw.fi>2021-10-24 11:37:20 +0300
commit574b8e2c74f3174b15d3d80a21d86cbb10268b15 (patch)
tree2eb1f525826e0dba2bfe67e964c07792d20dd52c /obnam.md
parent60cb5be04ecd313f4ea508f66951957d9644fa01 (diff)
downloadobnam2-574b8e2c74f3174b15d3d80a21d86cbb10268b15.tar.gz
feat! store schema version of generation database in the db
Add a new mandatory database table "meta" to the SQLite database the stores information about the files in a backup generation. The idea is for future versions of the Obnam client to be able to be able to restore from backups made by older -- or newer -- versions of Obnam, as far as is reasonable. Add the `obnam gen-info` command to show information about the generation metadata. Sponsored-by: author
Diffstat (limited to 'obnam.md')
-rw-r--r--obnam.md28
1 files changed, 28 insertions, 0 deletions
diff --git a/obnam.md b/obnam.md
index 02634f0..d363069 100644
--- a/obnam.md
+++ b/obnam.md
@@ -1768,6 +1768,34 @@ exclude_cache_tag_directories: false
~~~
+## Generation information
+
+This scenario verifies that the Obnam client can show metadata about a
+backup generation.
+
+~~~scenario
+given an installed obnam
+given a running chunk server
+given a client config based on smoke.yaml
+given a file live/data.dat containing some random data
+given a manifest of the directory live in live.yaml
+given file geninfo.json
+when I run obnam backup
+when I run obnam gen-info latest
+then stdout, as JSON, has all the values in file geninfo.json
+~~~
+
+~~~{#geninfo.json .file .json}
+{
+ "schema_version": {
+ "major": 0,
+ "minor": 0
+ },
+ "extras": {}
+}
+~~~
+
+
# Acceptance criteria for backup encryption
This chapter outlines scenarios, to be implemented later, for