From 1330ccba42d8e099b2d3e56208b4f0d2eae3fe20 Mon Sep 17 00:00:00 2001 From: Dan MacDonald Date: Sun, 15 Oct 2023 12:30:02 +0100 Subject: [PATCH] Updated Home (markdown) --- Home.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Home.md b/Home.md index ee2e660..1066692 100644 --- a/Home.md +++ b/Home.md @@ -302,8 +302,8 @@ To prevent confusion, and to be more flexible, I would advise you to always use * Use ```--clear-mountpoint``` to prevent all kinds of problems. See [[Mounting]] * Use ```--debug``` if something goes wrong and you want to see the commands that are executed. This will also stop at the first error. -* Use these only one time if needed: `--force` `--destroy-incompatible` `--rollback`. 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 these only one time if needed: `--force` `--destroy-incompatible` `--rollback`. Don't 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. It's still possible to receive new datasets and manipulate properties etc. * Use ```--clear-refreservation``` to save space on your backup machine. * zfs-autobackup uses holds by default, so you might get "dataset busy" if you try to destroy a snapshot. (check zfs holds --help)