Storage

Post 6 got your storage connected. This post explains how it actually works , and why the architecture decisions you make here determine whether your Hyper-V cluster performs like an enterprise platform or stumbles under load.

Storage is where the three-tier Hyper-V story gets strongest. Your existing SAN investment , the FlashArrays, the PowerStores, the NetApp filers , carries forward without additional storage licensing. No vSAN subscription. No S2D requiring identical disk configurations on every node. No platform fee just to connect storage you already own. The storage you already operate works with Hyper-V exactly as it worked with VMware: present LUNs, configure MPIO, format volumes, and build around proven operational patterns. The difference is what sits on top of it , and that’s what this post is about.

Not everything needs to be hyper-converged.

There’s a strong narrative in the infrastructure world that three-tier architecture, separate compute, network, and storage tiers, is outdated. That hyper-converged infrastructure (HCI) is the only path forward. That separating your storage from your compute is a legacy pattern.

That narrative is incomplete.

Three-tier architecture remains the right answer for many workloads and many organizations. If you have an existing SAN investment, if your workloads require deterministic storage performance, if you need storage-level replication for disaster recovery, or if your team has deep storage operations expertise, three-tier isn’t just viable, it’s often superior.