Updated Home (markdown)

Dan MacDonald
2023-10-15 12:27:37 +01:00
parent 32f8bff001
commit 7585b0bd48

@ -245,7 +245,7 @@ Once you've got the correct settings for your situation, you can just store the
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 jobs
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.
@ -259,7 +259,7 @@ And this on weekend days:
You can also create the snapshots in offline mode by using zfs-autobackup as a snapshot tool on the source side. This way the snapshots will always be created, even if the backup server is offline or unreachable. You can also create the snapshots in offline mode by using zfs-autobackup as a snapshot tool on the source side. This way the snapshots will always be created, even if the backup server is offline or unreachable.
## Use as snapshot tool ## Use as a snapshot tool
You can use zfs-autobackup as a standalone snapshot tool. You can use zfs-autobackup as a standalone snapshot tool.
@ -296,7 +296,7 @@ You CAN use the same backup name to transfer data to multiple targets. However i
One way to do this is to make adjust the --keep-source option or to make sure the backups run at a close enough interval. One way to do this is to make adjust the --keep-source option or to make sure the backups run at a close enough interval.
However: To prevent confusion, and to be more flexible, I would advise to always use different and clear to distinguish names. e.g.: autobackup:offsite and autobackup:local for example. To prevent confusion, and to be more flexible, I would advise you to always use easily distinguished names e.g.: autobackup:offsite and autobackup:local, for example.
## Tips ## Tips