In the following demonstration, you’ll see how Nasuni’s global file locking works using the Nasuni Service and why it’s unlike anything else on the market.
In the following demonstration, you’ll see how global file locking works using the Nasuni service, and why it’s unlike anything else on the market. Setting the stage for this short demo, we have two Windows clients, both running Windows 2008, each representing a different office location. For purposes of this demo, we’ll call the machine on the left New York, and on the right side, London.
To show you how global file locking works within the Nasuni service, we’re going to create a Microsoft Word document in our New York office, and then attempt to edit it in London. You’ll notice the different IP addresses, as these are different shares, and different Nasuni filers. And here we go.
On the left screen, we have the New York office, where we will create a Word doc. On the right, we have London, where we will attempt to edit that document. Let’s start by creating a new Word document and adding some text. We’ll now save the newly-created document to our local New York office share. You’ll notice the IP address is 10.1.3.191. We’ll name the file demo. The file has now been saved locally.
Moving over to our London office, the file will now show up on their local share. You’ll notice the IP address is 10.1.3.2. Let’s see what happens if someone in London attempts to edit the file. A dialogue box pops up that says demo.doc is being locked for editing by test user one. The filer’s global locking capability will give the user in London the option the file as a read-only doc, create a local copy and merge changes later, or receive a notification when the original is available. We’ll choose to receive a notification when the original copy is available. This will open a read-only version in our London office.
Back to New York. We’ll make some new edits to this document, and hit save. After the file is saved, we’ll close it. In seconds, the file lock is released, and a notification comes up in the London office telling the user that demo.doc is available for editing. This cloud-based locking is all happening in the Nasuni service, and is not dependent on any one specific filer device. We’ll choose to open the document for editing. The read-only status has now changed to read right, and the recent changes made in New York also appear in London.
Now, we’ll make some changes to the doc in London, and try opening it in New York. You can see that a new lock has been put in place by the London user, and the standard file and use dialogue comes up.
Global file locking with Nasuni is fast, reliable, and highly-scalable. And more importantly, there is no tedious conflict resolution, and never a change to end user behavior.
Now, let’s take a moment to go over how Nasuni’s cloud-based file locking differs from a device-centric approach, where a single node is utilized as a lock manager. In the device-centric model, if a single lock manager node fails, all of the locks will be affected. The lock may not propagate, or the file could remain in a locked state. This results in file conflicts, and possibly lost or corrupted files. Nasuni’s service-centric global file locking happens in the cloud, at cloud scale, ensuring there is never a single point of failure for lock management.
Thanks for spending a few minutes with us learning about Nasuni’s global file locking technology. If you’d like more information about how the Nasuni service fits into your storage strategy, please visit our website.