Applies To: Windows Server 2016
Failover clustering - a Windows Server feature that enables you to group multiple servers together into a fault-tolerant cluster - provides new and improved features for software-defined datacenter customers and many other workloads running clusters on physical hardware or in virtual machines.
A failover cluster is a group of independent computers that work together to increase the availability and scalability of clustered roles (formerly called clustered applications and services). The clustered servers (called nodes) are connected by physical cables and by software. If one or more of the cluster nodes fail, other nodes begin to provide service (a process known as failover). In addition, the clustered roles are proactively monitored to verify that they are working properly. If they are not working, they are restarted or moved to another node.
Failover clusters also provide Cluster Shared Volume (CSV) functionality that provides a consistent, distributed namespace that clustered roles can use to access shared storage from all nodes. With the Failover Clustering feature, users experience a minimum of disruptions in service.
Failover Clustering has many practical applications, including:
- Highly available or continuously available file share storage for applications such as Microsoft SQL Server and Hyper-V virtual machines
- Highly available clustered roles that run on physical servers or on virtual machines that are installed on servers running Hyper-V
Here are some of the new features in Windows Server 2016 - for more details, see What's new in Failover Clustering:
Enables an administrator to upgrade the operating system of the cluster nodes from without stopping the Hyper-V or the Scale-Out File Server workloads.
A new type of quorum witness that leverages Microsoft Azure to help determine which cluster node should be considered authoritative if a node goes offline.
Improves the day-to-day monitoring, operations, and maintenance experience of Storage Spaces Direct clusters.
Enables you to define what fault domain to use with a Storage Spaces Direct cluster. A fault domain is a set of hardware that share a single point of failure, such as a server node, server chassis, or rack.
Helps load be evenly distributed across nodes in a Failover Cluster by identifying busy nodes and live-migrating VMs on these nodes to less busy nodes.
Enables easier configuration of multiple network adapters in a cluster.
- Failover Clustering Hardware Requirements and Storage Options
- Validate Hardware for Failover Clustering
- Network Recommendations for a Hyper-V Cluster
- Installing the Failover Clustering Feature and Tools
- Validate Hardware for a Failover Cluster
- Prestage Cluster Computer Objects in Active Directory Domain Services
- Creating a Failover Cluster
- Deploy Hyper-V over SMB
- Deploy a Scale-Out File Server
- iSCSI Target Block Storage, How To
- Deploy an Active Directory Detached Cluster
- Using Guest Clustering for High Availability
- Deploy a Guest Cluster using a Shared Virtual Hard Disk
- Building Your Cloud Infrastructure: Scenario Overview
- Configure and Manage the Quorum in a Failover Cluster
- Use Cluster Shared Volumes in a Failover Cluster
- Cluster-Aware Updating Overview