{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/", "item": { "id": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/", "slug": "use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming", "url": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming.md", "json": "https://update.dsesecurity.com/api/v1/posts/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/" }, "title": "Use OpenZFS bookmarks as incremental-send markers with clear naming", "summary": "Map bookmarks to the incremental replication relationship they are intended to support.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-15T13:32:51+00:00", "modified_at": "2026-10-15T13:36:15+00:00", "reviewed_on": "2026-10-15", "reading_minutes": 2, "word_count": 250, "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.", "primary_source": { "name": "OpenZFS 2.3 — zfs bookmark", "url": "https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-bookmark.8.html", "published_on": null, "authority": "openzfs.github.io" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

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

\n

Source facts

\n

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.

\n

Source: OpenZFS 2.3 — zfs bookmark.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official reference

\n

OpenZFS 2.3 — zfs bookmark. Reviewed October 15, 2026.

", "content_text": "Map bookmarks to the incremental replication relationship they are intended to support.\nSource facts\nOpenZFS 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.\nSource: OpenZFS 2.3 — zfs bookmark.\nApplicability\nThis 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.\nDSE recommendation\nDSE 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.\nVerification\nIn 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.\nOfficial reference\nOpenZFS 2.3 — zfs bookmark. Reviewed October 15, 2026.", "content_markdown": "Map bookmarks to the incremental replication relationship they are intended to support.\n\n## Source facts\n\nOpenZFS 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.\n\nSource: [OpenZFS 2.3 — zfs bookmark](https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-bookmark.8.html).\n\n## Applicability\n\nThis 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nIn 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.\n\n## Official reference\n\n[OpenZFS 2.3 — zfs bookmark](https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-bookmark.8.html). Reviewed October 15, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/", "url": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Use OpenZFS bookmarks as incremental-send markers with clear naming", "item": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/#article", "identifier": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/", "url": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/", "headline": "Use OpenZFS bookmarks as incremental-send markers with clear naming", "description": "Map bookmarks to the incremental replication relationship they are intended to support.", "abstract": "Map bookmarks to the incremental replication relationship they are intended to support.", "articleBody": "Map bookmarks to the incremental replication relationship they are intended to support.\nSource facts\nOpenZFS 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.\nSource: OpenZFS 2.3 — zfs bookmark.\nApplicability\nThis 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.\nDSE recommendation\nDSE 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.\nVerification\nIn 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.\nOfficial reference\nOpenZFS 2.3 — zfs bookmark. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:32:51+00:00", "dateModified": "2026-10-15T13:36:15+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/use-openzfs-bookmarks-as-incremental-send-markers-with-clear-naming/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Use OpenZFS bookmarks as incremental-send markers with clear naming" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 250, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "OpenZFS 2.3 — zfs bookmark", "url": "https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-bookmark.8.html" } } ] } }