Failover cannot yet be initiated because initial data synchronization from the primary to secondary region is in progress. Failover will be available when synchronization is complete.

Goyal, Gaurav 41 Reputation points
2024-09-03T14:05:36.6666667+00:00

I did the failover and it took only 15 mins. But now I am trying to again go back to Primary region so I did Failover Finalize to make the storage account from LRS to RA-GRS. but it is running from last 2 hours. Due to it I am stuck and can move to Failback step. Any ideas?

Failover - 15 mins

Failover Finalize - Running from more than 2 hours

Failback - Stuck due to above step.

I found this:
Initial synchronization from the primary to the secondary region must complete before the failover process can begin.

But normally how much it takes for Initial Synchronization to be completed.

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.
3,105 questions
Accepted answer
  1. KarishmaTiwari-MSFT 19,872 Reputation points Microsoft Employee
    2024-09-06T08:09:32.1166667+00:00

    @Goyal, Gaurav When you do your failover, the replicated data already exists in the secondary and this is what is converted to LRS. When you go to convert from LRS to GRS to go back the other way, the data needs to be re-replicated which can take some time and depends on a number of factors that are called out in the doc here: The time and cost of failing over.

    These factors include:

    • The number and size of the objects in the storage account. Replicating many small objects can take longer than replicating fewer and larger objects.
    • The available resources for background replication, such as CPU, memory, disk, and WAN capacity. Live traffic takes priority over geo replication.
    • The number of snapshots per blob, if applicable.
    • The data partitioning strategy, if your storage account contains tables. The replication process can't scale beyond the number of partition keys that you use.

    Unplanned failover replicates a true disaster simulation where the primary region would be impacted or potentially lost, as a result, the data is the primary region is deleted and the account becomes LRS (since the geo-paired region is "unavailable"). When you re-enable GRS/RA-GRS there is a full data copy being replicated back to the previous primary region (since it is now deleted). 

    Planned failover would be a great option for you in the future if you have concerns with the timeline to re-enable GRS.

    Hope this information helps. Let me know in the comments if you have any questions.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. KarishmaTiwari-MSFT 19,872 Reputation points Microsoft Employee
    2024-09-03T23:13:16.5866667+00:00

    @Goyal, Gaurav The initial synchronization from the primary to the secondary region typically takes several minutes, but this can vary depending on the amount of data and network conditions.
    https://video2.skills-academy.com/en-us/azure/storage/common/storage-initiate-account-failover?tabs=azure-portal#initiate-the-failover

    If the process seems stuck, you will need to contact Azure support for further assistance from the support engineer with backend access. Let me know and I can help with it.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.