{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/", "slug": "dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage", "url": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/" }, "title": "Choose block access or DAX before deploying persistent-memory storage", "summary": "Which persistent-memory access model matches the application and filesystem requirements?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "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:14:26+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 195, "potentially_affected": "Administrators evaluating persistent-memory storage on supported Windows Server platforms.", "dse_recommendation": "Have the application and storage owners choose the access model explicitly.", "primary_source": { "name": "Understand and deploy persistent memory", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/deploy-persistent-memory", "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

Persistent memory retains its contents across power cycles and can be used as storage. Microsoft distinguishes block access through the normal filesystem and storage stacks from direct access, or DAX. Block access supports NTFS and ReFS; DAX is limited to NTFS. The guidance warns that incorrect DAX use can lose data and recommends a block translation table to reduce the risk of torn writes. Microsoft documentation.

\n

Applicability

\n

Identify the hardware, server release, application access model, filesystem, and supported deployment requirements. Review the application’s documented persistent-memory behavior before selecting DAX because of a latency goal.

\n

DSE recommendation

\n

Have the application and storage owners choose the access model explicitly. Record the required filesystem, protective configuration, and recovery method. Keep the access-model decision separate from whether a memory module is healthy or whether a persistent-memory region has been detected.

\n

Verification

\n

Deploy a representative supported test configuration and confirm that the application uses the intended access path. Validate controlled data writes and the approved recovery exercise, preserving configuration and outcome evidence. Investigate any unsupported access assumption before allowing important data onto the proposed design.

\n

Official references

\n

Microsoft Learn: Understand and deploy persistent memory. Source reviewed September 8, 2026.

", "content_text": "Source facts\nPersistent memory retains its contents across power cycles and can be used as storage. Microsoft distinguishes block access through the normal filesystem and storage stacks from direct access, or DAX. Block access supports NTFS and ReFS; DAX is limited to NTFS. The guidance warns that incorrect DAX use can lose data and recommends a block translation table to reduce the risk of torn writes. Microsoft documentation.\nApplicability\nIdentify the hardware, server release, application access model, filesystem, and supported deployment requirements. Review the application’s documented persistent-memory behavior before selecting DAX because of a latency goal.\nDSE recommendation\nHave the application and storage owners choose the access model explicitly. Record the required filesystem, protective configuration, and recovery method. Keep the access-model decision separate from whether a memory module is healthy or whether a persistent-memory region has been detected.\nVerification\nDeploy a representative supported test configuration and confirm that the application uses the intended access path. Validate controlled data writes and the approved recovery exercise, preserving configuration and outcome evidence. Investigate any unsupported access assumption before allowing important data onto the proposed design.\nOfficial references\nMicrosoft Learn: Understand and deploy persistent memory. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nPersistent memory retains its contents across power cycles and can be used as storage. Microsoft distinguishes block access through the normal filesystem and storage stacks from direct access, or DAX. Block access supports NTFS and ReFS; DAX is limited to NTFS. The guidance warns that incorrect DAX use can lose data and recommends a block translation table to reduce the risk of torn writes. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/deploy-persistent-memory).\n\n## Applicability\n\nIdentify the hardware, server release, application access model, filesystem, and supported deployment requirements. Review the application’s documented persistent-memory behavior before selecting DAX because of a latency goal.\n\n## DSE recommendation\n\nHave the application and storage owners choose the access model explicitly. Record the required filesystem, protective configuration, and recovery method. Keep the access-model decision separate from whether a memory module is healthy or whether a persistent-memory region has been detected.\n\n## Verification\n\nDeploy a representative supported test configuration and confirm that the application uses the intended access path. Validate controlled data writes and the approved recovery exercise, preserving configuration and outcome evidence. Investigate any unsupported access assumption before allowing important data onto the proposed design.\n\n## Official references\n\n[Microsoft Learn: Understand and deploy persistent memory](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/deploy-persistent-memory). 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-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/", "url": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose block access or DAX before deploying persistent-memory storage", "item": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/", "url": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/", "headline": "Choose block access or DAX before deploying persistent-memory storage", "description": "Which persistent-memory access model matches the application and filesystem requirements?", "abstract": "Which persistent-memory access model matches the application and filesystem requirements?", "articleBody": "Source facts\nPersistent memory retains its contents across power cycles and can be used as storage. Microsoft distinguishes block access through the normal filesystem and storage stacks from direct access, or DAX. Block access supports NTFS and ReFS; DAX is limited to NTFS. The guidance warns that incorrect DAX use can lose data and recommends a block translation table to reduce the risk of torn writes. Microsoft documentation.\nApplicability\nIdentify the hardware, server release, application access model, filesystem, and supported deployment requirements. Review the application’s documented persistent-memory behavior before selecting DAX because of a latency goal.\nDSE recommendation\nHave the application and storage owners choose the access model explicitly. Record the required filesystem, protective configuration, and recovery method. Keep the access-model decision separate from whether a memory module is healthy or whether a persistent-memory region has been detected.\nVerification\nDeploy a representative supported test configuration and confirm that the application uses the intended access path. Validate controlled data writes and the approved recovery exercise, preserving configuration and outcome evidence. Investigate any unsupported access assumption before allowing important data onto the proposed design.\nOfficial references\nMicrosoft Learn: Understand and deploy persistent memory. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:26+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/" }, "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-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Choose block access or DAX before deploying persistent-memory storage" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 195, "timeRequired": "PT1M", "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": "Understand and deploy persistent memory", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/deploy-persistent-memory" } } ] } }