ZFS Overhead Reduction

Reducing storage overhead in Encrypted ZFS Failback

Today’s ZFS experiment delivered a rather satisfying result: raw encrypted failback into a copy-on-write dataset works without duplicating the baseline data. Using OpenZFS 2.4.4, AES-256-GCM encryption and a common snapshot GUID, we successfully received a raw incremental stream (zfs send -w -i) into a new dataset using zfs receive -o origin.

The resulting clone inherited the original snapshot’s blocks while allocating storage primarily for the incremental changes and associated metadata. Subsequent zfs promote reversed the clone dependency without duplicating the underlying data, and file-level verification confirmed that the recovered dataset contained both the original data and the writes made during simulated failover.

The implications are substantial: a 14 TB encrypted ZFS failback operation may no longer require maintaining another permanent 14 TB staging dataset. The mechanism is proven in a small-scale PoC; production-grade lifecycle handling and recovery orchestration remain to be validated. Copy-on-write doing some seriously useful work.