question

ErikaPrieto-1573 avatar image
0 Votes"
ErikaPrieto-1573 asked SumanthMarigowda-MSFT commented

Azure Files synchronization of unmodified open files

We have an Azure File Sync deployed on a Windows Server 2012 R2, and after syncing all files to Azure Files we detected that there were a large number of files archived to another disk (with a specific archiving solution), and the sync agent did not unarchive those files before replicating them to Azure. Now we are forcing the unarchiving of those files by doing a "read" of them, but we can't find a way to confirm if once we read those files once unarchived (without modifying anything in them), the sync agent detects them as changed (because of the access date which is new) and will re-sync them to Azure Files.

azure-files
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@ErikaPrieto-1573 Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused. [11:44 pm] Will Gries
What do you mean "archive"?


For better understanding the issue: Can you provide more information on your query?

0 Votes 0 ·

1 Answer

ErikaPrieto-1573 avatar image
0 Votes"
ErikaPrieto-1573 answered SumanthMarigowda-MSFT commented

When the files have more than 60 days without being used they are archived in another cheaper disk, we have an application that takes charge of this task. On the original disk it only leaves a kind of "pointer" that represents a link to the real physical location of the file that has been archived.
When configuring the Azure sync agent we were counting on the agent to read that file and then upload it to the cloud, but apparently it has not been so, because it has only taken a part of the file, because when we try to open it from the cloud it can not.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Is that Azure File Sync? AFS will leave a 0 byte file - if user clicks it it should pull back from Azure fileshare. Anytime they change the tiering it will 'start' countdown from that new date it's not retroactive - I think that might be the confusion there.


If I set up a 30 day retention policy starting today, the first tiered file will be 30 days from today. It will start creating a heatmap from the time it's turned on our changed. Anytime they make a change they should also recall all tiered files as those already tiered will still be under the previous policy.

https://docs.microsoft.com/en-us/azure/storage/file-sync/file-sync-cloud-tiering-overview

==============================================================================

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 Votes 0 ·