azure - Microsoft Azure RA-GRS 存储 - 在 Microsoft 管理的故障转移到次要区域后，数据是否仍进行异地复制？

Question

在 Azure 存储帐户上使用 RA-GRS 复制时，如果发生区域中断并且存在 Microsoft 管理的故障转移到次要区域，该次要区域中的数据是否会再次自动进行异地复制？

同样，一旦原始主要区域重新上线，存储帐户是否会自动故障回复到该区域，还是保留在辅助区域中？

我可以找到有关当前预览版的客户管理的故障转移的大量信息，但我很难找到有关 Microsoft 管理的故障转移的信息。

Answer 1

对于您的问题:

1. 是的，该次要区域中的数据将自动再次进行读取访问异地复制。
2. 故障转移后，存储帐户将作为新的主存储端点保留在次要区域中，但自存储帐户 account 的 DNS 条目以来，所有现有 URI 在异地故障转移之前和之后都会以相同的方式工作。 .core.windows.net 将更新为从主要位置指向辅助位置。我认为，如果原来的主要区域重新上线，它可能会成为数据地理冗余的新辅助区域。您可以引用博客中的评论。 这取决于问题。我们可以选择对主数据库进行故障转移，或者从辅助数据库恢复主数据库上的数据，我们的选择取决于当前的问题。

What is the Geo-Failover Process? Geo failover is the process of configuring a storage account’s secondary location as the new primary location. At present, failover is at stamp level and we do not have the ability to failover a single storage account. We plan to provide an API to allow customers to trigger a failover at an account level, but this is not available yet. Given that failover is at the stamp level, in the event of a major disaster that affects the primary location, we will first try to restore the data in the primary location. Restoring of primary is given precedence since failing over to secondary may result in recent delta changes being lost because of the nature of replication being asynchronous, and not all applications may prefer failing over if the availability to the primary can be restored.

If we needed to perform a failover, affected customers will be notified via their subscription contact information. As part of the failover, the customer’s “account..core.windows.net” DNS entry would be updated to point from the primary location to the secondary location. Once this DNS change is propagated, the existing Blob, Table, and Queue URIs will work. This means that you do not need to change your application’s URIs – all existing URIs will work the same before and after a geo-failover. For example, if the primary location for a storage account “myaccount” was North Central US, then the DNS entry for myaccount..core.windows.net would direct traffic to North Central US. If a geo-failover became necessary, the DNS entry for myaccount..core.windows.net would be updated so that it would then direct all traffic for the storage account to South Central US. After the failover occurs, the location that is accepting traffic is considered the new primary location for the storage account. Once the new primary is up and accepting traffic, we will bootstrap to a new secondary to get the data geo redundant again.

您可以从 Microsoft Azure 存储团队博客获取更多详细信息--- Windows Azure Storage Redundancy Options and Read Access Geo Redundant Storage