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

Updated Home (markdown)

DatuX
2023-02-26 12:07:27 +01:00
parent f31ec68aa5
commit d6494b6ec6
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Home.md

@ -38,6 +38,8 @@ In this example, a machine called `backup` is going to create and pull backup sn
As zfs-autobackup will perform numerous remote commands via ssh, we strongly recommend setting up passwordless login via ssh. This means generating an ssh key on target machine (`backup`) and copying the public ssh key to the source machine (`pve01`).
NOTE: Most examples use root-access on both the source and target. If you want to use a normal user its a bit more complex: Your user needs read/write access to /dev/zfs and you need to setup zfs permissions as well.
#### Generate an SSH key on `backup`
Create an SSH key on the backup machine that runs zfs-autobackup. You only need to do this once.
@ -197,9 +199,9 @@ Note that this is called a "pull" backup. The backup (target) machine pulls the
It is also possible to let a source machine push its backup to the target machine. There are security implications to both approaches, as follows:
With a pull backup, the target machine will have root access to the source machine.
With a pull backup, the target machine will have ssh access to the source machine.
With a push backup, the source machine will have root access to the target machine.
With a push backup, the source machine will have ssh access to the target machine.
If you wish to do a push backup, then you would setup the SSH keys the other way around and use the `--ssh-target` parameter on the source machine.