summaryrefslogtreecommitdiff
path: root/obnam.md
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2020-09-28 09:10:45 +0300
committerLars Wirzenius <liw@liw.fi>2020-10-03 10:34:56 +0300
commit864e20652458c1a4ae09c882ad3e29d6b0988b06 (patch)
tree2e08a43a4deb3759153105a8a3a4495faa3f9121 /obnam.md
parent164c5bfc707e21ebc1f1bf6bfb89e4adc2332ef0 (diff)
downloadobnam2-864e20652458c1a4ae09c882ad3e29d6b0988b06.tar.gz
feat: add rudimentary backup client
Also, a bit of logging for server.
Diffstat (limited to 'obnam.md')
-rw-r--r--obnam.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/obnam.md b/obnam.md
index d4a2e35..0dedde2 100644
--- a/obnam.md
+++ b/obnam.md
@@ -329,6 +329,13 @@ one directory can be backed up and restored, and the restored files
and their metadata are identical to the original. This is the simplest
possible, but still useful requirement for a backup system.
+~~~scenario
+given a chunk server
+and a file live/data.dat containing some random data
+when I back up live with obnam-backup
+then backup command is successful
+~~~
+
## Backups and restores
These scenarios verify that every kind of file system object can be