Azure Blob Storage with GZRS Replication, DR Testing

Pallab Chakraborty 401 Reputation points
2021-03-12T15:45:04.24+00:00

I would like to know the below things please.

1) I did a failover of my Azure Storage Account with GZRS replication from Canada Central to Canada East and i saw that the replication got changed to LRS automatically as i believe, that is how it should be. So i believe i have to reconfigure the replication once again. But while reconfiguring, i didn't see any option to convert it back to GZRS, it was only GRS. So is this how it should be that once you failover from Primary to Secondary with GZRS, you cannot get back to GZRS?

2) My storage account is configured with private endpoint and private link. I have an internal Storage API that will be be called by a front end application to talk to the Private Endpoint Storage Account and the blobs inside it. So my question is, if i do a failover of my storage account during disaster from Primary Canada Central to Secondary Canada East, is there anything that needs to be done on the Private Endpoint side so that the storage account traffic is redirected to Canada East, or this will be done automatically by the service on the backend?

Appreciate a quick reply please.

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,684 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,427 questions
Azure Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
460 questions
0 comments
Accepted answer
  1. Sumarigo-MSFT 43,486 Reputation points Microsoft Employee
    2021-03-16T13:26:50.17+00:00

    @Pallab Chakraborty Welcome to Microsoft Q&A, Thank you for posting your query!

    Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.

    • This is expected behavior. LRS -> GZRS with LRS as primary is not supported.

    To get back to the original state (GZRS), you have to
    (1) Convert LRS in to GRS,
    (2) Failback to (as LRS),
    (3) Then request Azure to migrate this LRS to ZRS , which can then be converted to GZRS .

    Change how a storage account is replicated

    After the failover, your storage account type is automatically converted to locally redundant storage (LRS) in the new primary region. You can re-enable geo-redundant storage (GRS) or read-access geo-redundant storage (RA-GRS) for the account. Note that converting from LRS to GRS or RA-GRS incurs an additional cost.

    After you re-enable GRS for your storage account, Microsoft begins replicating the data in your account to the new secondary region. Replication time is dependent on the amount of data being replicated.

    • For read access to the secondary region with a storage account configured for geo-redundant storage, you need separate private endpoints for both the primary and secondary instances of the service. You don't need to create a private endpoint for the secondary instance for failover. The private endpoint will automatically connect to the new primary instance after failover.

    Hope this helps!

    Kindly let us know if the above helps or you need further assistance on this issue.

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest