{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/", "slug": "dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change", "url": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/" }, "title": "Understand how ReFS keeps block-cloned files independent when they change", "summary": "What happens when an application writes into a region shared by ReFS block clones?", "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-09-08T18:16:01+00:00", "modified_at": "2026-09-08T18:20:22+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 226, "potentially_affected": "Use this review when evaluating an application that uses ReFS block cloning.", "dse_recommendation": "Ask the application owner to distinguish a logical copy operation from an independently stored physical copy in the design record.", "primary_source": { "name": "Block cloning on ReFS", "url": "https://learn.microsoft.com/en-us/windows-server/storage/refs/block-cloning", "published_on": null, "authority": "Microsoft Learn" }, "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": "

Source facts

\n

Block cloning lets an application request a copy of a byte range within one file or between files. ReFS implements the copy through metadata and reference counts, allowing file regions to share the same physical data. When a shared region is written, ReFS allocates a new region for that write. Microsoft describes this allocate-on-write behavior as preserving isolation between the files. Microsoft documentation.

\n

Applicability

\n

Use this review when evaluating an application that uses ReFS block cloning. Confirm the supported filesystem and application requirements before relying on the mechanism. Identify which files and operations the application is expected to clone.

\n

DSE recommendation

\n

Ask the application owner to distinguish a logical copy operation from an independently stored physical copy in the design record. Choose a test that clones representative content and then changes one of the resulting files. Record the expected contents of each file after the change. Keep recovery and backup decisions separately documented rather than deriving them from copy performance.

\n

Verification

\n

Run the approved clone-and-modify test and compare both files with their expected contents. Record the application operation and filesystem context, together with relevant capacity or I/O observations. Investigate any mismatch before enabling the workflow for important data. Repeat the acceptance review if the application’s copy method or supported storage configuration changes.

\n

Official references

\n

Microsoft Learn: Block cloning on ReFS. Source reviewed September 8, 2026.

", "content_text": "Source facts\nBlock cloning lets an application request a copy of a byte range within one file or between files. ReFS implements the copy through metadata and reference counts, allowing file regions to share the same physical data. When a shared region is written, ReFS allocates a new region for that write. Microsoft describes this allocate-on-write behavior as preserving isolation between the files. Microsoft documentation.\nApplicability\nUse this review when evaluating an application that uses ReFS block cloning. Confirm the supported filesystem and application requirements before relying on the mechanism. Identify which files and operations the application is expected to clone.\nDSE recommendation\nAsk the application owner to distinguish a logical copy operation from an independently stored physical copy in the design record. Choose a test that clones representative content and then changes one of the resulting files. Record the expected contents of each file after the change. Keep recovery and backup decisions separately documented rather than deriving them from copy performance.\nVerification\nRun the approved clone-and-modify test and compare both files with their expected contents. Record the application operation and filesystem context, together with relevant capacity or I/O observations. Investigate any mismatch before enabling the workflow for important data. Repeat the acceptance review if the application’s copy method or supported storage configuration changes.\nOfficial references\nMicrosoft Learn: Block cloning on ReFS. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nBlock cloning lets an application request a copy of a byte range within one file or between files. ReFS implements the copy through metadata and reference counts, allowing file regions to share the same physical data. When a shared region is written, ReFS allocates a new region for that write. Microsoft describes this allocate-on-write behavior as preserving isolation between the files. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/refs/block-cloning).\n\n## Applicability\n\nUse this review when evaluating an application that uses ReFS block cloning. Confirm the supported filesystem and application requirements before relying on the mechanism. Identify which files and operations the application is expected to clone.\n\n## DSE recommendation\n\nAsk the application owner to distinguish a logical copy operation from an independently stored physical copy in the design record. Choose a test that clones representative content and then changes one of the resulting files. Record the expected contents of each file after the change. Keep recovery and backup decisions separately documented rather than deriving them from copy performance.\n\n## Verification\n\nRun the approved clone-and-modify test and compare both files with their expected contents. Record the application operation and filesystem context, together with relevant capacity or I/O observations. Investigate any mismatch before enabling the workflow for important data. Repeat the acceptance review if the application’s copy method or supported storage configuration changes.\n\n## Official references\n\n[Microsoft Learn: Block cloning on ReFS](https://learn.microsoft.com/en-us/windows-server/storage/refs/block-cloning). Source reviewed September 8, 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/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/", "url": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Understand how ReFS keeps block-cloned files independent when they change", "item": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/", "url": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/", "headline": "Understand how ReFS keeps block-cloned files independent when they change", "description": "What happens when an application writes into a region shared by ReFS block clones?", "abstract": "What happens when an application writes into a region shared by ReFS block clones?", "articleBody": "Source facts\nBlock cloning lets an application request a copy of a byte range within one file or between files. ReFS implements the copy through metadata and reference counts, allowing file regions to share the same physical data. When a shared region is written, ReFS allocates a new region for that write. Microsoft describes this allocate-on-write behavior as preserving isolation between the files. Microsoft documentation.\nApplicability\nUse this review when evaluating an application that uses ReFS block cloning. Confirm the supported filesystem and application requirements before relying on the mechanism. Identify which files and operations the application is expected to clone.\nDSE recommendation\nAsk the application owner to distinguish a logical copy operation from an independently stored physical copy in the design record. Choose a test that clones representative content and then changes one of the resulting files. Record the expected contents of each file after the change. Keep recovery and backup decisions separately documented rather than deriving them from copy performance.\nVerification\nRun the approved clone-and-modify test and compare both files with their expected contents. Record the application operation and filesystem context, together with relevant capacity or I/O observations. Investigate any mismatch before enabling the workflow for important data. Repeat the acceptance review if the application’s copy method or supported storage configuration changes.\nOfficial references\nMicrosoft Learn: Block cloning on ReFS. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:01+00:00", "dateModified": "2026-09-08T18:20:22+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/" }, "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/dse-20260908-070-understand-how-refs-keeps-block-cloned-files-independent-when-they-change/#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": "Understand how ReFS keeps block-cloned files independent when they change" }, "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": 226, "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": "Block cloning on ReFS", "url": "https://learn.microsoft.com/en-us/windows-server/storage/refs/block-cloning" } } ] } }