Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link:

Contents of this Issue


Page 54 of 212

43 C H A P T E R 3 | Higher availability Note In the current release of Windows Server 2016 Technical Preview, this feature is enabled by default. However, you must use PowerShell to create a workgroup cluster because the Failover Cluster Manager snap-in does not support this functionality. Furthermore, configuring a cross- domain cluster is more complex than configuring a workgroup cluster because Kerberos is required to make cross-domain authentication work correctly. You can learn more about configuration requirements for both scenarios by referring to "Workgroup and Multi-domain clusters in Windows Server 2016" at Configuring a cloud witness Maintaining quorum is the most important function of any clustering software. In SQL Server, the most frequently deployed model is Node And File Share Majority. One of the challenges when you are designing a disaster-recovery architecture is to decide where to place the file share witness. Microsoft's official recommendation is to place it in a third data center, assuming you have a primary/secondary availability group configuration. Many organizations already have two data centers, but fewer have a third data center. Windows Server 2016 Technical Preview introduces a new feature, the cloud witness, that address this problem. You create a cloud witness by using the Cluster Quorum Wizard. Before you launch this wizard, you must have an active Azure subscription and a storage account. To launch the wizard, right-click the server in the Failover Cluster Manager, point to More Actions, select Configure Cluster Quorum Settings, select the Select The Quorum Witness option, and then select the Configure A Cloud Witness option, as shown in Figure 3-7. Figure 3-7: Creating a cloud witness for a cluster quorum.

Articles in this issue

Links on this page

Archives of this issue

view archives of Netherlands: Software - Introductie van Micorosoft SQL Server 2016