There are two set of business continuity solution in Azure.
1) Active geo-replication
2) Failover groups
Active geo-replication
Geo-Replication is an Azure SQL database feature that allows you to create a readable secondary database in the same region or cross-region. We can failover to the secondary database in case of an outage for a long time on the primary database server.
Active geo-replication leverages the Always On availability group technology of the database engine to asynchronously replicate committed transactions on the primary database to a secondary database using snapshot isolation.
Up to four secondary are supported in the same or different regions. Geo-replication does not support automatic failover. The failover must be initiated manually by the application or the user. After failover, the new primary has a different connection string and it required to change accordingly in application side connection string.
Geo Replication is used for only Azure SQL Databases.
Failover groups
Failover groups allow you to manage replication and failover of a group of databases on a server or all databases to another region. It provides automatic failover features.
Failover groups support only one secondary server. If you need multiple secondary databases, consider using active geo-replication.
Connection end point need not required to change after failover in Failover group as it provides read-write and read-only listener endpoints that remain unchanged during failovers. The Read-Only listener can be used for reading intent application for load balancing while Read-write listener which can be used to direct the connections to the Primary SQL server where read and writes both can happen.
Failover groups is applicable to both Azure SQL DB and Azure SQL DB managed instance.
Comments
Post a Comment