Phil Brewer
My feedback
-
63 votesPhil Brewer
supported this idea
·
An error occurred while saving the comment -
1 votePhil Brewer
shared this idea
·
-
2,212 votes
As you mentioned, we initiate a change detection job once every 24 hours to enumerate the Azure file share and scan for changes. This is required for the Azure file share because Azure Files currently lacks a change notification mechanism like Windows Server has. Long term we will add this capability and have automatic immediate sync.
There is now a way to trigger sync to happen on files that are placed directly in the Azure File share. With this new cmdlet you can point sync to particular files or directories and have it look for changes right then. This is intended for scenarios where some type of automated process in Azure is doing the file edits or migrations are done by an admin (like moving a new directory of files into the share). For end-user changes, the best thing to do is install Azure File Sync in an IaaS VM…
Phil Brewer
supported this idea
·
-
423 votes
This feature is under review.
Thanks
An error occurred while saving the comment Phil Brewer
commented
Yes this is critically needed. Is there any site where we can see roadmap for Azure Stack?
Phil Brewer
supported this idea
·
-
1 votePhil Brewer
shared this idea
·
-
112 votes
Thanks for your request this is currently under review.
It would be good if you can detail whether you need NC or NV series?
Thanks
Phil Brewer
supported this idea
·
An error occurred while saving the comment Phil Brewer
commented
Yes please. We need NV Series support in Azure Stack for Laser scan registration. Any update on when this may be rolled out?
Yes absolutely need to implement some backup mechanism or allow the Selective Disk Preview to work.