patrick/zfs_autobackup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated Common snapshots and holds (markdown)

DatuX
2022-04-28 17:44:16 +02:00
parent 209fac13b4
commit d86aa049ec
1 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
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 ## 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. 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