{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/", "slug": "dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity", "url": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/" }, "title": "Plan cluster volume count around metadata ownership and capacity", "summary": "How should Storage Spaces Direct volume count account for ownership distribution?", "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:47+00:00", "modified_at": "2026-09-08T18:23:27+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 198, "potentially_affected": "Administrators planning volumes in Storage Spaces Direct clusters.", "dse_recommendation": "Create a volume worksheet showing workload placement, planned capacity, and intended ownership distribution.", "primary_source": { "name": "Plan volumes on Azure Local and Windows Server clusters", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/plan-volumes", "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 relates the number of cluster volumes to pool capacity and the maximum supported volume size, with at least one volume per node. That layout allows volume ownership to be distributed among servers; one server coordinates metadata for each volume. The planning guidance treats filesystem, resiliency, and size as separate choices driven by workload performance and capacity needs. Microsoft documentation.

\n

Applicability

\n

Inventory the pool, node count, workload groups, expected growth, and supported volume limits. Review the specific resiliency and capacity calculation for the proposed design before assigning a target size to each volume.

\n

DSE recommendation

\n

Create a volume worksheet showing workload placement, planned capacity, and intended ownership distribution. Ask the application and storage owners to approve the boundaries between workloads. Include the expected expansion scenario so the initial layout does not depend on an undocumented spare-capacity assumption.

\n

Verification

\n

Compare the created volume inventory and ownership with the worksheet. Test representative access and an approved ownership move while observing the workload. Record actual capacity and distribution separately from forecasts, and revisit the plan when node count or workload growth changes materially.

\n

Official references

\n

Microsoft Learn: Plan volumes on Azure Local and Windows Server clusters. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft relates the number of cluster volumes to pool capacity and the maximum supported volume size, with at least one volume per node. That layout allows volume ownership to be distributed among servers; one server coordinates metadata for each volume. The planning guidance treats filesystem, resiliency, and size as separate choices driven by workload performance and capacity needs. Microsoft documentation.\nApplicability\nInventory the pool, node count, workload groups, expected growth, and supported volume limits. Review the specific resiliency and capacity calculation for the proposed design before assigning a target size to each volume.\nDSE recommendation\nCreate a volume worksheet showing workload placement, planned capacity, and intended ownership distribution. Ask the application and storage owners to approve the boundaries between workloads. Include the expected expansion scenario so the initial layout does not depend on an undocumented spare-capacity assumption.\nVerification\nCompare the created volume inventory and ownership with the worksheet. Test representative access and an approved ownership move while observing the workload. Record actual capacity and distribution separately from forecasts, and revisit the plan when node count or workload growth changes materially.\nOfficial references\nMicrosoft Learn: Plan volumes on Azure Local and Windows Server clusters. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft relates the number of cluster volumes to pool capacity and the maximum supported volume size, with at least one volume per node. That layout allows volume ownership to be distributed among servers; one server coordinates metadata for each volume. The planning guidance treats filesystem, resiliency, and size as separate choices driven by workload performance and capacity needs. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/plan-volumes).\n\n## Applicability\n\nInventory the pool, node count, workload groups, expected growth, and supported volume limits. Review the specific resiliency and capacity calculation for the proposed design before assigning a target size to each volume.\n\n## DSE recommendation\n\nCreate a volume worksheet showing workload placement, planned capacity, and intended ownership distribution. Ask the application and storage owners to approve the boundaries between workloads. Include the expected expansion scenario so the initial layout does not depend on an undocumented spare-capacity assumption.\n\n## Verification\n\nCompare the created volume inventory and ownership with the worksheet. Test representative access and an approved ownership move while observing the workload. Record actual capacity and distribution separately from forecasts, and revisit the plan when node count or workload growth changes materially.\n\n## Official references\n\n[Microsoft Learn: Plan volumes on Azure Local and Windows Server clusters](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/plan-volumes). 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-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/", "url": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Plan cluster volume count around metadata ownership and capacity", "item": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/", "url": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/", "headline": "Plan cluster volume count around metadata ownership and capacity", "description": "How should Storage Spaces Direct volume count account for ownership distribution?", "abstract": "How should Storage Spaces Direct volume count account for ownership distribution?", "articleBody": "Source facts\nMicrosoft relates the number of cluster volumes to pool capacity and the maximum supported volume size, with at least one volume per node. That layout allows volume ownership to be distributed among servers; one server coordinates metadata for each volume. The planning guidance treats filesystem, resiliency, and size as separate choices driven by workload performance and capacity needs. Microsoft documentation.\nApplicability\nInventory the pool, node count, workload groups, expected growth, and supported volume limits. Review the specific resiliency and capacity calculation for the proposed design before assigning a target size to each volume.\nDSE recommendation\nCreate a volume worksheet showing workload placement, planned capacity, and intended ownership distribution. Ask the application and storage owners to approve the boundaries between workloads. Include the expected expansion scenario so the initial layout does not depend on an undocumented spare-capacity assumption.\nVerification\nCompare the created volume inventory and ownership with the worksheet. Test representative access and an approved ownership move while observing the workload. Record actual capacity and distribution separately from forecasts, and revisit the plan when node count or workload growth changes materially.\nOfficial references\nMicrosoft Learn: Plan volumes on Azure Local and Windows Server clusters. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:47+00:00", "dateModified": "2026-09-08T18:23:27+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/" }, "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-144-plan-cluster-volume-count-around-metadata-ownership-and-capacity/#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": "Plan cluster volume count around metadata ownership and capacity" }, "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": 198, "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": "Plan volumes on Azure Local and Windows Server clusters", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/plan-volumes" } } ] } }