{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/", "slug": "dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together", "url": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/" }, "title": "Choose whether cluster compute and storage should scale together", "summary": "Should a planned failover cluster add compute and storage in the same growth unit?", "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:15:39+00:00", "modified_at": "2026-09-08T18:20:22+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 208, "potentially_affected": "Architects comparing Windows Server failover-cluster storage layouts.", "dse_recommendation": "Compare two concrete expansion scenarios: adding capacity without additional application compute, and adding compute without additional storage.", "primary_source": { "name": "Failover Clustering Storage Architectures in Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/storage-architectures", "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 distinguishes storage separated from compute from hyperconverged Storage Spaces Direct. With separate SAN or NAS storage, cluster nodes reach storage across a network and compute and storage can grow independently. In the hyperconverged model, Storage Spaces Direct combines drives from the nodes into a shared pool and exposes Cluster Shared Volumes. Adding nodes increases compute resources and storage together. Microsoft documentation.

\n

Applicability

\n

Start with workload growth, storage growth, existing equipment, and ownership requirements. Check the applicable hardware and operating-system requirements for each proposed design before treating a diagram as an approved configuration.

\n

DSE recommendation

\n

Compare two concrete expansion scenarios: adding capacity without additional application compute, and adding compute without additional storage. Record which servers, fabric components, and owners participate in each option. Ask application and storage teams to agree on the expansion unit and the maintenance responsibilities it creates.

\n

Verification

\n

Review a representative workload placement and maintenance event against the selected architecture. Confirm where its data resides, which nodes can reach it, and how expansion would be performed under the approved design. Keep capacity assumptions and measured application requirements explicit so later growth does not rely on an undocumented architectural shortcut.

\n

Official references

\n

Microsoft Learn: Failover Clustering Storage Architectures in Windows Server. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft distinguishes storage separated from compute from hyperconverged Storage Spaces Direct. With separate SAN or NAS storage, cluster nodes reach storage across a network and compute and storage can grow independently. In the hyperconverged model, Storage Spaces Direct combines drives from the nodes into a shared pool and exposes Cluster Shared Volumes. Adding nodes increases compute resources and storage together. Microsoft documentation.\nApplicability\nStart with workload growth, storage growth, existing equipment, and ownership requirements. Check the applicable hardware and operating-system requirements for each proposed design before treating a diagram as an approved configuration.\nDSE recommendation\nCompare two concrete expansion scenarios: adding capacity without additional application compute, and adding compute without additional storage. Record which servers, fabric components, and owners participate in each option. Ask application and storage teams to agree on the expansion unit and the maintenance responsibilities it creates.\nVerification\nReview a representative workload placement and maintenance event against the selected architecture. Confirm where its data resides, which nodes can reach it, and how expansion would be performed under the approved design. Keep capacity assumptions and measured application requirements explicit so later growth does not rely on an undocumented architectural shortcut.\nOfficial references\nMicrosoft Learn: Failover Clustering Storage Architectures in Windows Server. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft distinguishes storage separated from compute from hyperconverged Storage Spaces Direct. With separate SAN or NAS storage, cluster nodes reach storage across a network and compute and storage can grow independently. In the hyperconverged model, Storage Spaces Direct combines drives from the nodes into a shared pool and exposes Cluster Shared Volumes. Adding nodes increases compute resources and storage together. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/failover-clustering/storage-architectures).\n\n## Applicability\n\nStart with workload growth, storage growth, existing equipment, and ownership requirements. Check the applicable hardware and operating-system requirements for each proposed design before treating a diagram as an approved configuration.\n\n## DSE recommendation\n\nCompare two concrete expansion scenarios: adding capacity without additional application compute, and adding compute without additional storage. Record which servers, fabric components, and owners participate in each option. Ask application and storage teams to agree on the expansion unit and the maintenance responsibilities it creates.\n\n## Verification\n\nReview a representative workload placement and maintenance event against the selected architecture. Confirm where its data resides, which nodes can reach it, and how expansion would be performed under the approved design. Keep capacity assumptions and measured application requirements explicit so later growth does not rely on an undocumented architectural shortcut.\n\n## Official references\n\n[Microsoft Learn: Failover Clustering Storage Architectures in Windows Server](https://learn.microsoft.com/en-us/windows-server/failover-clustering/storage-architectures). 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-092-choose-whether-cluster-compute-and-storage-should-scale-together/", "url": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose whether cluster compute and storage should scale together", "item": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/", "url": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/", "headline": "Choose whether cluster compute and storage should scale together", "description": "Should a planned failover cluster add compute and storage in the same growth unit?", "abstract": "Should a planned failover cluster add compute and storage in the same growth unit?", "articleBody": "Source facts\nMicrosoft distinguishes storage separated from compute from hyperconverged Storage Spaces Direct. With separate SAN or NAS storage, cluster nodes reach storage across a network and compute and storage can grow independently. In the hyperconverged model, Storage Spaces Direct combines drives from the nodes into a shared pool and exposes Cluster Shared Volumes. Adding nodes increases compute resources and storage together. Microsoft documentation.\nApplicability\nStart with workload growth, storage growth, existing equipment, and ownership requirements. Check the applicable hardware and operating-system requirements for each proposed design before treating a diagram as an approved configuration.\nDSE recommendation\nCompare two concrete expansion scenarios: adding capacity without additional application compute, and adding compute without additional storage. Record which servers, fabric components, and owners participate in each option. Ask application and storage teams to agree on the expansion unit and the maintenance responsibilities it creates.\nVerification\nReview a representative workload placement and maintenance event against the selected architecture. Confirm where its data resides, which nodes can reach it, and how expansion would be performed under the approved design. Keep capacity assumptions and measured application requirements explicit so later growth does not rely on an undocumented architectural shortcut.\nOfficial references\nMicrosoft Learn: Failover Clustering Storage Architectures in Windows Server. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:15:39+00:00", "dateModified": "2026-09-08T18:20:22+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/" }, "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-092-choose-whether-cluster-compute-and-storage-should-scale-together/#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 whether cluster compute and storage should scale together" }, "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": 208, "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": "Failover Clustering Storage Architectures in Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/storage-architectures" } } ] } }