是否SQL Azure的自动地域复制自动故障转移？ [英] Does SQL Azure automatically geo-replication automatically failover?

问题描述

我们必须在SQL Azure中（专业版）地缘复制的数据库，并想知道如果我们所指向的是主中南美国的数据库中，如果出现故障做，我们必须手动更改我们的连接字符串在我们的代码（C＃.net /实体框架6）指向北说美国新的数据库？我们正在寻找办法有一个连接字符串，然后天青做在幕后到现在指向新的数据库，如果主不断下降。这是可能的。

We have a geo-replicated database in SQL Azure (Premium) and are wondering if we are pointing to the South Central US database that is the master, if that goes down do we have to manually change our connection strings in our code (C# .Net / Entity Framework 6) to point to the new database in say North US? We are looking for a way to have a single connection string and then Azure do the under the covers to now point to the new database if the master ever goes down. Is that possible?

的方法更新如下：？结果
所以我看到这个，我们需要手动进入一个web.config文件在生产系统上的文件时，一个区域的下降和主数据库更改为另一部正在工作复制的数据库。

Update on method followed:
so I read this that we have to manually go into a web.config file on a production system when a region goes down and change the main database to another replicated database that is working.

我决定只硬编码东部，西部和南部地区，在web配置和编写代码来重试和故障转移到其他地区，如果主要的一个不能到达。这意味着它只能读，不能写，直到微软或我们手动故障转移师傅只读活动奴隶。不是我最好的体验。需要人为干预知道它的下跌，然后翻转它和自定义代码

I decided to just hard code east, west and south regions in the web config and wrote code to retry and fail over to other regions if the main one couldn't be reached. This means it can only read, not write until Microsoft or we manually failover the master to a Read Only Active slave. Not the best experience to me. Requires human intervention knowing it's down, then flipping it and custom code

推荐答案

您应该阅读这篇文章的设计为云灾难恢复解决方案主动地域复制

You should read this article Designing Cloud Solutions for Disaster Recovery Using Active Geo-Replication

有可用性如何设置Azure的几个选项。因此，根据您的要求和配置，您可以需要改变SQL连接字符串。在这篇文章中，关键是看SLA。例如，在 选项2：主动 - 主动计算与解耦故障转移的，SLA是：

There are a few options on how to setup Azure for availability. So, based on your requirements and configuration, you may need to change SQL Connection String. The key in this article is to look at the "SLA". For example, in Option 2: Active-active compute with decoupled failover, the SLA is:

RTO = SQL connection change + database state change + application verification test

的通知在 SQL连接变化;这意味着一个连接字符串的变化。

Notice the SQL connection change; this implies a connection string change.

这篇关于是否SQL Azure的自动地域复制自动故障转移？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！