{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/windows-refs-supported-resiliency-design/", "item": { "id": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/", "slug": "windows-refs-supported-resiliency-design", "url": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design.md", "json": "https://update.dsesecurity.com/api/v1/posts/windows-refs-supported-resiliency-design/" }, "title": "Use ReFS resiliency only inside a supported storage and application design", "summary": "ReFS supplies metadata integrity and documented resiliency features, while repair capability, data integrity streams, storage layout, hardware certification, and application support determine the actual outcome.", "format": { "slug": "explainer", "name": "Explainer" }, "priority": { "slug": "advisory", "name": "Advisory" }, "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-08-25T21:35:01+00:00", "modified_at": "2026-08-25T21:43:55+00:00", "reviewed_on": "2026-08-25", "reading_minutes": 3, "word_count": 471, "potentially_affected": "Windows Server storage designs using or evaluating ReFS for Storage Spaces, Storage Spaces Direct, basic disks, or backup targets.", "dse_recommendation": "Select ReFS only for a Microsoft- and application-supported configuration, document which data is checksummed and repairable, monitor integrity events, and maintain independent tested backups.", "primary_source": { "name": "Resilient File System (ReFS) overview", "url": "https://learn.microsoft.com/en-us/windows-server/storage/refs/refs-overview", "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": "

Bottom line: ReFS is designed for integrity, availability, scale, and specific storage workloads. Its repair behavior depends on the storage configuration, alternate data copies, integrity streams, and application. Microsoft limits supported scenarios and calls for certified hardware and application compatibility. ReFS is not a universal corruption-proof file system or a backup.

\n

Source fact: what Microsoft documents

\n

Microsoft’s ReFS overview describes integrity streams, online repair, metadata checksums, block cloning, sparse valid data length, and scale features. In supported Storage Spaces and Storage Spaces Direct designs, ReFS can use alternate copies to repair detected metadata or data corruption when the necessary integrity and redundancy are available.

\n

Microsoft lists supported configurations and scenarios for Storage Spaces Direct, Storage Spaces, basic disks, and backup targets. The page states that supported configurations must use Windows Server Catalog-certified hardware and meet application requirements. Capabilities differ by Windows Server version and storage design. Microsoft also calls out SAN and feature considerations where NTFS may be required, and advises contacting application and storage vendors for relevant support details.

\n

What the source does not establish

\n

ReFS does not guarantee that all file data is checksummed, that every detected corruption can be repaired, or that a basic disk has an alternate copy. It does not replace backup, protect against deletion or ransomware, validate application consistency, or make unsupported hardware supportable. A clean file-system status does not prove stored application data is semantically correct.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n
    \n
  1. Confirm Microsoft, hardware, storage, and application support for the exact OS, firmware, topology, and workload.
    2. \n
  2. Document the protection model for metadata and file data, including integrity-stream state, redundancy, failure domains, and repair limits.
    3. \n
  3. Test representative application I/O, backup, restore, expansion, drive failure, repair, and performance before production acceptance.
    4. \n
  4. Monitor ReFS, storage, controller, and application events; route integrity or repair warnings to an owned queue.
    5. \n
  5. Maintain independent backups and prove restoration to another system. Do not count online repair as the recovery copy.
    6. \n
\n

Verification and evidence

\n\n

Official references

\n", "content_text": "Bottom line: ReFS is designed for integrity, availability, scale, and specific storage workloads. Its repair behavior depends on the storage configuration, alternate data copies, integrity streams, and application. Microsoft limits supported scenarios and calls for certified hardware and application compatibility. ReFS is not a universal corruption-proof file system or a backup.\nSource fact: what Microsoft documents\nMicrosoft’s ReFS overview describes integrity streams, online repair, metadata checksums, block cloning, sparse valid data length, and scale features. In supported Storage Spaces and Storage Spaces Direct designs, ReFS can use alternate copies to repair detected metadata or data corruption when the necessary integrity and redundancy are available.\nMicrosoft lists supported configurations and scenarios for Storage Spaces Direct, Storage Spaces, basic disks, and backup targets. The page states that supported configurations must use Windows Server Catalog-certified hardware and meet application requirements. Capabilities differ by Windows Server version and storage design. Microsoft also calls out SAN and feature considerations where NTFS may be required, and advises contacting application and storage vendors for relevant support details.\nWhat the source does not establish\nReFS does not guarantee that all file data is checksummed, that every detected corruption can be repaired, or that a basic disk has an alternate copy. It does not replace backup, protect against deletion or ransomware, validate application consistency, or make unsupported hardware supportable. A clean file-system status does not prove stored application data is semantically correct.\nApplicability questions\n\nWhich Windows Server edition and version, physical disks, controller or HBA, enclosure, firmware, and storage topology are proposed?\nIs the workload Storage Spaces Direct, Storage Spaces, a basic disk, a backup target, Hyper-V, SQL Server, or another application?\nWhich data has integrity streams, and where does an alternate good copy come from?\nDoes the application and hardware vendor explicitly support ReFS for this exact use?\nHow are integrity warnings, scrub results, storage faults, capacity, and repair actions monitored?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\n\nConfirm Microsoft, hardware, storage, and application support for the exact OS, firmware, topology, and workload.\nDocument the protection model for metadata and file data, including integrity-stream state, redundancy, failure domains, and repair limits.\nTest representative application I/O, backup, restore, expansion, drive failure, repair, and performance before production acceptance.\nMonitor ReFS, storage, controller, and application events; route integrity or repair warnings to an owned queue.\nMaintain independent backups and prove restoration to another system. Do not count online repair as the recovery copy.\n\nVerification and evidence\n\nPreserve hardware certification, vendor support, OS/build, storage layout, ReFS settings, and acceptance approval.\nRecord integrity-stream state and documented health or scrub output for representative volumes.\nCapture controlled failure-and-repair test results without risking the only copy of data.\nDemonstrate a restore from independent backup and application-level validation afterward.\n\nOfficial references\n\nResilient File System (ReFS) overview — Microsoft", "content_markdown": "Bottom line: ReFS is designed for integrity, availability, scale, and specific storage workloads. Its repair behavior depends on the storage configuration, alternate data copies, integrity streams, and application. Microsoft limits supported scenarios and calls for certified hardware and application compatibility. ReFS is not a universal corruption-proof file system or a backup.\n\n## Source fact: what Microsoft documents\n\nMicrosoft’s [ReFS overview](https://learn.microsoft.com/en-us/windows-server/storage/refs/refs-overview) describes integrity streams, online repair, metadata checksums, block cloning, sparse valid data length, and scale features. In supported Storage Spaces and Storage Spaces Direct designs, ReFS can use alternate copies to repair detected metadata or data corruption when the necessary integrity and redundancy are available.\n\nMicrosoft lists supported configurations and scenarios for Storage Spaces Direct, Storage Spaces, basic disks, and backup targets. The page states that supported configurations must use Windows Server Catalog-certified hardware and meet application requirements. Capabilities differ by Windows Server version and storage design. Microsoft also calls out SAN and feature considerations where NTFS may be required, and advises contacting application and storage vendors for relevant support details.\n\n## What the source does not establish\n\nReFS does not guarantee that all file data is checksummed, that every detected corruption can be repaired, or that a basic disk has an alternate copy. It does not replace backup, protect against deletion or ransomware, validate application consistency, or make unsupported hardware supportable. A clean file-system status does not prove stored application data is semantically correct.\n\n## Applicability questions\n\n- Which Windows Server edition and version, physical disks, controller or HBA, enclosure, firmware, and storage topology are proposed?\n\n- Is the workload Storage Spaces Direct, Storage Spaces, a basic disk, a backup target, Hyper-V, SQL Server, or another application?\n\n- Which data has integrity streams, and where does an alternate good copy come from?\n\n- Does the application and hardware vendor explicitly support ReFS for this exact use?\n\n- How are integrity warnings, scrub results, storage faults, capacity, and repair actions monitored?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\n- Confirm Microsoft, hardware, storage, and application support for the exact OS, firmware, topology, and workload.\n\n- Document the protection model for metadata and file data, including integrity-stream state, redundancy, failure domains, and repair limits.\n\n- Test representative application I/O, backup, restore, expansion, drive failure, repair, and performance before production acceptance.\n\n- Monitor ReFS, storage, controller, and application events; route integrity or repair warnings to an owned queue.\n\n- Maintain independent backups and prove restoration to another system. Do not count online repair as the recovery copy.\n\n## Verification and evidence\n\n- Preserve hardware certification, vendor support, OS/build, storage layout, ReFS settings, and acceptance approval.\n\n- Record integrity-stream state and documented health or scrub output for representative volumes.\n\n- Capture controlled failure-and-repair test results without risking the only copy of data.\n\n- Demonstrate a restore from independent backup and application-level validation afterward.\n\n## Official references\n\n- [Resilient File System (ReFS) overview](https://learn.microsoft.com/en-us/windows-server/storage/refs/refs-overview) — Microsoft" }, "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/windows-refs-supported-resiliency-design/", "url": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-25" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Use ReFS resiliency only inside a supported storage and application design", "item": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/#article", "identifier": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/", "url": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/", "headline": "Use ReFS resiliency only inside a supported storage and application design", "description": "ReFS supplies metadata integrity and documented resiliency features, while repair capability, data integrity streams, storage layout, hardware…", "abstract": "ReFS supplies metadata integrity and documented resiliency features, while repair capability, data integrity streams, storage layout, hardware certification, and application support determine the actual outcome.", "articleBody": "Bottom line: ReFS is designed for integrity, availability, scale, and specific storage workloads. Its repair behavior depends on the storage configuration, alternate data copies, integrity streams, and application. Microsoft limits supported scenarios and calls for certified hardware and application compatibility. ReFS is not a universal corruption-proof file system or a backup.\nSource fact: what Microsoft documents\nMicrosoft’s ReFS overview describes integrity streams, online repair, metadata checksums, block cloning, sparse valid data length, and scale features. In supported Storage Spaces and Storage Spaces Direct designs, ReFS can use alternate copies to repair detected metadata or data corruption when the necessary integrity and redundancy are available.\nMicrosoft lists supported configurations and scenarios for Storage Spaces Direct, Storage Spaces, basic disks, and backup targets. The page states that supported configurations must use Windows Server Catalog-certified hardware and meet application requirements. Capabilities differ by Windows Server version and storage design. Microsoft also calls out SAN and feature considerations where NTFS may be required, and advises contacting application and storage vendors for relevant support details.\nWhat the source does not establish\nReFS does not guarantee that all file data is checksummed, that every detected corruption can be repaired, or that a basic disk has an alternate copy. It does not replace backup, protect against deletion or ransomware, validate application consistency, or make unsupported hardware supportable. A clean file-system status does not prove stored application data is semantically correct.\nApplicability questions\n\nWhich Windows Server edition and version, physical disks, controller or HBA, enclosure, firmware, and storage topology are proposed?\nIs the workload Storage Spaces Direct, Storage Spaces, a basic disk, a backup target, Hyper-V, SQL Server, or another application?\nWhich data has integrity streams, and where does an alternate good copy come from?\nDoes the application and hardware vendor explicitly support ReFS for this exact use?\nHow are integrity warnings, scrub results, storage faults, capacity, and repair actions monitored?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\n\nConfirm Microsoft, hardware, storage, and application support for the exact OS, firmware, topology, and workload.\nDocument the protection model for metadata and file data, including integrity-stream state, redundancy, failure domains, and repair limits.\nTest representative application I/O, backup, restore, expansion, drive failure, repair, and performance before production acceptance.\nMonitor ReFS, storage, controller, and application events; route integrity or repair warnings to an owned queue.\nMaintain independent backups and prove restoration to another system. Do not count online repair as the recovery copy.\n\nVerification and evidence\n\nPreserve hardware certification, vendor support, OS/build, storage layout, ReFS settings, and acceptance approval.\nRecord integrity-stream state and documented health or scrub output for representative volumes.\nCapture controlled failure-and-repair test results without risking the only copy of data.\nDemonstrate a restore from independent backup and application-level validation afterward.\n\nOfficial references\n\nResilient File System (ReFS) overview — Microsoft", "datePublished": "2026-08-25T21:35:01+00:00", "dateModified": "2026-08-25T21:43:55+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/windows-refs-supported-resiliency-design/" }, "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/windows-refs-supported-resiliency-design/#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 ReFS resiliency only inside a supported storage and application design" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Explainer", "Advisory priority" ], "genre": "Explainer", "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": 471, "timeRequired": "PT3M", "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": "Resilient File System (ReFS) overview", "url": "https://learn.microsoft.com/en-us/windows-server/storage/refs/refs-overview" } } ] } }