Azure File Sync not syncing some folders, no errors

Question

Azure file share was empty when sync was started. The sync ran well for a week and uploaded 500GBs out of 2.5TBs. There are a few sync errors for invalid file names/but none for the folders that are missing. I have looked through the Agent and Management Event Logs and didn't see anything related. Sync Group is Healthy.

In my case the file path is J:\KCR-sales\CECE. The CECE folder in the cloud is empty. The local folder has Ecom shoot, Old, Pictures, Test and and a text file. None of these folders are syncing.

What's strange is that their is another CECE folder under J:\Archives\CECE. Again CECE is empty in the cloud. The local CECE folder has 2015, 2016,and 2017 folders. Again none are syncing.

I was thinking about deleting the Server endpoint from the sync group and re-adding it using Authoritative Upload. I don't know if it would accomplish anything, but I'm out of ideas.

Answer 1

@BCI Azure Administrator
Apologies for the delayed response. Odd that both folders named CECE are failing to sync. I wonder if renaming these might resolve the issue. Please run the diagnostic script FileSyncErrorsReport.ps1 and look for any errors. See the troubleshooting guide here for information on this and related errors.

Hope this helps. Let us know if you are still facing issues syncing these after running the script.

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

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

Answer 2

So sort of a weird update.

I haven't run the script yet. I have had issues running it in the past. I even ran it on another server and got results for zero errors, but the Agent Event Log definitely had sync errors listed.

I have 6 sync groups on the server. I added a Test folder to each local drive and most updated the Azure File share with the new folder within seconds.

One of the larger drives(2TBs) took 5 mins to update with the new folder.

The drive that's currently having issues(2.5TBs) took about 30mins to upload the new folder.

Just to add context, the J:\KCR-Sales and J:\Archives folders both had another folder called Vince that wasn't syncing, similar to the CECE folder.

I decided to add a new folder to the J:\KCR-Sales\CECE folder, just to see if that triggered anything. It did end up triggering a file sync. It appears that all the folders under J:\KCR-Sales synced. The CECE folder and the Vince folder both synced. From 1:30PM to 4PM that day 260GBs synced.

I tried to do the same thing in the J:\Archive folder. I added a new folder to the CECE folder and the Vince folder. This time it didn't work and these folders didn't upload like under KCR-Sales. I added folders in the Azure side of things to try and trigger a sync from that end and still no go.

Another thing I noticed is one of the 9900 Errors under the Item Results Event Log for the J drive. It was for a .jpg that was pretty deep in another top folder, not KCR-Sales or Archives. I corrected the name of the file last week, it had a [] in the file name. It reported the same error again today even though it has been corrected. So it seems like it's not scanning the drive correctly or can't refresh some local database? This file still hasn't synced. Not seeing any other J: drive errors and Azure is only reporting the single sync error.

This may or not be relevant as well. The file server is a VM. It crashed during the initial sync do to running out of space on the C drive. They were able to expand the drive and get the VM back online, but maybe something with Azure Sync got corrupted and that's why it's not picking up changes? The fact that I was seemingly able to trigger one set of folders to sync, but not the other is odd.

I will try the script on this server and any other Trouble Shooting tips that seem relevant and report back. Please let me know if the new info provided helps.