Windows Server Failover Clusters (WSFC)

Windows Server Failover Clusters (WSFC) on Windows Server 2022 involves configuring multiple servers to work together to increase availability for applications or services. Here’s a step-by-step guide:

Prerequisites

Servers: At least two servers running Windows Server 2022.
Network:
- Ensure servers are on the same domain.
- Use at least two network interfaces per server (one for cluster communication and one for client access).
Storage:
- Shared storage accessible by all cluster nodes (e.g., SAN or SMB).
- Configure storage before cluster setup.
Domain Account: A domain user account with administrative privileges.
Hardware Validation: Verify hardware compatibility using the Cluster Validation Wizard.

Step 1: Install the Failover Clustering Feature

Log in to each server with administrative privileges.
Open Server Manager > Click Manage > Add Roles and Features.
In the wizard:
- Role-based or feature-based installation > Next.
- Select your server > Next.
- Go to the Features section and select Failover Clustering > Install.
Repeat the process on all nodes.
Install the Failover Clustering Tools (optional for GUI management).

Step 2: Validate the Cluster Configuration

Open Failover Cluster Manager:
- Use failovercluster.msc or search in the Start Menu.
Click Validate Configuration.
Add the servers to be included in the cluster.
Run all validation tests:
- Storage: Ensure shared storage is accessible to all nodes.
- Network: Ensure proper network configuration.
- System Configuration: Verify OS and hardware compatibility.
Address any validation warnings or errors before proceeding.

Step 3: Create the Cluster

In Failover Cluster Manager, click Create Cluster.
Add the servers you validated.
Assign a Cluster Name and a Cluster IP Address:
- The cluster name and IP will be used by clients to access cluster services.
Confirm the configuration and click Create.
Verify the cluster is successfully created.

Step 4: Configure Cluster Networks

In Failover Cluster Manager, go to Networks.
Ensure:
- One network is marked for Cluster and Client Communications.
- Another network is used only for Cluster Communication (Heartbeat).

Step 5: Add Storage to the Cluster

In Failover Cluster Manager, click Disks > Add Disk.
Select shared storage available to all nodes.
Configure the disk as a Cluster Shared Volume (CSV):
- Right-click the disk > Add to Cluster Shared Volumes.
- CSV is ideal for Hyper-V and file server clusters.

Step 6: Configure a Cluster Role

Cluster roles are applications or services that run on the cluster.

In Failover Cluster Manager, click Roles > Configure Role.
Choose the type of role:
- File Server: For shared file storage.
- Virtual Machines: For high-availability Hyper-V virtual machines.
- Other Services or Applications: For specific workloads.
Configure role-specific settings and dependencies.
Verify the role is online and functional.

Step 7: Test Failover

Right-click the cluster role and select Move > Best Possible Node.
Ensure the role moves to another node without service interruption.
Test failback by moving the role back to the original node.

Step 8: Monitor and Maintain the Cluster

Regularly check the Failover Cluster Manager Dashboard for health and warnings.
Set up Event Monitoring:
- Use Event Viewer to monitor cluster events.
Implement Backups:
- Backup cluster configurations and applications regularly.

Optional: Advanced Configurations

Quorum Configuration:
Ensure proper quorum settings for your cluster, such as Node Majority, File Share Witness, or Cloud Witness.
Cluster-Aware Updating (CAU):
Automate Windows updates on cluster nodes with minimal downtime.
Hyper-V Failover Cluster:
Configure highly available virtual machines by adding Hyper-V workloads.

Conclusion

Once configured, the Windows Server Failover Cluster provides high availability and disaster recovery for critical applications and services. Regular monitoring and adherence to best practices will ensure optimal performance and reliability.