patrick/zfs_autobackup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

moved run-without-root to manual

Edwin Eefting
2023-10-15 20:10:13 +02:00
parent d1bf920edd
commit 92bd39bbeb
2 changed files with 17 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Home.md

@ -78,22 +78,6 @@ root@backup:~#
``` ```
This allows the backup machine to login to `pve01` as root without password. This allows the backup machine to login to `pve01` as root without password.
### Running without root
In order to run zfs-autobackup without root permissions, you'll need to set a few ZFS permissions. The permissions required differ for receiving and sending.
On the machine you want to sync the dataset from, you'll need the send, hold, mount, snapshot, and destroy permissions. You can apply them like so:
```console
root@source:~# zfs allow -u localuser mount,send,hold,snapshot,destroy rpool
```
On the receiving side, you will need the compression, mountpoint, create, mount, receive, rollback and destroy permissions:
```console
root@target:~# zfs allow -u remoteuser compression,mountpoint,create,mount,receive,rollback,destroy tank/backups/rpool
```
### Select filesystems to backup ### Select filesystems to backup
Next, we specify the filesystems we want to snapshot and replicate by assigning a unique group name to those filesystems. Next, we specify the filesystems we want to snapshot and replicate by assigning a unique group name to those filesystems.

17
Manual.md

@ -170,3 +170,20 @@ The handling of those is described [here](Thinner#destroying-missing-datasets) (
## Thinner ## Thinner
The thinner decides when a snapshot is obsolete. Look at [Thinner](Thinner) for more info. (`--keep-source` and `--keep-target`) The thinner decides when a snapshot is obsolete. Look at [Thinner](Thinner) for more info. (`--keep-source` and `--keep-target`)
## Running without root
In order to run zfs-autobackup without root permissions, you'll need to set a few ZFS permissions. The permissions required differ for receiving and sending.
On the machine you want to sync the dataset from, you'll need the send, hold, mount, snapshot, and destroy permissions. You can apply them like so:
```console
root@source:~# zfs allow -u localuser mount,send,hold,snapshot,destroy rpool
```
On the receiving side, you will need the compression, mountpoint, create, mount, receive, rollback and destroy permissions:
```console
root@target:~# zfs allow -u remoteuser compression,mountpoint,create,mount,receive,rollback,destroy tank/backups/rpool
```