<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CSV on This Is My Demo</title><link>https://thisismydemo.cloud/tags/csv/</link><description>Recent content in CSV on This Is My Demo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Apr 2026 17:46:25 +0000</lastBuildDate><atom:link href="https://thisismydemo.cloud/tags/csv/index.xml" rel="self" type="application/rss+xml"/><item><title>Storage Architecture Deep Dive</title><link>https://thisismydemo.cloud/post/storage-architecture-deep-dive/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><guid>https://thisismydemo.cloud/post/storage-architecture-deep-dive/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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&amp;rsquo;s what this post is about.&lt;/p&gt;</description></item></channel></rss>