Two-Node Hyper-V Failover Cluster Part 10 of 15: Create the Cluster (CNO + IP)
Validation passed in Part 9. Now we create the actual cluster object — gives the cluster a name, an IP, registers it in AD, and pulls in the iSCSI disks.…
Validation passed in Part 9. Now we create the actual cluster object — gives the cluster a name, an IP, registers it in AD, and pulls in the iSCSI disks.…
SAN built in Part 7. Now we connect the cluster nodes. Same pattern as the SQL FCI series — bind iSCSI Initiator to the Storage NIC, log in with CHAP,…
Storage and networks are wired. Time to install the cluster bits and prove the design is supported. Two moves: install Failover Clustering feature on both nodes, then run Validate Configuration.…
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…
VMs created in Parts 2 and 3. Now the basic post-install tasks for all three. This is foundation sysadmin work — rename, domain-join, static IP, patch, reboot. If any of…
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…