# Choose block access or DAX before deploying persistent-memory storage

> Which persistent-memory access model matches the application and filesystem requirements?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:14:26+00:00
- Modified: 2026-09-08T18:26:31+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

Which persistent-memory access model matches the application and filesystem requirements?

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/deploy-persistent-memory).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[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.

## Primary reference

- Name: Understand and deploy persistent memory
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/deploy-persistent-memory
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose block access or DAX before deploying persistent-memory storage,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-165-choose-block-access-or-dax-before-deploying-persistent-memory-storage/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.