# Use OpenZFS bookmarks as incremental-send markers with clear naming

> Map bookmarks to the incremental replication relationship they are intended to support.

- Canonical URL: https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-15T13:32:51+00:00
- Modified: 2026-10-15T13:36:15+00:00
- Last reviewed by DSE: 2026-10-15
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Map bookmarks to the incremental replication relationship they are intended to support.

## Potentially affected

This applies to the OpenZFS 2.3 bookmark command and incremental-source selection. It does not establish a complete snapshot-retention policy or replace verifying destination recovery data.

## DSE recommendation

DSE recommends documenting bookmark names alongside the replication relationship they support.

## Article

Map bookmarks to the incremental replication relationship they are intended to support.

## Source facts

OpenZFS 2.3 bookmarks mark the point in time at which a snapshot was created and can be used as the incremental source for a send. The bookmark command can create a new bookmark from a snapshot or another bookmark, and the pool’s bookmarks feature must be enabled. Creating one from a redaction bookmark does not produce another redaction bookmark. A bookmark therefore has a defined replication role and should not be confused with arbitrary snapshot naming or redaction metadata.

Source: [OpenZFS 2.3 — zfs bookmark](https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-bookmark.8.html).

## Applicability

This applies to the OpenZFS 2.3 bookmark command and incremental-source selection. It does not establish a complete snapshot-retention policy or replace verifying destination recovery data.

## DSE recommendation

DSE recommends documenting bookmark names alongside the replication relationship they support. Record the source point and the destination chain that the operator expects to continue. Include feature compatibility in migration reviews, particularly when a pool will be handled by a different appliance or release. Keep redaction-specific decisions separate so a copied bookmark name is not taken as evidence that redaction metadata has been preserved. Require a reviewed chain check before removing or renaming an operational marker.

## Verification

In a disposable dataset, create a bookmark from a known snapshot and use it as the source of a subsequent incremental-send rehearsal. Confirm the intended receiver accepts that chain. Retain the mapping of bookmark, original point, and target snapshot in the test record.

## Official reference

[OpenZFS 2.3 — zfs bookmark](https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-bookmark.8.html). Reviewed October 15, 2026.

## Primary reference

- Name: OpenZFS 2.3 — zfs bookmark
- Authority: openzfs.github.io
- URL: https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-bookmark.8.html
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Use OpenZFS bookmarks as incremental-send markers with clear naming,” DSE Security, https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.