Microsoft Azure RA-GRS 存储 - 在 Microsoft 管理的故障转移到次要区域后，数据是否仍在异地复制？
Microsoft Azure RA-GRS Storage - After a Microsoft-managed failover to secondary region, is the data still geo-replicated?
在 Azure 存储帐户上使用 RA-GRS 复制时，如果发生区域中断并且存在 Microsoft 管理的到次要区域的故障转移，该次要区域中的数据读取访问是否会再次自动异地复制？
同样，一旦原始主要区域重新联机，存储帐户会自动故障回复到该区域还是保留在次要区域中？
我可以找到大量有关当前处于预览状态的客户管理的故障转移的信息，但我很难找到有关 Microsoft 管理的故障转移的信息。
您的问题：
- 是的，该次要区域中的数据将再次自动进行读取访问地理复制。
- 故障转移后，存储帐户将保留在辅助区域中作为新的主要存储端点，但所有现有 URI 在地理故障转移前后都将工作相同，因为您的存储帐户的 DNS 条目
account..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
在 Azure 存储帐户上使用 RA-GRS 复制时，如果发生区域中断并且存在 Microsoft 管理的到次要区域的故障转移，该次要区域中的数据读取访问是否会再次自动异地复制？
同样，一旦原始主要区域重新联机，存储帐户会自动故障回复到该区域还是保留在次要区域中？
我可以找到大量有关当前处于预览状态的客户管理的故障转移的信息，但我很难找到有关 Microsoft 管理的故障转移的信息。
您的问题：
- 是的，该次要区域中的数据将再次自动进行读取访问地理复制。
- 故障转移后，存储帐户将保留在辅助区域中作为新的主要存储端点，但所有现有 URI 在地理故障转移前后都将工作相同，因为您的存储帐户的 DNS 条目
account..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