Same workflow as Part 2 (the iSCSI VM), repeated twice. NODE-01 and NODE-02 are the cluster nodes — the actual hypervisor hosts that will run highly-available VMs in Part 13.…
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…
The grand finale. Twelve parts of building — this part is about tearing down gracefully when nodes need to be replaced or decommissioned. Plus advanced cluster moves: shuffling individual disks,…
3-node FCI is built. Now we use it. This part covers the real-world “go-live” flow: migrate a database from a legacy standalone SQL Server into AOFCI via backup/restore, then perform…
Node-03 is in the Windows cluster (Part 10) but has no SQL binaries. This part installs SQL Server in Add Node mode on Node-03 — functionally identical to Part 7…
Node-03 prepared in Part 9. Now we formally add it to the Windows Failover Cluster as a voting member. Short post — the Add Node wizard does most of the…
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…
Eight parts of work get tested in 30 seconds. We create some baseline data on the active node, kill the active node hard, watch the cluster move SQL to the…
SQL Server is installed on Node-01 only — that’s technically a single point of failure dressed up as a cluster. This part fixes that. We run the same setup.exe on…
The big moment. Five parts of plumbing — networks, SAN, initiators, cluster, validation — have led here. Now we install SQL Server itself, but in a special mode: Failover Cluster…
Plumbing is in. Storage is connected. Time to merge two standalone servers into a single Windows Failover Cluster — the brain that orchestrates failover for SQL Server (and any other…
