{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/", "slug": "dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts", "url": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/" }, "title": "Monitor persistent memory beyond ordinary disk charts", "summary": "Which observations should be collected when persistent-memory health is uncertain?", "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:14:09+00:00", "modified_at": "2026-09-08T18:26:32+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 216, "potentially_affected": "Administrators monitoring persistent-memory devices used with Windows storage.", "dse_recommendation": "Add persistent-memory-specific health queries to the storage runbook.", "primary_source": { "name": "Persistent memory health management for Storage Spaces Direct in Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/persistent-memory-health", "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

Microsoft says persistent memory does not produce Physical Disk performance counters, so it does not appear in the corresponding Windows Admin Center charts. It also does not produce Storport 505 data for proactive outlier detection. The UnsafeShutdownCount value totals shutdowns of underlying persistent-memory devices that may have caused data loss. Microsoft Learn.

\n

Applicability

\n

Confirm that the investigated device is persistent memory and identify its actual storage role. Review the documented operating-system limitations before interpreting missing chart data. Keep a missing metric, a warning state, and an unhealthy device as different observations.

\n

DSE recommendation

\n

Add persistent-memory-specific health queries to the storage runbook. Capture device identity, health, operational status, physical location, and unsafe-shutdown observations in a single record. Assign a hardware owner to interpret warnings alongside the vendor guidance. Avoid reinitializing an unfamiliar or unhealthy device merely to make a dashboard look normal. Preserve the initial state for investigation.

\n

Verification

\n

Compare the query output with the physical inventory and the relevant operational events. Verify that monitoring can detect the documented warning or unhealthy state in an approved test or reviewed incident sample. Record unavailable metrics as monitoring limitations and confirm that the escalation path reaches the correct hardware owner.

\n

Official references

\n

Microsoft Learn: Persistent memory health management for Storage Spaces Direct in Windows Server. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft says persistent memory does not produce Physical Disk performance counters, so it does not appear in the corresponding Windows Admin Center charts. It also does not produce Storport 505 data for proactive outlier detection. The UnsafeShutdownCount value totals shutdowns of underlying persistent-memory devices that may have caused data loss. Microsoft Learn.\nApplicability\nConfirm that the investigated device is persistent memory and identify its actual storage role. Review the documented operating-system limitations before interpreting missing chart data. Keep a missing metric, a warning state, and an unhealthy device as different observations.\nDSE recommendation\nAdd persistent-memory-specific health queries to the storage runbook. Capture device identity, health, operational status, physical location, and unsafe-shutdown observations in a single record. Assign a hardware owner to interpret warnings alongside the vendor guidance. Avoid reinitializing an unfamiliar or unhealthy device merely to make a dashboard look normal. Preserve the initial state for investigation.\nVerification\nCompare the query output with the physical inventory and the relevant operational events. Verify that monitoring can detect the documented warning or unhealthy state in an approved test or reviewed incident sample. Record unavailable metrics as monitoring limitations and confirm that the escalation path reaches the correct hardware owner.\nOfficial references\nMicrosoft Learn: Persistent memory health management for Storage Spaces Direct in Windows Server. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft says persistent memory does not produce Physical Disk performance counters, so it does not appear in the corresponding Windows Admin Center charts. It also does not produce Storport 505 data for proactive outlier detection. The UnsafeShutdownCount value totals shutdowns of underlying persistent-memory devices that may have caused data loss. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/persistent-memory-health).\n\n## Applicability\n\nConfirm that the investigated device is persistent memory and identify its actual storage role. Review the documented operating-system limitations before interpreting missing chart data. Keep a missing metric, a warning state, and an unhealthy device as different observations.\n\n## DSE recommendation\n\nAdd persistent-memory-specific health queries to the storage runbook. Capture device identity, health, operational status, physical location, and unsafe-shutdown observations in a single record. Assign a hardware owner to interpret warnings alongside the vendor guidance. Avoid reinitializing an unfamiliar or unhealthy device merely to make a dashboard look normal. Preserve the initial state for investigation.\n\n## Verification\n\nCompare the query output with the physical inventory and the relevant operational events. Verify that monitoring can detect the documented warning or unhealthy state in an approved test or reviewed incident sample. Record unavailable metrics as monitoring limitations and confirm that the escalation path reaches the correct hardware owner.\n\n## Official references\n\n[Microsoft Learn: Persistent memory health management for Storage Spaces Direct in Windows Server](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/persistent-memory-health). 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-182-monitor-persistent-memory-beyond-ordinary-disk-charts/", "url": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Monitor persistent memory beyond ordinary disk charts", "item": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/", "url": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/", "headline": "Monitor persistent memory beyond ordinary disk charts", "description": "Which observations should be collected when persistent-memory health is uncertain?", "abstract": "Which observations should be collected when persistent-memory health is uncertain?", "articleBody": "Source facts\nMicrosoft says persistent memory does not produce Physical Disk performance counters, so it does not appear in the corresponding Windows Admin Center charts. It also does not produce Storport 505 data for proactive outlier detection. The UnsafeShutdownCount value totals shutdowns of underlying persistent-memory devices that may have caused data loss. Microsoft Learn.\nApplicability\nConfirm that the investigated device is persistent memory and identify its actual storage role. Review the documented operating-system limitations before interpreting missing chart data. Keep a missing metric, a warning state, and an unhealthy device as different observations.\nDSE recommendation\nAdd persistent-memory-specific health queries to the storage runbook. Capture device identity, health, operational status, physical location, and unsafe-shutdown observations in a single record. Assign a hardware owner to interpret warnings alongside the vendor guidance. Avoid reinitializing an unfamiliar or unhealthy device merely to make a dashboard look normal. Preserve the initial state for investigation.\nVerification\nCompare the query output with the physical inventory and the relevant operational events. Verify that monitoring can detect the documented warning or unhealthy state in an approved test or reviewed incident sample. Record unavailable metrics as monitoring limitations and confirm that the escalation path reaches the correct hardware owner.\nOfficial references\nMicrosoft Learn: Persistent memory health management for Storage Spaces Direct in Windows Server. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:09+00:00", "dateModified": "2026-09-08T18:26:32+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-182-monitor-persistent-memory-beyond-ordinary-disk-charts/" }, "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-182-monitor-persistent-memory-beyond-ordinary-disk-charts/#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": "Monitor persistent memory beyond ordinary disk charts" }, "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": 216, "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": "Persistent memory health management for Storage Spaces Direct in Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/persistent-memory-health" } } ] } }