An auto-failover group is an Azure SQL Database configuration built on geo-replication. It coordinates failover for one or more databases between primary and secondary regions, helping applications stay available when a region has trouble. section 10.5.2 section 10.7
Key capabilities include:
- Automatic or manual failover, selected through the failover policy. section 10.5.2
- Read-write and read-only listener endpoints that redirect traffic to the appropriate databases. section 10.5.2
- Graceful planned failover that synchronizes data before switching regional roles, minimizing data loss. section 10.5.2
Banning Books keeps ordering online
Banning Books can replicate BanningBooksDB to BanningBooksSecondaryServer, then create a failover group with an automatic policy. If the primary region fails, Azure SQL Database can move service to the synchronized secondary with less manual intervention. section 10.5.1 section 10.5.2
C:/> az sql failover-group create --name banningbooksfailovergroup --resource-group BanningRG --server BanningBooksServer --partner-server BanningBooksSecondaryServer --failover-policy Automatic --add-db BanningBooksDB
The Azure CLI example creates a failover group by naming the primary server, secondary partner, automatic policy, and database. section 10.5.2
