docs: continous_server_backup: simplify by removing need for recv.placeholder

This commit is contained in:
Christian Schwarz 2022-01-09 12:51:00 +01:00
parent 556fac3002
commit 66946df756
3 changed files with 7 additions and 10 deletions

View File

@ -9,7 +9,4 @@ jobs:
key: "/etc/zrepl/backups.key" key: "/etc/zrepl/backups.key"
client_cns: client_cns:
- "prod" - "prod"
recv:
placeholder:
encryption: inherit # use 'off' if sender uses send.encrypted
root_fs: "storage/zrepl/sink" root_fs: "storage/zrepl/sink"

View File

@ -9,8 +9,8 @@ jobs:
key: /etc/zrepl/prod.key key: /etc/zrepl/prod.key
server_cn: "backups" server_cn: "backups"
filesystems: { filesystems: {
"zroot/var/db": true, "zroot<": true,
"zroot/usr/home<": true, "zroot/var/tmp<": false,
"zroot/usr/home/paranoid": false "zroot/usr/home/paranoid": false
} }
snapshotting: snapshotting:

View File

@ -9,13 +9,13 @@ This config example shows how we can backup our ZFS-based server to another mach
* Production server ``prod`` with filesystems to back up: * Production server ``prod`` with filesystems to back up:
* ``zroot/var/db`` * The entire pool ``zroot``
* ``zroot/usr/home`` and all its child filesystems * except ``zroot/var/tmp`` and all child datasets of it
* **except** ``zroot/usr/home/paranoid`` belonging to a user doing backups themselves * and except ``zroot/usr/home/paranoid`` which belongs to a user doing backups themselves.
* Backup server ``backups`` with * Backup server ``backups`` with a dataset sub-tree for use by zrepl:
* Filesystem ``storage/zrepl/sink/prod`` + children dedicated to backups of ``prod`` * In our example, that will be ``storage/zrepl/sink/prod``.
Our backup solution should fulfill the following requirements: Our backup solution should fulfill the following requirements: