From d86aa049ec22687b221e17abfc45bf30dd7d17a7 Mon Sep 17 00:00:00 2001 From: DatuX Date: Thu, 28 Apr 2022 17:44:16 +0200 Subject: [PATCH] Updated Common snapshots and holds (markdown) --- Common-snapshots-and-holds.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/Common-snapshots-and-holds.md b/Common-snapshots-and-holds.md index a95aed3..94e2a43 100644 --- a/Common-snapshots-and-holds.md +++ b/Common-snapshots-and-holds.md @@ -6,6 +6,15 @@ If you're new to ZFS these terms can be quite confusing. Whats going on? ## Common snapshots -ZFS can do incremental transfers via snapshots. It can only do this from a snapshot that's common on both the target and source. +ZFS can do incremental transfers via snapshots. It does this very efficiently by sending over the differences between two snapshots. + +There are a few rules for ZFS however: + +* The same starting snapshot has to exist on both target and source. So its a common snapshot. +* There cant be any newer snapshots on the target. (Normally should not happen, otherwise use --destroy-incompatible) +* Encryption has to be compatible (See [[Encryption]]) + +If there is no snapshot in common, the only way to continue is to destroy all the whole dataset (and all its snapshots) on the target and start from a full backup. + +## Holds to the rescue -If there is no snapshot in common, the only way to continue is to destroy all the whole dataset (and all its snapshots) on the target and start from a full backup. \ No newline at end of file