Till recently, SQL Server Always On Availability Groups were the only Cluster based High Availability option that was both supported and a recommended approach on Azure. You need to configure a failover clustered instance on the primary instance on the production data center for local high availability and an Availability Group replica on Microsoft Azure for disaster recovery in case of a hybrid deployment. For Hybrid, you needed a site-to-site VPN to allow communication between the primary data center and the virtual network on Microsoft Azure.
Note: If you buy something from our links, we might earn a commission. See our disclosure statement.
Microsoft included support (KB article 2721672) for volume-level replication for non-shared storage when used to deploy Windows Server Failover Clusters. This enables you to use 3rd Party replication providers like Doubletake Software, SIOS Data Keeper, StarWind Virtual SAN to simulate a SAN and enable FCI based Clusters on Azure a.k.a Geo-Clusters.
Typical FCI Deployment with a 2 Node Cluster
The Azure Virtual Network enables you to extend your on-premises network to Windows Azure and securely connect it using an IPsec connection
After the network is configured and connectivity is achieved, the next steps is to configure the Cluster and SQL Server Installation:
You need to use Azure hosted storage using either of the following options:
Comments are closed.