Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: document permissions for syncoid #432

Merged
merged 1 commit into from
Oct 29, 2024
Merged

docs: document permissions for syncoid #432

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 15 additions & 7 deletions docs/sanoid.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,13 +157,21 @@ chmod go-rwx -R /home/$OPERATOR/.ssh
```

Adding needed permissions to pull zfs syncs
```bash
# choose the right dataset according to your needs
zfs allow $OPERATOR hold,send zfs-hdd
zfs allow $OPERATOR hold,send zfs-nvme
zfs allow $OPERATOR hold,send rpool

```
1. if you use `--no-sync-snap`, you only use `hold,send`
```bash
# choose the right dataset according to your needs
zfs allow $OPERATOR hold,send zfs-hdd
zfs allow $OPERATOR hold,send zfs-nvme
zfs allow $OPERATOR hold,send rpool
```

2. otherwise you'll need , you need `destroy,hold,mount,send,snapshot`
```bash
# choose the right dataset according to your needs
zfs allow $OPERATOR destroy,hold,mount,send,snapshot rpool
```

#### test connection on BACKUP_SERVER

On BACKUP_SERVER, test ssh connection:
Expand Down Expand Up @@ -191,4 +199,4 @@ Don't forget to create a sane retention policy (with `autosnap=no`) in sanoid on
**Note:** because of the 6h timeout, if you have big datasets, you may want to do the first synchronization before enabling the service.

**Important:** try to have a good hierarchy of datasets, and separate what's from the server and what's from other servers.
Normally we put other servers backups in a off-backups dataset. It's important not to mix it with backups dataset which is for the server itself.
Normally we put other servers backups in a off-backups dataset. It's important not to mix it with backups dataset which is for the server itself.
Loading