Just a note to self after tonights exam preparation on how to create a SQL Failover Cluster.
Every database server that hosts critical system should be created as high-availability solutions. This can be done by creating “Failover Cluster” or “AlwaysOn Availability Groups”. This post only includes notes on important points for Failover cluster.
- Configure shared storage. Make sure servers are in the OU for SQL Servers. Apply firewall rules for ports TCP/135, TCP/3260, in addition to UDP/138 and any SAN target software. Bring SAN volumes online and create disk partitions. Add DNS record for cluster name.
- Configure Windows Server R2 failover cluster. Apply .NET Framework 3.5.1 on all nodes. Configure cluster servers (nodes). Set cluster name and IP.
- Run “Advanced Cluster Preparation” on each node. Each node in cluster need to perform this preparation task with node reboot. Installation includes db engine, replication, Mgmnt tools on default instans.
- Run “Advanced Cluster Completion” on node with shared storage. Verify SAN disks. Set server network name, resource group, cluster IP and subnet-mask, including online status verfication.
- Perform a cluster failover. This can be done by powershell command “Move-ClusterGroup <resourcegroup> <node>”