A new feature for the windows server 2019 that is currently released in the Windows insiders. If you want to test it out and provice feedback please follow the link and sign up.
One of the quorum models for Failover Clustering is the ability to use a file share as a witness resource. The File Share Witness is designated a vote in the Cluster when needed and can act as a tie breaker in case there is ever a split between nodes.
There is a specific requirement that the witness should be joined to the domain and part of the same forest. And the reason is that it needs Kerberos to connect and authenticate with the share.
For Windows Server 2019, additional safeguards have been added to help protect from misconfigurations. We have added logic to check to check if the share is going to DFS.
Microsoft does not support running the File Share Witness on a DFS share and did not support it in the past and we will not support it for the foreseeable future.
In a Windows 2016 4-node multi-site Cluster with two nodes at each site running SQL FCI, where each side utilizing a storage replication for the shared drives. This connection to the file share Witness, a part of the DFS share.
The Storage Migration Service was created to migrate servers and their data without re-configuring applications or users.
- Migrates unstructured data from anywhere into Azure & modern Windows Servers
- It’s fast, consistent, and scalable
- It takes care of complexity
- It provides an easily-learned graphical workflow
Windows Server 2019 and the Storage Migration Service are not supported in production environments!