From daab64edc12778cf7aefc43dcab679caa20efcb4 Mon Sep 17 00:00:00 2001 From: DatuX Date: Thu, 28 Apr 2022 16:35:39 +0200 Subject: [PATCH] Updated Home (markdown) --- Home.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Home.md b/Home.md index 1b0036d..7a034e8 100644 --- a/Home.md +++ b/Home.md @@ -266,6 +266,7 @@ Look in ```man ssh_config``` for many more options. * 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. +* zfs-autobackup uses holds by default, so you might get "dataset busy" if you try to destroy a snapshot. (check zfs holds --help) ## Restore example