{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/", "item": { "id": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/", "slug": "retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy", "url": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy.md", "json": "https://update.dsesecurity.com/api/v1/posts/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/" }, "title": "Retain and resume interrupted OpenZFS receives with an explicit policy", "summary": "Give retained partial receives a restart decision, owner, and separate completion check.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-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:50+00:00", "modified_at": "2026-10-15T13:36:15+00:00", "reviewed_on": "2026-10-15", "reading_minutes": 2, "word_count": 249, "potentially_affected": "This applies to OpenZFS 2.3 resumable receive. It addresses interrupted-transfer handling and does not mean an incomplete receive is already an accepted, usable recovery snapshot.", "dse_recommendation": "DSE recommends deciding whether unattended replication should retain partial state and defining who reviews an interrupted transfer.", "primary_source": { "name": "OpenZFS 2.3 — zfs receive", "url": "https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-receive.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": "

Give retained partial receives a restart decision, owner, and separate completion check.

\n

Source facts

\n

OpenZFS 2.3 receive can preserve partially received state when its resumable option is selected. Interruptions can include a broken stream, checksum error, process termination, or unclean shutdown. The receiving dataset exposes a receive_resume_token that can be supplied to send to continue the transfer. This requires the extensible_dataset pool feature. A separate abort operation deletes saved partial state. Resumable receive therefore provides a controlled recovery path, but retained partial state still needs ownership.

\n

Source: OpenZFS 2.3 — zfs receive.

\n

Applicability

\n

This applies to OpenZFS 2.3 resumable receive. It addresses interrupted-transfer handling and does not mean an incomplete receive is already an accepted, usable recovery snapshot.

\n

DSE recommendation

\n

DSE recommends deciding whether unattended replication should retain partial state and defining who reviews an interrupted transfer. Record the source snapshot, destination dataset, token location, and restart or abort decision without exposing unrelated credentials. Before deleting partial state, confirm whether resuming the existing transfer is still intended. Keep incomplete receives visible in monitoring so an old interruption is not mistaken for a current recovery point. Use a separate completion and application-recovery check after transfer resumes.

\n

Verification

\n

Interrupt a disposable transfer, inspect the saved state and token, and resume it using the documented mechanism. Compare the completed destination with the intended source. Rehearse abort on a separate partial transfer and confirm monitoring reports the difference between retained partial state and an accepted completed snapshot.

\n

Official reference

\n

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

", "content_text": "Give retained partial receives a restart decision, owner, and separate completion check.\nSource facts\nOpenZFS 2.3 receive can preserve partially received state when its resumable option is selected. Interruptions can include a broken stream, checksum error, process termination, or unclean shutdown. The receiving dataset exposes a receive_resume_token that can be supplied to send to continue the transfer. This requires the extensible_dataset pool feature. A separate abort operation deletes saved partial state. Resumable receive therefore provides a controlled recovery path, but retained partial state still needs ownership.\nSource: OpenZFS 2.3 — zfs receive.\nApplicability\nThis applies to OpenZFS 2.3 resumable receive. It addresses interrupted-transfer handling and does not mean an incomplete receive is already an accepted, usable recovery snapshot.\nDSE recommendation\nDSE recommends deciding whether unattended replication should retain partial state and defining who reviews an interrupted transfer. Record the source snapshot, destination dataset, token location, and restart or abort decision without exposing unrelated credentials. Before deleting partial state, confirm whether resuming the existing transfer is still intended. Keep incomplete receives visible in monitoring so an old interruption is not mistaken for a current recovery point. Use a separate completion and application-recovery check after transfer resumes.\nVerification\nInterrupt a disposable transfer, inspect the saved state and token, and resume it using the documented mechanism. Compare the completed destination with the intended source. Rehearse abort on a separate partial transfer and confirm monitoring reports the difference between retained partial state and an accepted completed snapshot.\nOfficial reference\nOpenZFS 2.3 — zfs receive. Reviewed October 15, 2026.", "content_markdown": "Give retained partial receives a restart decision, owner, and separate completion check.\n\n## Source facts\n\nOpenZFS 2.3 receive can preserve partially received state when its resumable option is selected. Interruptions can include a broken stream, checksum error, process termination, or unclean shutdown. The receiving dataset exposes a receive_resume_token that can be supplied to send to continue the transfer. This requires the extensible_dataset pool feature. A separate abort operation deletes saved partial state. Resumable receive therefore provides a controlled recovery path, but retained partial state still needs ownership.\n\nSource: [OpenZFS 2.3 — zfs receive](https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-receive.8.html).\n\n## Applicability\n\nThis applies to OpenZFS 2.3 resumable receive. It addresses interrupted-transfer handling and does not mean an incomplete receive is already an accepted, usable recovery snapshot.\n\n## DSE recommendation\n\nDSE recommends deciding whether unattended replication should retain partial state and defining who reviews an interrupted transfer. Record the source snapshot, destination dataset, token location, and restart or abort decision without exposing unrelated credentials. Before deleting partial state, confirm whether resuming the existing transfer is still intended. Keep incomplete receives visible in monitoring so an old interruption is not mistaken for a current recovery point. Use a separate completion and application-recovery check after transfer resumes.\n\n## Verification\n\nInterrupt a disposable transfer, inspect the saved state and token, and resume it using the documented mechanism. Compare the completed destination with the intended source. Rehearse abort on a separate partial transfer and confirm monitoring reports the difference between retained partial state and an accepted completed snapshot.\n\n## Official reference\n\n[OpenZFS 2.3 — zfs receive](https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-receive.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/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/", "url": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Retain and resume interrupted OpenZFS receives with an explicit policy", "item": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/#article", "identifier": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/", "url": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/", "headline": "Retain and resume interrupted OpenZFS receives with an explicit policy", "description": "Give retained partial receives a restart decision, owner, and separate completion check.", "abstract": "Give retained partial receives a restart decision, owner, and separate completion check.", "articleBody": "Give retained partial receives a restart decision, owner, and separate completion check.\nSource facts\nOpenZFS 2.3 receive can preserve partially received state when its resumable option is selected. Interruptions can include a broken stream, checksum error, process termination, or unclean shutdown. The receiving dataset exposes a receive_resume_token that can be supplied to send to continue the transfer. This requires the extensible_dataset pool feature. A separate abort operation deletes saved partial state. Resumable receive therefore provides a controlled recovery path, but retained partial state still needs ownership.\nSource: OpenZFS 2.3 — zfs receive.\nApplicability\nThis applies to OpenZFS 2.3 resumable receive. It addresses interrupted-transfer handling and does not mean an incomplete receive is already an accepted, usable recovery snapshot.\nDSE recommendation\nDSE recommends deciding whether unattended replication should retain partial state and defining who reviews an interrupted transfer. Record the source snapshot, destination dataset, token location, and restart or abort decision without exposing unrelated credentials. Before deleting partial state, confirm whether resuming the existing transfer is still intended. Keep incomplete receives visible in monitoring so an old interruption is not mistaken for a current recovery point. Use a separate completion and application-recovery check after transfer resumes.\nVerification\nInterrupt a disposable transfer, inspect the saved state and token, and resume it using the documented mechanism. Compare the completed destination with the intended source. Rehearse abort on a separate partial transfer and confirm monitoring reports the difference between retained partial state and an accepted completed snapshot.\nOfficial reference\nOpenZFS 2.3 — zfs receive. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:32:50+00:00", "dateModified": "2026-10-15T13:36:15+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/" }, "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/retain-and-resume-interrupted-openzfs-receives-with-an-explicit-policy/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Retain and resume interrupted OpenZFS receives with an explicit policy" }, "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": 249, "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 receive", "url": "https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-receive.8.html" } } ] } }