ambiser
/
btrbk
mirror of https://github.com/digint/btrbk
9
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

documentation: README.md: minor fixes in example

pull/112/merge
Cerem Cem ASLAN 2017-04-29 19:47:04 +03:00 committed by Axel Burri
parent b58817d5af
commit ed80bccc79
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -121,7 +121,7 @@ When playing around with config-files, it is highly recommended to
check the output using the `dryrun` command before executing the check the output using the `dryrun` command before executing the
backups: backups:
btrbk -c myconfig -v dryrun btrbk -c /path/to/myconfig -v dryrun
This will read all btrfs information on the source/target filesystems This will read all btrfs information on the source/target filesystems
and show what actions would be performed (without writing anything to and show what actions would be performed (without writing anything to
@ -135,11 +135,15 @@ Example: laptop with usb-disk for backups
In this example, we assume you have a laptop with: In this example, we assume you have a laptop with:
* a disk having a btrfs volume mounted as `/mnt/btr_pool`, * a disk having a btrfs root subvolume (subvolid=5) mounted on
containing a subvolume `rootfs` for the root filesystem and a `/mnt/btr_pool`, containing a subvolume `rootfs` for the root
subvolume `home` for the user data. filesystem (i.e. mounted on `/`) and a subvolume `home` for the
user data,
* a directory or subvolume `/mnt/btr_pool/btrbk_snapshots` which
will hold the btrbk snapshots,
* a backup disk having a btrfs volume mounted as `/mnt/btr_backup`, * a backup disk having a btrfs volume mounted as `/mnt/btr_backup`,
containing a subvolume `mylaptop` for the incremental backups. containing a subvolume or directory `mylaptop` for the incremental
backups.
Retention policy: Retention policy: