Distributed File Locking
Panzura CloudFS™ features distributed file and byte-range locking that make it possible for enterprise users to work together in real-time as if they are in the same room, even if they are a world apart, without creating multiple versions of the same file.
Modern, global enterprises need to give users consistent, fast access to shared file data across sites. Typically, they either centralize their data in one location and rely on increased bandwidth, expensive network connections, and WAN optimization to try to make access fast and consistent, or they replicate data between sites. Both approaches have drawbacks, and neither solves the problem.
Centralization Means Reduced Speed
Performance for users at headquarters is fast, but users in other offices waste time waiting for files to open over the network. The result is project delays and lost productivity.
Replication Means File Versions
Performance is good at all offices since the data is local, but multiple versions of files have to be merged later. Data corruption issues are inevitable with this approach.
Panzura Solves Both Speed and Replication
Panzura’s global namespace technology allows files to be stored in the cloud as a single authoritative data source, while leveraging intelligent caching on local filers provides a local data center performance in all locations. Our distributed file locking technology means files are always locked for editing within your global cloud file system, regardless of the location they are accessed from.
Distributed File Locking
With Panzura CloudFS, as soon as a user opens a file in your cloud network, it’s locked for editing. If another user tries to open it, they’re notified that the file is already in use and are given the option to open a read-only copy, or to be notified when the file is available for editing. As a result, the second user cannot overwrite or change the original file; they can only create a copy of it.
Many modern applications that use large, complex files support byte-range locking. This is because byte-range locking offers a more granular approach to file locking. Instead of locking an entire file, byte-range locking only locks the relevant elements of a file that are in use. Multiple users can then collaborate on a single file, at the same time, without overwriting each other’s work or having to merge edits later.
Panzura fully supports byte-range locking in modern enterprise applications such as AutoDesk Revit and AutoCAD, Tekla Structures, Bentley Microstation, and Microsoft Office.
Our Distributed File Locking is Built on 5 Operating Principles:
Data Integrity Above All Else
The locking mechanism and other file system features are built to prioritize data integrity for the authoritative version of the file stored in the cloud.
Immediately Consistent Lock Data
To support data integrity, the locking metadata is updated immediately across the Global Cloud File System of all Panzura Filers.
Every File Has an Origin
The Freedom Filer that originally created the file maintains authority and ownership of that file. This node can assign temporary ownership to another Freedom Filer.
One Data Owner at a Time
A sub-file or file can only “belong” to one Freedom Filer at a time — the Data Owner. The Data Owner manages the authoritative copy for that data instance and normally acts as the Authoritative Write Node for that data. Any writes have to be committed through the Data Owner.
Data Asymmetry Resolution (DAR)
Any differences between remote sets of files are resolved quickly and efficiently by the Global Cloud File System. Changed blocks are transported back to the Data Owner.