When a high-demanded service or website is hosted on a Server, they are commonly designed such that at that spot are multiple balancing nodes. These nodes brand certain that when 1 node fails, at that spot are other nodes which tin own got care. In instance of Windows Server 2019/2016, the node balancing industrial plant through a quorum system. In this guide, nosotros volition verbalise virtually the Windows File Share Witness feature.
File Share Witness & Quorum system
A quorum organization is a vote based organization where a pose out of notes should live introduce to brand certain they piece of occupation inwards instance of failure. Sometimes, the voting organization comes to stop when at that spot is “even number” of amount votes. The signal of voting is simple. It makes certain that nodes are non overloaded. Introducing a File Share Witness human activeness every bit a tiebreaker. It tin render an additional quorum vote when necessary. This makes certain that a cluster continues to run inwards the resultant of a site outage.
So if you lot own got 4 nodes which are balanced inwards a 2-2 format, together with if 1 of the nodes fail, other two nodes should live able to residue it. However, amongst 2-2 format, it gets stuck. If information technology admins tin deploy a File Share Witness which tin add together a vote to two of those existing nodes, a quorum volition live reached, together with nodes tin own got help of everything. Read to a greater extent than virtually Legacy & Modern FSW here.
What is File Share Witness characteristic inwards Windows 2019/2016
One of the fundamental requirement for FSW to piece of occupation is that it should live travel is that it must live domain joined together with a travel of the same forest. This touchstone was of import because the failover Cluster utilizes Kerberos for the Cluster Name Object (CNO) to connect together with authenticate the share. This sometimes powerfulness non live possible because of several reasons including
- Poor meshing connection.
- The domain controller is non available.
- No active directory CNO object
- and lastly no shared drives for a disk witness.
Keeping these scenarios inwards mind, Microsft added a characteristic inwards Windows 2019 which quorum organization piece of occupation fifty-fifty when it’s non travel of a domain. This was possible past times using a local user describe of piece of occupation organization human relationship on the server the FSW is connected to.
IT admins can create a local (not administrative) user account, give that local describe of piece of occupation organization human relationship amount rights to the share, connect the cluster to the share. Here are the steps:
- Log on to SERVER together with create a local user describe of piece of occupation organization human relationship (i.e. FSW-ACCT)
- Create a folder on the SERVER together with part it out
- Give the local user describe of piece of occupation organization human relationship (FSW-ACCT) amount rights to the share
- Log inwards to 1 of your cluster nodes together with run the PowerShell command:
Set-ClusterQuorum -FileShareWitness \\SERVER\SHARE -Credential $(Get-Credential)
- You volition live prompted for the describe of piece of occupation organization human relationship together with password for which you lot should travel into SERVER\FSW-ACCT together with the password.
Further, if at that spot is no extra server available, a USB drive connected to a router industrial plant every bit well. Once connected, you lot tin ready your part name, username, together with password for access. This industrial plant amongst SMB 2.0 together with above.
You tin read to a greater extent than about File Share Witness characteristic on MSDN.