Introduction

High availability enables your IT infrastructure to function continuously though some of the components may fail. High availability plays a vital role in case of a severe disruption in services that may lead to severe business impact.

It is a concept that entails the elimination of single points of failure to make sure that even if one of the components fail, such as a server, the service is still available.

Failover

Failover is a process. Whenever a primary system, network or a database fails or is abnormally terminated, then a Failover acts as a standby which helps resume these operations.

Failover Cluster

Failover cluster is a set of servers that work together to provide High Availability (HA) or Continuous availability (CA). As mentioned earlier, if one of the servers goes down another node in the cluster can take over its workload with minimal or no downtime. Some failover clusters use physical servers whereas others involve virtual machines (VMs).

CA clusters allow users to access and work on the services and applications without any incidence of timeouts (100% availability), in case of a server failure. HA clusters, on the other hand, may cause a short hiatus in the service, but system recovers automatically with minimum downtime and no data loss.

A cluster is a set of two or more nodes (servers) that transmit data for processing through cables or a dedicated secure network. Even load balancing, storage or concurrent/parallel processing is possible through other clustering technologies.

If you look at the above image, Node 1 and Node 2 have common shared storage. Whenever one node goes down, the other one will pick up from there. These two nodes have one virtual IP that all other clients connect to.

Let us take a look at the two failover clusters, namely High Availability Failover Clusters and Continuous Availability Failover Clusters.

High Availability Failover Clusters

In case of High Availability Failover Clusters, a set of servers share data and resources in the system. All the nodes have access to the shared storage.

High availability clusters also include a monitoring connection that servers use to check the “heartbeat” or health of the other servers. At any time, at least one of the nodes in a cluster is active, while at least one is passive.

Continuous Availability Failover Clusters

This system consists of multiple systems that share a single copy of a computer’s operating system. Software commands issued by one system are also executed on the other systems. In case of a failover, the user can check critical data in a transaction.

There are a few Failover Cluster types like Windows Server Failover Cluster (WSFC), VMware Failover Clusters, SQL Server Failover Clusters, and Red Hat Linux Failover Clusters.

Windows Server Failover Clustering (WSFC)

One of the powerful features of Windows Server is the ability to create Windows failover clusters. With Windows Server 2019, Windows Failover Clustering is more powerful than ever and can host many highly available resources for business-critical workloads.

Following are the types of Windows Server 2019 Failover Clustering:

  • Hyper-V Clustering
  • Clustering for File Services
  • Scale-Out File Server
  • Application Layer Clustering
  • Host Layer Clustering
  • Tiered Clustering

Each provides tremendous capabilities to ensure production workloads are resilient and highly available.

Windows Server 2019 Failover Clustering supports the new and demanding use cases with a combination of various cluster types and applications of various clustering technologies.

Windows Server Failover Clustering (WSFC) is a feature of the Windows server platform for improving the high availability of clustered roles (formerly called clustered applications and services). For example, say there are two servers. They communicate through a series of heartbeat signals over a dedicated network.

Supported Target Version

Supported Target Versions
Windows Server 2019

Hierarchy of Windows Failover Cluster

  Windows Failover Cluster
        - Windows Cluster Node
        - Windows Cluster Shared Volume
        - Windows Cluster Disk
        - Windows Cluster Role

Version History

Application VersionBug fixes / Enhancements
7.1.0
  • Powershell script optimizations.
  • Added Time outs for Native Bridge connection to handle threads holding issue and provided the feasibility to configure these timeouts from configuration UI.
7.0.0
  • Added script connection timeout support.
  • Discovery and Monitoring scripts optimizations.
6.0.0
  • Log File Monitoring support
  • New Metric support for Cluster Generic service state (windows_cluster_genericService_State)
5.0.2Set the Node IP by filtering the networks based on the role ClusterAndClient.
5.0.1Activity log changes & latest metric snapshot changes.
5.0.0Provided additional metric support on Windows Failover Cluster native type for NetWork State and Network Interface State metrics.
4.0.0Added Physical Disk and Roles as new resource types.
3.0.3Power shell script fix to close the session in case of failures.
3.0.2Fixed metric component alerting issue. Users can enable/disable alerting for specific metric components.
Click here to view the earlier version updates
Application VersionBug fixes / Enhancements
3.0.1Metric label support added.
3.0.0Added monitoring support for cluster shared volume.
2.1.3Full discovery support added.
2.1.2
  • App enhancement changes.
  • Macro support for alert subject and description customization.
  • Support added to get latest metric snapshot data (from Gateway v14.0.0).
  • Added support for Template level component filters.
2.1.1Added support to alert on gateway in case initial discovery fails with connectivity/authorization issues.
2.1.0Removed Port from Windows cluster app configuration page.
2.0.0Initial sdk app discovery & monitoring implementation.