India +91 8886531212 info@itautomation.in

Windows failover cluster

What is Windows Failover Cluster?

Windows Failover Cluster and Complete Details Step by Step with Brief Explanation

A Windows Server Failover Cluster is a group of two or more independent servers that work together to increase the availability of applications and services. If one of the cluster nodes fails, another node in the cluster can take over its workload, a process known as failover. This helps to minimize downtime and ensure business continuity.

Step-by-Step Guide to Set Up a Basic Windows Failover Cluster

Step 1: Prerequisites

  • Identical Hardware and Software: Ensure all servers intended to be part of the cluster have similar hardware configurations (CPU, RAM, Network Adapters) and are running the same version of Windows Server.
  • Network Configuration:
    • Identical Network Adapters: Each server should have at least two network adapters: one for the public network (client communication) and one or more for the private network (inter-node communication/heartbeat). Using identical network adapter models is recommended.
    • Static IP Addresses: Assign static IP addresses to all network adapters on each server. Ensure the public network adapters are on the same subnet and the private network adapters are on a separate, dedicated subnet for cluster communication.
    • DNS Configuration: Ensure your DNS server is correctly configured and can resolve the names of all the servers you intend to add to the cluster.
  • Shared Storage: You'll need shared storage accessible by all nodes in the cluster. This is typically a Storage Area Network (SAN) or iSCSI target. Ensure the storage is properly configured, and LUNs (Logical Unit Numbers) are presented to all cluster nodes. Do not format these LUNs yet.
  • Domain Membership: All servers intended to be part of the failover cluster must be joined to the same Active Directory domain. The user account performing the cluster creation must have administrative privileges on all servers and the necessary permissions to create computer objects in the domain.

Step 2: Install the Failover Clustering Feature

You need to install the "Failover Clustering" feature on all servers that will be part of the cluster. You can do this through Server Manager or PowerShell:

Using Server Manager:

  1. Open Server Manager.
  2. Click Add Roles and Features.
  3. On the "Before you begin" page, click Next.
  4. Select Role-based or feature-based installation and click Next.
  5. Select the local server from the server pool and click Next.
  6. On the "Select server roles" page, click Next.
  7. On the "Select features" page, find and select Failover Clustering.
  8. A pop-up might appear asking to add required features; click Add Features.
  9. Click Next and then Install.
  10. Repeat these steps on all other servers you want to add to the cluster.

Using PowerShell:

  1. Open PowerShell as an administrator.
  2. Run the following command: 
    Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools
  3. Repeat this command on all other servers.

Step 3: Validate the Cluster Configuration

Before creating the cluster, it's crucial to run a validation wizard to ensure your servers, network, and storage are configured correctly for a failover cluster.

  1. Open Failover Cluster Manager. You can find it in Tools within Server Manager or by searching in the Start Menu.
  2. In the "Actions" pane (on the right), click Validate Configuration.
  3. On the "Before you begin" page, click Next.
  4. On the "Select Servers or a Cluster" page, enter the names of all the servers you want to include in the cluster, click Add, and then click Next.
  5. On the "Testing Options" page, it's recommended to select Run all tests (recommended) and click Next.
  6. On the "Confirmation" page, click Next.
  7. The wizard will run a series of tests. Once complete, review the Summary page.
  8. Crucially, address any errors. Warnings should also be investigated as they might indicate potential issues. Click View Report for detailed information about the tests.
  9. Fix any configuration problems identified in the validation report before proceeding. A cluster built on an invalid configuration is prone to issues.

Step 4: Create the Failover Cluster

Once the validation is successful, you can create the failover cluster.

  1. In Failover Cluster Manager, in the "Actions" pane, click Create Cluster.
  2. On the "Before you begin" page, click Next.
  3. On the "Select Servers" page, enter the names of the servers you want to add to the cluster, click Add, and then click Next.
  4. On the "Access Point for Administering the Cluster" page:
    • In the Cluster Name box, enter a unique name for your failover cluster. This name will be registered in DNS.
    • Under Network, if you have multiple network adapters, ensure the correct public network is selected.
    • In the Address field, enter a static IP address for the cluster. This IP address will be associated with the cluster name and will be used by clients to connect to clustered services and applications. Click Next.
  5. On the "Confirmation" page, review the settings. You can leave the "Add all eligible storage to the cluster" checkbox selected to automatically add the validated shared storage. Click Next.
  6. The wizard will now create the failover cluster. Once the process is complete, review the Summary page and click Finish.

Step 5: Configure Quorum Settings (Important)

The quorum determines how the cluster maintains a consistent view of its state and prevents "split-brain" scenarios where different nodes think they own resources. You need to configure the quorum based on your cluster size and configuration.

  1. In Failover Cluster Manager, right-click the newly created cluster name in the left pane and select More Actions > Configure Cluster Quorum Settings.
  2. On the "Before you begin" page, click Next.
  3. Select a quorum configuration option based on your environment:
    • Node Majority: Requires a majority of the voting nodes to be online for the cluster to run. Suitable for clusters with an odd number of nodes.
    • Node and Disk Majority: Requires a majority of voting nodes and a designated shared disk to be online. Useful for clusters with an even number of nodes to avoid ties.
    • Node and File Share Majority: Requires a majority of voting nodes and access to a designated file share witness on a separate server. Another option for even-numbered node clusters.
    • No Majority: Disk Only (Legacy): Relies solely on a shared disk. Generally not recommended for modern clusters.
  4. Follow the wizard prompts based on the quorum option you selected. For example, if you choose "Node and Disk Majority," you'll need to select the shared disk you want to use as the witness disk. If you choose "Node and File Share Majority," you'll need to specify the path to the file share.
  5. Click Next and then Finish.

Step 6: Add Clustered Roles and Features

Now that the basic cluster infrastructure is in place, you can configure highly available services and applications (clustered roles). Common clustered roles include:

  • File Server: Provides highly available shared folders.
  • SQL Server: Makes SQL Server databases highly available.
  • Hyper-V Replica Broker: Enables high availability for virtual machines.
  • Distributed Transaction Coordinator (DTC): Clusters the DTC service.
  • Generic Service/Application/Script: Allows you to make virtually any service, application, or script highly available.

To add a clustered role:

  1. In Failover Cluster Manager, right-click Roles in the left pane and select Configure Role....
  2. Follow the wizard, selecting the desired role and providing the necessary configuration information (e.g., client access point name, IP address, shared storage for a File Server role).

Step 7: Test Failover

After configuring clustered roles, it's essential to test the failover process to ensure everything works as expected.

  1. In Failover Cluster Manager, right-click a clustered role and select Move > Live Migration (if available and configured) or Move > Quick Migration or Move > Other Node and select a different node in the cluster.
  2. Monitor the process to ensure the role successfully moves to the target node and remains accessible to clients.
  3. You can also simulate a failure by shutting down or restarting one of the cluster nodes to observe automatic failover to another node.

By following these steps, you can set up a basic Windows Failover Cluster to enhance the availability of your critical services and applications. Remember that the specific configuration details will vary depending on your environment and the clustered roles you intend to deploy. Always refer to Microsoft's official documentation for in-depth information and best practices.

Module 1: Deploying and Managing Windows Server 2012

  • Windows Server 2012 Overview

  • Installing Windows Server 2012

  • Post-Installation Configuration of Windows Server 2012

  • Overview of Windows Server 2012 Management

  • Introduction to Windows PowerShel

    Module2: Introduction to Active Directory Domain Services

  • Lessons

  • Overview of AD DS

  • Overview of Domain Controllers

  • Installing a Domain Controller

    Module 3: Managing Active Directory Domain Services Objects

  • Lessons

  • Managing User Accounts

  • Managing Groups

  • Managing Computer Accounts

  • Delegating Administration

    Module 4: Automating Active Directory Domain Services Administration

  • Lessons

  • Using Command-line Tools for AD DS Administration

  • Using Windows PowerShell for AD DS Administration

  • Performing Bulk Operations with Windows PowerShell

    Module 5: Implementing IPv4

  • Lessons

  • Overview of TCP/IP

  • Understanding IPv4 Addressing

  • Subnetting and Supernetting

  • Configuring and Troubleshooting IPv4

    Module 6: Implementing Dynamic Host Configuration Protocol

  • Lessons

  • Overview of the DHCP Server Role

  • Configuring DHCP Scopes

  • Managing a DHCP Database

  • Securing and Monitoring DHCP

    Module 7: Implementing DNS

  • Lessons

  • Name Resolution for Windows Clients and Servers

  • Installing a DNS Server

  • Managing DNS Zones

    Module 8: Implementing IPv6

  • Lessons

  • Overview of IPv6

  • IPv6 Addressing

  • Coexistence with IPv4

  • IPv6 Transition Technologies

    Enroll with this course now 2,928 students enrolled

    • Get your admission now!

    Enroll