In this article, we will provide an outline of Azure SQL Server FCI (Failover cluster instances. Bobcares, as a part of our Microsoft SQL Server Support Services, offers solutions to every query that comes our way.

FCI with SQL Server on Azure

A Windows Server Failover Clustering, WSFC (or just the cluster) node or, maybe, many subnets may host a single instance of SQL Server known as an FCI. Using failover cluster instances (FCI) with SQL servers running on Microsoft Azure provides local high availability.

An FCI appears on the network as a single SQL Server instance running on a single machine. However, in the event that the present WSFC node becomes unavailable, the FCI offers failover to a different WSFC node.

It is possible to use a disc witness, a cloud witness, or a file share witness for cluster quorum in failover cluster instances using SQL Server on Azure virtual machines. A Windows failover cluster employs a storage area network (SAN) that is accessible by both nodes as the shared storage in conventional on-premises clustered systems. The shared storage is where SQL Server files are kept, and only the active node can access them at once.

As a shared storage option for the deployment of SQL Server failover cluster instances, SQL Server on Azure VMs provides several choices such as Azure shared disks, Storage Spaces Direct, and Premium file share.

1. Azure shared disks: Azure shared discs with a failover cluster instance is supported by Windows Server Failover Clustering. This is beneficial for applications that want to move to Azure while maintaining their current high-availability and disaster recovery (HADR) architecture.

2. Storage Spaces Direct: On Azure Virtual Machines, failover clustering is compatible with the Windows Server technology, Storage Spaces Direct. It offers a virtual SAN that is software-based.

3. Premium file share: For SQL Server 2012 or later running on Windows Server 2012 or later, premium file shares offer increased flexibility and allow failover cluster instances. Premium file sharing feature continuous low latency and are SSD backed.

Installation & Configuration FCI with SQL Server on Azure

We have to follow the below steps to install and configure FCI with SQL server on Azure.

1. Firstly, create a virtual network that just uses the Azure cloud (VNet).
2. Then establish an Azure cloud service.
3. Also establish an Azure storage account.
4. Now create and configure Azure virtual machine.
5. Then add a data disc hosted by Azure to the virtual machines used as WSFC nodes.
6. Now install and set up an Active Directory Domain Controller.
7. Also set up the WSFC Nodes.
8. Then install and configure StarWind Virtual SAN.
9. Now explore iSCSI Target Portals.
10. Set up Multi-pathing and Connecting iSCSI Targets.
11. Format and start initialising the discs.
12. Now execute Failover Cluster Validation Wizard.
13. Setup the Windows Server 2016 Failover Cluster.
14. Now fix the Windows Server Failover Cluster Client Access Point.
15. Set up the Cluster Quorum parameters.
16. Install an SQL Server on a Windows Server 2016 Failover Cluster.
17. Now add a Node on a SQL Server Failover Clustered Instance.
18. Then create an Azure Internal Load Balancer.
19. Change the Virtual Network Name for the SQL Server Failover Clustered Instance.

[Need help with another query? We’re available 24/7.]

Conclusion

To conclude, we have provided a detailed information from our Tech team on FCI with SQL Server on Azure, along with a general outline for installing and configuring FCI on SQL Server.