ZFS, Actually Storage you can finally reason about.

Send and Receive

concept
depth 2/4 − deeper + surface

Send and receive are how a snapshot—a frozen moment of a dataset— travels to another machine. send turns the moment into a flowing copy; receive, on the other end, rebuilds it perfectly: every file, every setting, the snapshot itself. And after the first full trip, ZFS ships only what changed between one moment and the next.

The mental slot to avoid: this is not a file-syncing tool with extra steps. Sync tools (like rsync) hunt for differences—walking every folder, comparing files, approximating sameness against a moving target. ZFS doesn't hunt, because it already knows exactly what changed between two frozen moments. The copy isn't approximately the same; it is the same.

The shape of use:

  • Full: zfs send tank/ds@snap | ssh backup zfs recv vault/ds—a stream through a pipe, composable with ssh (this is where your SSH keys earn their keep).
  • Incremental is the daily workhorse: zfs send -i @yesterday @today ships only the blocks born between the two snapshots. Cost scales with churn, not dataset size—a 10TB dataset that changed 2GB sends 2GB.
  • Interrupted transfers resume (-t with a receive token)—relevant the first time a multi-TB initial send meets a flaky link.
  • Nobody types this on schedule; syncoid wraps the whole dance. But run it by hand once—the pipe makes the architecture legible.