{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/", "slug": "dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses", "url": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/" }, "title": "Set Storage QoS goals in the units the policy actually uses", "summary": "How should a team define and verify a Storage QoS policy for virtual machines?", "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:44+00:00", "modified_at": "2026-09-08T18:17:14+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 251, "potentially_affected": "Use this review for a storage arrangement that meets the source's topology and version requirements.", "dse_recommendation": "Write the intended minimum and maximum goals before creating a policy.", "primary_source": { "name": "Storage Quality of Service", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-qos/storage-qos-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": "

Source facts

\n

Microsoft describes Storage QoS as centralized monitoring and management for virtual-machine storage using Hyper-V and Scale-Out File Server. Policies express minimum and maximum performance goals in normalized IOPS. At the default 8 KB normalization size, smaller operations count as one and larger operations count as multiple normalized I/Os. The normalization size is configurable across the storage cluster, so the active value must be identified when interpreting policy goals. The documented architecture serves Hyper-V storage over SMB3 and places the central monitoring policy manager on the file-server cluster. Microsoft documentation.

\n

Applicability

\n

Use this review for a storage arrangement that meets the source’s topology and version requirements. Identify the virtual disks and workloads the policy should govern, together with the owners who can interpret application performance.

\n

DSE recommendation

\n

Write the intended minimum and maximum goals before creating a policy. Record the reason for each goal and the workloads that share the storage. Ask application owners to define acceptable behavior under contention, and keep that expectation separate from the policy numbers. Pilot the policy on identified virtual disks and preserve their previous assignments for the approved recovery procedure.

\n

Verification

\n

Inspect the resulting policy assignments and compare storage observations with the intended normalized-IOPS goals. Exercise the agreed workload and contention scenario while recording application-level results. Investigate a policy mismatch separately from an application bottleneck. Keep the configuration, observations, and workload conditions together before deciding whether another workload should receive the same policy.

\n

Official references

\n

Microsoft Learn: Storage Quality of Service. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft describes Storage QoS as centralized monitoring and management for virtual-machine storage using Hyper-V and Scale-Out File Server. Policies express minimum and maximum performance goals in normalized IOPS. At the default 8 KB normalization size, smaller operations count as one and larger operations count as multiple normalized I/Os. The normalization size is configurable across the storage cluster, so the active value must be identified when interpreting policy goals. The documented architecture serves Hyper-V storage over SMB3 and places the central monitoring policy manager on the file-server cluster. Microsoft documentation.\nApplicability\nUse this review for a storage arrangement that meets the source’s topology and version requirements. Identify the virtual disks and workloads the policy should govern, together with the owners who can interpret application performance.\nDSE recommendation\nWrite the intended minimum and maximum goals before creating a policy. Record the reason for each goal and the workloads that share the storage. Ask application owners to define acceptable behavior under contention, and keep that expectation separate from the policy numbers. Pilot the policy on identified virtual disks and preserve their previous assignments for the approved recovery procedure.\nVerification\nInspect the resulting policy assignments and compare storage observations with the intended normalized-IOPS goals. Exercise the agreed workload and contention scenario while recording application-level results. Investigate a policy mismatch separately from an application bottleneck. Keep the configuration, observations, and workload conditions together before deciding whether another workload should receive the same policy.\nOfficial references\nMicrosoft Learn: Storage Quality of Service. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft describes Storage QoS as centralized monitoring and management for virtual-machine storage using Hyper-V and Scale-Out File Server. Policies express minimum and maximum performance goals in normalized IOPS. At the default 8 KB normalization size, smaller operations count as one and larger operations count as multiple normalized I/Os. The normalization size is configurable across the storage cluster, so the active value must be identified when interpreting policy goals. The documented architecture serves Hyper-V storage over SMB3 and places the central monitoring policy manager on the file-server cluster. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-qos/storage-qos-overview).\n\n## Applicability\n\nUse this review for a storage arrangement that meets the source’s topology and version requirements. Identify the virtual disks and workloads the policy should govern, together with the owners who can interpret application performance.\n\n## DSE recommendation\n\nWrite the intended minimum and maximum goals before creating a policy. Record the reason for each goal and the workloads that share the storage. Ask application owners to define acceptable behavior under contention, and keep that expectation separate from the policy numbers. Pilot the policy on identified virtual disks and preserve their previous assignments for the approved recovery procedure.\n\n## Verification\n\nInspect the resulting policy assignments and compare storage observations with the intended normalized-IOPS goals. Exercise the agreed workload and contention scenario while recording application-level results. Investigate a policy mismatch separately from an application bottleneck. Keep the configuration, observations, and workload conditions together before deciding whether another workload should receive the same policy.\n\n## Official references\n\n[Microsoft Learn: Storage Quality of Service](https://learn.microsoft.com/en-us/windows-server/storage/storage-qos/storage-qos-overview). 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-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/", "url": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Set Storage QoS goals in the units the policy actually uses", "item": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/", "url": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/", "headline": "Set Storage QoS goals in the units the policy actually uses", "description": "How should a team define and verify a Storage QoS policy for virtual machines?", "abstract": "How should a team define and verify a Storage QoS policy for virtual machines?", "articleBody": "Source facts\nMicrosoft describes Storage QoS as centralized monitoring and management for virtual-machine storage using Hyper-V and Scale-Out File Server. Policies express minimum and maximum performance goals in normalized IOPS. At the default 8 KB normalization size, smaller operations count as one and larger operations count as multiple normalized I/Os. The normalization size is configurable across the storage cluster, so the active value must be identified when interpreting policy goals. The documented architecture serves Hyper-V storage over SMB3 and places the central monitoring policy manager on the file-server cluster. Microsoft documentation.\nApplicability\nUse this review for a storage arrangement that meets the source’s topology and version requirements. Identify the virtual disks and workloads the policy should govern, together with the owners who can interpret application performance.\nDSE recommendation\nWrite the intended minimum and maximum goals before creating a policy. Record the reason for each goal and the workloads that share the storage. Ask application owners to define acceptable behavior under contention, and keep that expectation separate from the policy numbers. Pilot the policy on identified virtual disks and preserve their previous assignments for the approved recovery procedure.\nVerification\nInspect the resulting policy assignments and compare storage observations with the intended normalized-IOPS goals. Exercise the agreed workload and contention scenario while recording application-level results. Investigate a policy mismatch separately from an application bottleneck. Keep the configuration, observations, and workload conditions together before deciding whether another workload should receive the same policy.\nOfficial references\nMicrosoft Learn: Storage Quality of Service. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:44+00:00", "dateModified": "2026-09-08T18:17:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/" }, "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-027-set-storage-qos-goals-in-the-units-the-policy-actually-uses/#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": "Set Storage QoS goals in the units the policy actually uses" }, "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": 251, "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": "Storage Quality of Service", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-qos/storage-qos-overview" } } ] } }