Contact Us  |  Blog  |  Account  |  Support  |  DEMO

Business Continuity | Solution Whiteboard

What if your employees never had to stop working because of outages, disasters, or even time zone differences? What if everyone everywhere always had access to the files they need? Nasuni keeps your business running no matter what. In this installment of our Solution Whiteboard Series, Nasuni Founder and CTO, Andres Rodriguez explains what business continuity looks like in a Nasuni environment. 

Video Transcript

One of the things that is really hard to do with traditional infrastructure is to deploy a business continuity strategy that would allow you to have a failure on one side and immediately be able to recover your applications access to the end users from a secondary side. This is something that typically involves a lot of cost, set up, ongoing testing. One of the major use cases for cloud-native file systems is to leverage their ability to synchronize multiple access points to deliver very easy, ongoing business continuity. Here is how it works. A cloud native file system essentially lives outside of your data center. It has a full version stream of everything that’s happening in the file systems and what it can do that is different is you can actually synchronize multiple access points to the file system in different locations and make this active-active synchronized. That is, without any conflicts you can actually have file changes that are happening here where the users you know, they may be accessing through CIFS and the users are sitting right here. Any file changes that happen in this location are going to be synchronized back to the cloud file system and then back out to this location. In a business continuity scenario, what we want to do is we want to front these two appliances with a DFS layer or any other kind of load balancing redirection technology and make it so that this is the primary for these users and if there is any failure here the access will automatically shift to the secondary appliance. This can happen in a seamless manner automatically and when this side is back online the users can be redirected here and all the changes will flow back in the opposite direction. Of course, there’s some degradation in access time while the users are coming around to the secondary side, but it’s still very easy and very simple to run this and to make sure it’s always working because it’s always working. It’s not just working during a failure.