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

Updated Home (markdown)

DatuX
2023-06-01 14:06:32 +02:00
parent 0cbeff0b19
commit d5b471b815
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
Home.md

@ -216,7 +216,7 @@ It also possible to use a 3rd server that pulls backups from the source and push
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 3rd server and use both `--ssh-source` and `--ssh-target` to specify the other source and target servers.
### Local Usage ## Local Usage
It is also possible to run zfs-autobackup locally, where you could backup snapshots to a different pool on the same server. This is done by simply omitting the `--ssh-source` and `--ssh-target` parameters. It is also possible to run zfs-autobackup locally, where you could backup snapshots to a different pool on the same server. This is done by simply omitting the `--ssh-source` and `--ssh-target` parameters.
@ -228,7 +228,7 @@ Combining this with a remote push or pull backup, you could then set the zfs gro
> zfs-autobackup -v --ssh-target root@backupserver remote data/backup/pve01 > zfs-autobackup -v --ssh-target root@backupserver remote data/backup/pve01
### Automatic backups ## Automatic backups
Now every time you run the command, zfs-autobackup will create a new snapshot and replicate your data. Now every time you run the command, zfs-autobackup will create a new snapshot and replicate your data.
@ -238,11 +238,11 @@ Once you've got the correct settings for your situation, you can just store the
Or just create a script and run it manually when you need it. Or just create a script and run it manually when you need it.
### Monitoring ## Monitoring
Don't forget to monitor the results of your backups, look at [Monitoring](Monitoring) for more info. Don't forget to monitor the results of your backups, look at [Monitoring](Monitoring) for more info.
### Splitting up snapshot and backup job ## Splitting up snapshot and backup job
You might want to make snapshots during the week, and only transfer data during the weekends. You might want to make snapshots during the week, and only transfer data during the weekends.
@ -268,7 +268,7 @@ Only use this if you don't want to make any backup at all, or if a target isn't
If you have offline backups, checkout [[Common-snapshots-and-holds]] If you have offline backups, checkout [[Common-snapshots-and-holds]]
### Specifying ssh port or options ## Specifying ssh port or options
The correct way to do this is by creating ~/.ssh/config: The correct way to do this is by creating ~/.ssh/config:
@ -283,11 +283,11 @@ This way you can just specify "smartos04" as host.
Look in ```man ssh_config``` for many more options. Look in ```man ssh_config``` for many more options.
### Multiple backups of the same data ## Multiple backups of the same data
You can use multiple zfs-autobackup jobs to transfer data to multiple targets. Just make sure that you use different backup names. This way the jobs should not interfere with each other: Each job only removes its own snapshots. You can use multiple zfs-autobackup jobs to transfer data to multiple targets. Just make sure that you use different backup names. This way the jobs should not interfere with each other: Each job only removes its own snapshots.
#### Using the same backup name ### Using the same backup name
You CAN use the same backup name to transfer data to multiple targets. However in that case it's up to you to make sure that a common snapshot of one backup job isn't deleted by the other job. You CAN use the same backup name to transfer data to multiple targets. However in that case it's up to you to make sure that a common snapshot of one backup job isn't deleted by the other job.