Updated Home (markdown)

DatuX
2023-06-19 10:11:31 +02:00
parent 8769a93097
commit 2277bc46f3

@ -298,7 +298,7 @@ However: To prevent confusion, and to be more flexible, I would advise to always
## Tips
* Use ```--debug``` if something goes wrong and you want to see the commands that are executed. This will also stop at the first error.
* You can split up the snapshotting and sending tasks by creating two cronjobs. Create a separate snapshotter-cronjob by just omitting target-path.
* Use these only one time if needed: ```--force``` ```--destroy-incompatible```. Dont add them to your script. Try to solve the underlying cause if you keep needing them.
* Set the ```readonly``` property of the target filesystem to ```on```. This prevents changes on the target side. (Due to the nature of ZFS itself, if any changes are made to a dataset on the target machine, then the next backup to that target machine will probably fail. Such a failure can probably be resolved by perfroming a target-side zfs rollback of the affected dataset.) Note that ```readonly``` prevents changes to the CONTENTS of the dataset directly. Its still possible to receive new datasets and manipulate properties etc.
* Use ```--clear-refreservation``` to save space on your backup machine.
* Use ```--clear-mountpoint``` to prevent the target machine from mounting the backupped filesystem in the wrong place during a reboot.