Storage account stuck in data sync to secondary region

Richard Cain (RD-NA) 5

I have a storage account in West US that we have enabled RA-GRS resiliency on.
I wanted to perform a failover to the secondary region as part of a drill, but the storage account is stuck doing initial data sync from the primary to the secondary region and has been stuck in this state for days.

There's only 19GiB of data stored. I haven't been able to find anything that looks like an error message in the events log. I've tried switching redundancy to LRS and then back to RA-GRS on the console but the problem persists.

I did, one morning, see the message "this._model.isGeoReplicationSupported is not a function" on the redundancy page, but the message about "syncing" replaced it after refreshing the page.

I have other storage accounts in this region with RA-GRS enabled. In fact, I was able to perform a failover on this exact same storage account to the secondary region and back 4 months ago.

Does anyone have any idea what could be left to try?

KarishmaTiwari-MSFT 20,052 Reputation points Microsoft Employee

2024-10-09T22:02:21.9733333+00:00

@Richard Cain (RD-NA) Thanks for posting your query here. I see that you have posted another thread on it here: https://zcusa.951200.xyz/en-us/answers/questions/2100679/geo-redundancy-cannot-be-enabled-on-storage-accoun

Assuming that the other thread will have the most updated information on your issue, I will investigate and respond on the other thread. Let me know if that's not the case.
Richard Cain (RD-NA) 5 Reputation points

2024-10-09T22:06:33.36+00:00

Hi @KarishmaTiwari-MSFT
These threads are for two different storage accounts. I was performing failover on all 3 of my storage accounts in the same subscription. One was successful. The other two saw two different issues so I created a thread for each issue after I exhausted my knowledge and Azure documentation trying to fix them.
KarishmaTiwari-MSFT 20,052 Reputation points Microsoft Employee

2024-10-09T22:42:06.8066667+00:00
@Richard Cain (RD-NA) Thanks for confirming. Will treat these two threads separate then. Also,

I wanted to understand if there are any significant differences between the three storage accounts, especially between the one that succeeded vs the other two that failed.

Are you seeing this error: "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." If yes, did you get a chance to look at this thread: https://zcusa.951200.xyz/en-us/answers/questions/2034342/failover-cannot-yet-be-initiated-because-initial-d
Richard Cain (RD-NA) 5 Reputation points

2024-10-10T20:23:20.73+00:00
@KarishmaTiwari-MSFT Thank you, Karishma

I don't know of significant differences in the configuration of these three accounts

I have read that thread; however, the issue there seems related to having a massive amount of data (186TiB) being replicated back to the primary account which took 5 hours. As in the initial post above, my account here has only 19GiB of data and has been stuck in the initial sync for days.
KarishmaTiwari-MSFT 20,052 Reputation points Microsoft Employee

2024-10-14T00:56:00.3966667+00:00

Engaged with the customer offline.

1 answer

KarishmaTiwari-MSFT 20,052 Reputation points Microsoft Employee

2024-10-18T22:26:49.24+00:00

This was a one-off issue with the storage accounts and needed to be unblocked from the backend by the internal team.
If anyone encounters this issue, please create a new post on Microsoft Q&A and my team will be able to help.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Storage account stuck in data sync to secondary region

1 answer

Your answer