diff options
author | Lars Wirzenius <liw@liw.fi> | 2020-11-13 07:36:34 +0000 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2020-11-13 07:36:34 +0000 |
commit | 179993f3bdd5e5d4dd728fc2a8f5d63274f95966 (patch) | |
tree | 5595fe6c724a15d445dd64f46fefaa94db846174 /obnam.md | |
parent | 39e23fb3b16cb6777d8e63e9e2dc59ab6f908d67 (diff) | |
parent | a2d15ccf200ae449a64cd895615a89ec42b4ab6a (diff) | |
download | obnam2-179993f3bdd5e5d4dd728fc2a8f5d63274f95966.tar.gz |
Merge branch 'subplot' into 'main'
Subplot
See merge request larswirzenius/obnam!9
Diffstat (limited to 'obnam.md')
-rw-r--r-- | obnam.md | 14 |
1 files changed, 12 insertions, 2 deletions
@@ -306,10 +306,20 @@ 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 +given an installed obnam +and a chunk server +and a client config based on smoke.yaml and a file live/data.dat containing some random data -when I back up live with obnam-backup +when I invoke obnam-backup smoke.yaml then backup command is successful +and backup generation is GEN +when I invoke obnam-restore smoke.yaml <GEN> restore.db rest +then data in live and rest match +~~~ + +~~~{#smoke.yaml .file .yaml .numberLines} +root: live +dbname: tmp.db ~~~ ## Backups and restores |