Global File Locking for Azure File Sync
For Azure File Sync on multiple geographically diverse servers, lock files across the enterprise to eliminate conflicts.
For example, a user in Chicago opens a spreadsheet on a local server, and that server is running Azure File Sync to a share that is also mounted by a server in Atlanta also running Azure File Sync. The file lock for the spreadsheet should be global, preventing write access in Atlanta when opened in Chicago.
See Panzura.com for reference.
This is something we are actively investigating, and would appreciate your feedback on the need to do this, and especially how to ranks compared to other items we could pickup for Azure Files and Azure File Sync.
We’d like to hear from you on this item. Please send us an email at AzureFiles@microsoft.com, and of course vote for this item if you would like to see it.
Program Manager, Azure Files
I work for an MSP and we have multiple firms that have 4 to 5 offices in different cities that often work on files for projects in other cities. AFS looks like a great way to have the local servers all synced, but the lack of Global File Locking seems to be the common hang up. They work with an array of file types: Docs, XLS, CAD, FileMakerPro, etc.
Count me in. I work for an MSP and have 2 opportunities for this. 2 Different companies, with 4-5TB data each, with many remote offices, using CAD,Solidworks. File locking is a critical need. I just voted. Make sure you get people to vote.
Grant Klaaysen commented
Azure File Sync sounds awesome but without Global File Locking it misses the mark.
I think this is the single most important feature to add next and will simply make this product a no brainer for virtually any company still using and needing to use file shares.
Where are we with this? Anything to assist in file locks between endpoints is a real world need.
We have a need for global locking due to the nature of the files we work with....mostly CAD related, but we would see a need with other applications.
I believe the status is well past Under Review, and should be changed to Planned. Please advise...
We would very much like this feature for collaborating across offices where teams are working on the same files. Not having this prevents many use cases involving cross-office collaboration.
James Stetson commented
This is seriously needed. The reality is that Microsoft Customers experience both the pros and cons of local office file servers. Pros: speed of access, speed of creating, and speed of re-organizing content. Cons: duplicate/redundant files and inability to perform effective collaboration. SharePoint is all well and good, but, at the end of the day, it is far too heavy for most users. Storing files in the cloud is great, except that it's painfully slow. The combination of a local Windows Server with a central cloud storage and global file locking is what we need. The Windows Server in an office would transform into a caching, print, and systems management (DHCP/SCCM/Intune) node. There is no question that having a solution like this would be wildly popular at Microsoft-centric companies.
I would like to +1 on the specific use case for Autodesk products. Our files are large, they are worked on in real time by teams in different geographic locations. This is a real problem, and AFS could be a real solution as long as they get file locking right in terms of how Autodesk uses file locking. As I understand it Autodesk uses file locking a bit different than most programs. Unfortunately I cannot find the Autodesk KB where it details that. If anyone can find that KB, please post here.
Jonathan Weekes commented
This feature is the most requested. I currently have a client that would like to use it for engineering files (AutoCAD DWG files), but due to the lack of a file lock they can't.
Please see https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/File-locking-no-longer-controlled-by-software.html
As I understand it, this feature has moved passed 'Under Review', and it would be important to see the status here be updated to something that better indicates where MS is at with this much needed feature. Thanks for all the hard work on such game changing technology!
I think a comment like 'cannot figure out a perfect system before they offer it' is wildly unrealistic. You cannot steer a ship unless its moving, and you are more then welcome to wait for General Availability, and/or the features you want or need before you play in a sandbox you don't like. Certainly no need to muddle up comments with impatient and useless criticisms.
I am just amazed that a company like MS cannot figure out a perfect system before they offer it to public. Beta, non beta, testing whatever they want to call it, this is exhausting and disappointing.
Imagine, you are presenting a project update to your upper management and telling them the project completed, is in production but no one can start using it just yet.
AArrggghhhh, and they have the audacity to present it to us...
Missing Locking is a showstopper!
Martin Gudel commented
Hi Will Gries,
file locking is something that prevents some of my customers from using Azure File Sync as their file server replication partner.
I was very glad to see this request, but now I understand that this is under review for 2 months.
What I really need is a feature that sets a file locked when a writable copy on one oft the replication instances is opened.
What exactly is the information you need to proceed?
Brian Cook commented
We are just coming up on Panzura. If Azure File Sync had the file locking and centralized management we'd possibly go with it over Panzura. We are a VMware shop so Panzura and its Linux based system fit nicely. We are definitely going to keep an eye on Azure File Sync in the same way we are keeping an eye on Hyper-V.
Paul Gilchrist commented
This is the one missing feature that makes us consider Nasuni over Azure File Sync
I'm investigating distributed/cloud file systems at the moment for a client. I really like a lot of what Azure File Sync is offering, but lack of file locking could be the deal-breaker.
This is HUGE! talonstorage.com does the same thing, although they are MUCH better than Panzura because they are Windows based, whereas Panzura is Linux based. I have tested that file locking does work with Office docs such as Word and Excel as referenced here (https://docs.microsoft.com/en-us/rest/api/storageservices/managing-file-locks), however it does not work with AutoCAD, and this makes it a deal breaker for us.