In this post, I’ll explain how to address this requirement and provide a regional failover that requires no application connection string changes.įor our purposes, we’ll use the following simplified architecture diagram as a starting point: Some customers have expressed an interest in being able to perform a regional failover without later having to update the associated application connection strings. ![]() On the other hand, the manual process associated with a regional failover does introduce a change to the service endpoint name. With ZRHA, failover between the Primary and Standby servers is automatically managed by the Azure platform, and importantly, the service endpoint name does not change. This manifests itself as ZRHA in the primary region and a Read Replica in another region, preferably the paired region, as illustrated in the following diagram: One common pattern we’ve seen with several customers is the need for maximum in-region availability along with a cross region disaster recovery capability. In addition to the ‘in-region’ modes listed above, there’s also an option to design for protection of database services across Azure regions. For the latest list of Azure regions, in the Azure Database for MySQL documentation, see Azure regions. ![]() *ZRHA is only available in regions that support availability zones. Within a region, there are three potential options to consider, as shown in the following table: Note: For more information, see Azure Database for MySQL - Flexible Server - High Availability Concepts. The high availability solution is designed to ensure that committed data is never lost because of failures and that the database won't be a single point of failure in your software architecture. ![]() With Azure Database for MySQL - Flexible Server, you can configure high availability with automatic failover within a region.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |