Azure Storage Account LastSyncTime not updating with GRS replication

Question

We are using an Azure Storage Account with Global Redundancy replication but the account's LastSyncTime has not updated since March 23, despite uploading additional files on March 26 and 29 as requested by the engineer. We have not configured Azure File Sync. Can anyone suggest why the sync time has stopped and possible solutions? Thank you.

Answer 1

@Michael Meier Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

Adding more information to the above response

If the LastSyncTime for your Azure Storage Account with Global Redundancy replication has not updated since March 23, it could be due to a number of reasons. Here are some possible causes and solutions:

1. Network connectivity issues: Check if there are any network connectivity issues between your primary and secondary regions. You can use the Azure Network Watcher service to diagnose network connectivity issues and troubleshoot them.
2. Storage account issues: Check if there are any issues with your storage account, such as storage account limits or quotas being reached. You can use the Azure Storage Explorer tool to view and manage your storage account.
3. Replication lag: Check if there is a replication lag between your primary and secondary regions. Replication lag can occur due to network latency or other factors. You can use the Azure portal to view the replication status of your storage account and monitor the replication lag.
4. Outdated replication settings: Check if your replication settings are outdated or incorrect. You can use the Azure portal to view and update your replication settings.
5. Azure service issues: Check if there are any service issues with Azure Storage or Azure Global Redundancy replication. You can use the Azure status page to view the status of Azure services and check for any service issues.

Additional information: See Get the Last Sync Time property

Remember, the LastSyncTime is a GMT date/time value, and all data and metadata written prior to the last sync time is available on the secondary, while data and metadata written after the last sync time may not have been written to the secondary and may be lost2. It’s important to regularly monitor this property, especially if you rely on it for failover operations

Please let us know if you have any further queries. I’m happy to assist you further.    

---

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.