Two-Node Hyper-V Failover Cluster Part 7 of 15: Setup iSCSI Target & Create Shared Storage
Networks done in Part 6; now we build the SAN. Install iSCSI Target Server on the iSCSI VM, bind it to the Storage NIC ONLY, and carve two LUNs —…
Networks done in Part 6; now we build the SAN. Install iSCSI Target Server on the iSCSI VM, bind it to the Storage NIC ONLY, and carve two LUNs —…
VMs are built. Now the network plumbing the cluster needs: three vSwitches (External, Storage, Heartbeat), attached to the right VMs with the right IPs, all ping-tested. Skip the ping matrix…
The iSCSI VM has its OS disk (40 GB) but nothing to share yet. This part adds a 500 GB Fixed VHDX as the storage pool, attaches it to the…
Architecture is in your head from Part 1. Now we build VMs. The iSCSI VM is first because the cluster nodes need shared storage to be cluster-able — and that…
Welcome to part 1 of a 15-part series on building a Two-Node Hyper-V Failover Cluster. This is a planning post — no terminals, no wizards, no screenshots. The architecture goes…
Two-node FCI works. Tested it. But the design from Part 1 reserved a third node IP — this part builds it. The work splits into two posts: Part 9 (this…
SAN built in Part 3; now we connect the nodes to it. The iSCSI initiator on each node binds to its Storage NIC, discovers the target portal, logs in, and…
Networks done in Part 2; now we build the SAN. The iSCSI-Target VM gets the iSCSI Target Server role, the iSCSI service gets bound to the storage NIC ONLY, and…
Part 1 covered architecture; this part is the network plumbing. Three subnets, three named adapters per node, every link ping-tested before any cluster bit gets installed. Skip a ping test,…
Welcome to part 1 of a 13-part deep dive into SQL Server Always On Failover Cluster Instance (FCI). Before any wizard screens, before any PowerShell, you need the architecture in…