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

Updated Home (markdown)

Dan MacDonald
2023-10-15 12:22:07 +01:00
parent e82799c410
commit 32f8bff001
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Home.md

@ -217,9 +217,9 @@ Note that you can always change the ssh source and target parameters at a later
#### Pull+push (zero trust)
It also possible to use a 3rd server that pulls backups from the source and pushes the data to the target server via 1 stream. This way the source and target server wont have to be able to reach each other. If one server gets hacked, they cant access the other server.
It also possible to use a third server that pulls backups from the source and pushes the data to the target server via one stream. This way the source and target server won't have to be able to reach each other. If one server gets hacked, they can't access the other server.
To do this, you only have to install zfs-autobackup on a 3rd server and use both `--ssh-source` and `--ssh-target` to specify the other source and target servers.
To do this, you only have to install zfs-autobackup on a third server and use both `--ssh-source` and `--ssh-target` to specify the other source and target servers.
## Local Usage
@ -239,9 +239,7 @@ Now every time you run the command, zfs-autobackup will create a new snapshot an
Older snapshots will eventually be deleted, depending on the `--keep-source` and `--keep-target` settings. The defaults are shown above under the 'Settings summary'. Look at [Thinner](Thinner) for more info.
Once you've got the correct settings for your situation, you can just store the command in a cronjob.
Or just create a script and run it manually when you need it.
Once you've got the correct settings for your situation, you can just store the command in a cronjob or just create a script and run it manually when you need it.
## Monitoring