Quick reference guide to managing Windows failover clusters

Quick reference guide to managing Windows failover clusters

HomeEnayat MeerQuick reference guide to managing Windows failover clusters
Quick reference guide to managing Windows failover clusters
ChannelPublish DateThumbnail & View CountDownload Video
Channel AvatarPublish Date not found Thumbnail
0 Views
MCSA Exam: 70-740 and 70-741
Failover clustering—a Windows Server feature that lets you group multiple servers into a fault-tolerant cluster—provides new and improved capabilities for customers with software-defined data centers and many other workloads that run 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 cluster roles (formerly called cluster applications and services). The cluster servers (called nodes) are connected by physical cables and software. If one or more cluster nodes fail, other nodes take over service (a process called failover). In addition, the cluster roles are proactively monitored to ensure they are functioning properly. If they are not working, they are restarted or moved to another node.

Failover clusters also provide the Cluster Shared Volume (CSV) feature, which provides a consistent, distributed namespace that cluster roles can use to access shared storage from all nodes. With the failover cluster feature, users experience minimal service disruption.

Failover clustering has many practical applications, including:

Highly available or always-on file share storage for applications such as Microsoft SQL Server and Hyper-V virtual machines
Highly available cluster roles that run on physical servers or on virtual machines installed on servers with Hyper-V.
What's new

Ongoing upgrades for cluster operating systems
Allows an administrator to upgrade the operating system of the cluster nodes without stopping the Hyper-V or Scale-Out File Server workloads.

Cloud Witness for a failover cluster
A new type of quorum witness that uses Microsoft Azure to determine which cluster node should be considered authoritative if a node goes offline.

Healthcare
Improves daily monitoring, operations, and maintenance of Storage Spaces Direct clusters.

Error domains
Allows you to define which fault domain to use with a Storage Spaces Direct cluster. A fault domain is a group of hardware with a common point of failure, such as a server node, server chassis, or rack.

VM load balancing
Helps evenly distribute the load across nodes in a failover cluster by identifying busy nodes and live migrating VMs on those nodes to less busy nodes.

Simplified SMB multi-channel and multi-NIC cluster networks
Enables easier configuration of multiple network adapters in a cluster.

planning
Hardware requirements and storage options for failover clustering
Checking the hardware for failover clustering
Network recommendations for a Hyper-V cluster
Mission
Installing the failover clustering feature and tools
Checking the hardware for a failover cluster
Pre-provisioning cluster computer objects in Active Directory Domain Services
Creating a failover cluster
Deploying Hyper-V over SMB
Deploying a scale-out file server
iSCSI Target Block Storage, How to
Deploying a separate Active Directory cluster
Using the guest cluster for high availability
Deploying a guest cluster using a shared virtual disk
Building your cloud infrastructure: Scenario overview

Operations
Configuring and managing quorum in a failover cluster
Using Cluster Shared Volumes in a Failover Cluster
Overview of cluster-aware updating
Windows IT Pro Support

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.