{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/", "slug": "dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion", "url": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/" }, "title": "Separate Elastic SAN capacity expansion from performance expansion", "summary": "Additional capacity increases storage space, while base capacity determines the SAN's shared IOPS and throughput pool.", "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": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "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-10T00:25:56+00:00", "modified_at": "2026-09-10T02:01:56+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 237, "potentially_affected": "Azure Elastic SAN capacity planning for VM-connected volumes.", "dse_recommendation": "Identify whether the shortfall is space, SAN performance, volume limits or VM limits before expanding capacity.", "primary_source": { "name": "Learn about Azure Elastic SAN and VM performance | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-performance", "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

Elastic SAN distinguishes base capacity from additional capacity. Increasing additional capacity does not increase IOPS or throughput; the SAN’s performance pool grows with base capacity and is shared across its volumes.

\n

Individual volumes have their own performance limits, and combined volume demand cannot exceed the SAN’s total IOPS and throughput. VM type and size introduce their own limits, so an application’s request can be throttled at more than one boundary. Microsoft Learn.

\n

Applicability

\n

Record the actual SAN base and additional capacities, relevant volumes and connected VM types. Distinguish a need for more stored data from a need for more serviceable I/O.

\n

DSE recommendation

\n

DSE recommends tracing the observed bottleneck before selecting an expansion. Compare concurrent workload demand with the shared SAN budget and each participating volume and VM limit. Do not justify additional-capacity expansion as an IOPS fix without evidence that the selected change addresses the limiting boundary. Review competing workloads together rather than treating each volume’s maximum as independently reserved performance.

\n

Verification

\n

Use an approved representative workload to compare latency, throughput and IOPS before and after the chosen adjustment. Include the concurrent demand expected from other volumes. Retain the capacity split and relevant limits with the measurements. If the expected improvement does not occur, reassess the limiting layer instead of repeatedly adding storage space to a performance problem.

\n

Official references

\n

Microsoft Learn: Learn about Azure Elastic SAN and VM performance. Source retrieved September 9, 2026.

", "content_text": "Source facts\nElastic SAN distinguishes base capacity from additional capacity. Increasing additional capacity does not increase IOPS or throughput; the SAN’s performance pool grows with base capacity and is shared across its volumes.\nIndividual volumes have their own performance limits, and combined volume demand cannot exceed the SAN’s total IOPS and throughput. VM type and size introduce their own limits, so an application’s request can be throttled at more than one boundary. Microsoft Learn.\nApplicability\nRecord the actual SAN base and additional capacities, relevant volumes and connected VM types. Distinguish a need for more stored data from a need for more serviceable I/O.\nDSE recommendation\nDSE recommends tracing the observed bottleneck before selecting an expansion. Compare concurrent workload demand with the shared SAN budget and each participating volume and VM limit. Do not justify additional-capacity expansion as an IOPS fix without evidence that the selected change addresses the limiting boundary. Review competing workloads together rather than treating each volume’s maximum as independently reserved performance.\nVerification\nUse an approved representative workload to compare latency, throughput and IOPS before and after the chosen adjustment. Include the concurrent demand expected from other volumes. Retain the capacity split and relevant limits with the measurements. If the expected improvement does not occur, reassess the limiting layer instead of repeatedly adding storage space to a performance problem.\nOfficial references\nMicrosoft Learn: Learn about Azure Elastic SAN and VM performance. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nElastic SAN distinguishes base capacity from additional capacity. Increasing additional capacity does not increase IOPS or throughput; the SAN’s performance pool grows with base capacity and is shared across its volumes.\n\nIndividual volumes have their own performance limits, and combined volume demand cannot exceed the SAN’s total IOPS and throughput. VM type and size introduce their own limits, so an application’s request can be throttled at more than one boundary. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-performance).\n\n## Applicability\n\nRecord the actual SAN base and additional capacities, relevant volumes and connected VM types. Distinguish a need for more stored data from a need for more serviceable I/O.\n\n## DSE recommendation\n\nDSE recommends tracing the observed bottleneck before selecting an expansion. Compare concurrent workload demand with the shared SAN budget and each participating volume and VM limit. Do not justify additional-capacity expansion as an IOPS fix without evidence that the selected change addresses the limiting boundary. Review competing workloads together rather than treating each volume’s maximum as independently reserved performance.\n\n## Verification\n\nUse an approved representative workload to compare latency, throughput and IOPS before and after the chosen adjustment. Include the concurrent demand expected from other volumes. Retain the capacity split and relevant limits with the measurements. If the expected improvement does not occur, reassess the limiting layer instead of repeatedly adding storage space to a performance problem.\n\n## Official references\n\n[Microsoft Learn: Learn about Azure Elastic SAN and VM performance](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-performance). Source retrieved September 9, 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-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/", "url": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Separate Elastic SAN capacity expansion from performance expansion", "item": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/", "url": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/", "headline": "Separate Elastic SAN capacity expansion from performance expansion", "description": "Additional capacity increases storage space, while base capacity determines the SAN's shared IOPS and throughput pool.", "abstract": "Additional capacity increases storage space, while base capacity determines the SAN's shared IOPS and throughput pool.", "articleBody": "Source facts\nElastic SAN distinguishes base capacity from additional capacity. Increasing additional capacity does not increase IOPS or throughput; the SAN’s performance pool grows with base capacity and is shared across its volumes.\nIndividual volumes have their own performance limits, and combined volume demand cannot exceed the SAN’s total IOPS and throughput. VM type and size introduce their own limits, so an application’s request can be throttled at more than one boundary. Microsoft Learn.\nApplicability\nRecord the actual SAN base and additional capacities, relevant volumes and connected VM types. Distinguish a need for more stored data from a need for more serviceable I/O.\nDSE recommendation\nDSE recommends tracing the observed bottleneck before selecting an expansion. Compare concurrent workload demand with the shared SAN budget and each participating volume and VM limit. Do not justify additional-capacity expansion as an IOPS fix without evidence that the selected change addresses the limiting boundary. Review competing workloads together rather than treating each volume’s maximum as independently reserved performance.\nVerification\nUse an approved representative workload to compare latency, throughput and IOPS before and after the chosen adjustment. Include the concurrent demand expected from other volumes. Retain the capacity split and relevant limits with the measurements. If the expected improvement does not occur, reassess the limiting layer instead of repeatedly adding storage space to a performance problem.\nOfficial references\nMicrosoft Learn: Learn about Azure Elastic SAN and VM performance. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:25:56+00:00", "dateModified": "2026-09-10T02:01:56+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/" }, "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-20260909-360-separate-elastic-san-capacity-expansion-from-performance-expansion/#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": "Separate Elastic SAN capacity expansion from performance expansion" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 237, "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": "Learn about Azure Elastic SAN and VM performance | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-performance" } } ] } }