Nasuni Reviews

We have multiple physical locations and we had to find an alternative data repository so that we could transition from some legacy technology like Microsoft StorSimple. We needed a cloud-native solution that would be more cost-effective than some of the other vendors out there. We ended up going with Nasuni primarily for file server access for three locations within Australia.

Nasuni is helping us replace multiple data silos and toolsets with a single global file system. We are still in the transition stage for some of our locations. We're doing away with the Microsoft StorSimple services, which is being retired at the end of the year. We have an HPE Unity SAN at one of our locations, and because that used to store all the data, we have had to have backup technology to replicate it. We're doing away with both of them and simplifying our infrastructure in that location to accommodate just a small caching appliance. And there's an FTP capability that we're looking to investigate for some of our infrastructure components.

Also, we have reduced the IT risk in our recovery point objectives and recovery time objectives. In the event of a disaster, we're able to bring up the infrastructure in a different location very quickly. In addition, we can have access to this data in a site-survivability mode in our manufacturing area. That means that for a period of time, the data that's cached on those appliances will happily be used by that office, should the network become isolated from the internet.

Another benefit is that, compared to what we had before, from a dashboarding perspective, we get really good visibility within the Nasuni console. We also have much better assurances around the backups and the mechanisms assuring that the data is actually being securely stored, based on our rules, with various tools and backup solutions. There were many different places where we used to get that information and that just wasn't efficient.

One of our guiding principles, when it comes to architecture, is to ensure that we have immutable backups of all of our data. Historically, we were able to do that for everything except for our file servers. We still leveraged legacy capabilities for that. By moving to Nasuni, we were able to ensure that the backups are immutable and retained for a period of time without being impacted. That gives us assurance that, in the event of a ransomware attack, we're able not only to restore the data or make it accessible, but we're also able to provide a different mechanism for users to access the data in a disaster recovery scenario. That can be done by using the web interface rather than having to establish network connectivity.

Nasuni has also helped to eliminate on-premises infrastructure. We're simplifying the infrastructure we deploy and, as part of that process, we're able to then repurpose it. For example, we currently have SAN storage attached to the network and we had a couple of NAS appliances. We consolidated all of that into a virtualization stack that only has to store a minimal amount of caching data. That saves us hours a week from managing the backups and ensuring that they work. When we do restore testing, we only have to test a finite amount of data because it's one system working for many different areas. It's considerably easier. There was a little bit of a learning curve to understand how the new technology works, but the implementer helped us with that.

It has also decreased capital costs in the sense that we don't have to renew the purchasing of additional specific hardware for it. The last SAN storage appliance that we purchased cost $180,000 four and a half years ago, and it is coming up for retirement and decommissioning. Nasuni is not a complete replacement, as we'll be replacing that SAN with some virtualization infrastructure, but that will be co-shared and used by a number of different systems and applications. We're taking away a storage appliance, but adding more capacity and more processing power for use with more systems.

We effectively subscribe to the storage where that is saved. As a result, from a cash flow perspective, we're clearer. We're not having a large capital investment for the storage appliance. And we also have the assurance that it is considerably more redundant than what we used previously.

The disaster recovery capabilities are very easy because their virtual appliances are just like OVFs or images. You put in a code and it collects all the configuration from the cloud and then builds up the cache. But that doesn't preclude the device from easily being restored or recovered at short notice. It also means, from a security-patching perspective, that we don't have to add any additional processes like managing a Windows Server or having agents on it. We can simply rebuild those or upgrade those agents.

The storage that we're deploying it to is in Azure, but one of the key features of Nasuni is the fact that we can actually change the location of that storage when it becomes cost-prohibited to have it in Azure, and we can find equally reliable but cost-effective places. A good example would be Wasabi storage services. They don't have regions in Australia, but should they get regions in Australia, they are considerably cheaper than what Azure, AWS, and GCP offer. We have that flexibility.

Nasuni also provides file storage capacity anywhere it's needed on-demand and without any limits. What we've found is that a lot of our storage is dormant and not actively used. Nasuni gives us really good insights into the usage of the data and enables us to store that data in an immutable secured location. The flexibility is there and the level of data that we can send to it is exceptionally high. The importance of this feature is about a six out of 10 for us. That's because our volume of data is actually decreasing year-on-year, specifically in those types of data repositories. We are exponentially growing on data stored in cloud services, like Dropbox, OneDrive, SharePoint, and Teams, but that's a different technology stack.

Migration from existing systems, specifically StorSimple, could be improved, but that solution will be end-of-life by the end of the year. 

Also, the documentation could be more accessible.

It's a pretty good product, overall. It's hard to find something specific that they really have to focus on.

I have been using Nasuni for a couple of months.

So far, we've had no problems with its stability.

We're assessing whether we're going to deploy it throughout Asia as well. But strategically, we're moving away from this type of storage. We're looking to leverage more cloud-based collaborative storage. The primary reason is that we don't have the necessary use cases for really large storage connectivity, like CAD or design drawings. Our usage of Nasuni will actually become lower and lower over time as we transition business processes.

Their tech support is quite busy at the moment with everyone trying to outsource storage. We can give them a little bit of leniency on that.

Positive

We had a risk around an end-of-life technology and we brought in Nasuni and we transitioned to it within a week and a half.

The initial setup was straightforward. The biggest thing that we had to focus on was transitioning our existing snapshot backups. They definitely had some guidance on how to do that and that helped. The technology side was straightforward. Some of the business decisions that we had to make were more complex. For example, how comfortable were we in keeping some of the data that we had in our old system and getting rid of some of the other data?

Compared to what we used to have, this solution is significantly simpler. The deployment of the caching appliances is very easy, as is redeploying them. From an infrastructure perspective, that's quite straightforward. We don't have the hardware appliances, but I believe they are equally easy to manage.

Our deployment is a combination. In one location it's on-premises, but it's in a virtualized environment. We are deploying components in our core data center, which is a co-lo with our virtualization infrastructure.

While a 360-degree view is going to be a stretch, it does allow us to have all of our file repositories centrally managed in one administrative console. It doesn't cater to data classifications and data loss prevention, but from an object storage point of view and a management perspective, it definitely works.

The use case specifically is to allow our engineering staff in different offices to be able to work collaboratively on the same projects at the same time. Also, another important feature for us is the ability to recover or restore data from any point in time in its history.

We have Nasuni Filers deployed at each of our offices in the US and another location in India. Nasuni is used by our engineering staff and where production engineering data is stored.

The cloud is used for synchronization from site to site as well as for backup and storing all our snapshot historical data.

We use different cloud providers for different things. Currently, hard Nasuni data is in AWS.

We use it for VDI. VDI is the direction that we are going throughout the company for consistency and user experience for DR and DC capabilities. Having the Nasuni Filers be a central element supporting the VDI solution has enabled us to have all our engineers work collaboratively in a very tightly integrated total solution.

It is very rare that we need to make significant changes to the Nasuni infrastructure to support organizational changes. On a day-to-day basis, there are new projects added across various design teams in the company. Those can be set up in seconds in Nasuni. It is just very easy to work with it. In essence, setting up the basic file structures just looks like another volume that has been shared on the network. Through the console, we can configure Global File Lock permissions for how those files can be accessed from site to site.

One of its most valuable features would be the Global File Lock capability, which is what enables our engineers to be able to work on projects collaboratively from site to site.

Nasuni offers us a single platform with a 360-degree view of our file data, which is definitely important to us. It simplifies IT operations tremendously. Because it is taking continuous snapshots, it eliminates a lot of work that was previously done when trying to manage backing up and restoring data files.

It is far less labor intensive than our previous processes. There is a console interface that is used for managing all the data repositories, what is in the cache of each appliance, the Global File Lock parameters and settings, the ability to recover files, etc. The single pane of glass interface manages all those capabilities. Things can be done in minutes through the Nasuni Management Console, which previously would have been a more labor-intensive effort with more manual processes.

Nasuni enables us to provide file storage capacity anywhere it is needed, on-demand, and without limits. We have it deployed on Nasuni appliances at our offices, but we also have the ability to create virtual Nasuni Filers that potentially could be deployed anywhere in our infrastructure.

Nasuni provides Continuous File Versioning down to the granularity of the snapshots, which occur about every 15 minutes. If there was a ransomware or other disaster type of event, only the data in the cache on the local appliance would be affected. The entire snapshot history of every file is backed up in the cloud. We can, on a file-by-file, directory-by-directory, or volume basis, recover any or all files from that snapshot history back into the local appliance. The only impact would be the time to copy the data back from the cloud snapshot back into the local appliance.

Because these snapshots occur so frequently, we can recover data to a point very shortly before the time a person wants to recover that data, e.g., within 15 minutes of when whatever happened. If somebody deletes a file or accidentally moves/loses it, then we are able to recover it within 15 minutes of that point in time. Very little data, if any, is lost with this type of operation. This has greatly relieved any concerns about IT backups and restores to the point where it is a very minimal concern. 

It frees up IT staff to work on other initiatives, because these are automated processes that occur in the background and require minimal attention, if any at all, from IT staff.

One area where Nasuni has made huge strides over the last year and a half is the time required to synchronize data from site to site. This has gone down quite a lot, but we always would like it to occur faster. 

I would like to see Nasuni provide the ability to mirror a Nasuni appliance from one site to another. They could maybe have a standby appliance that is mirrored in a different location for disaster recovery purposes. We can recover if data and a Filer are lost because of a possible ransomware event, but even that takes time to recover. If we had the ability to have a mirrored appliance, we could flip over to that mirrored device and resume instantly rather than repopulate the local appliance with data from the snapshot history in the cloud. This is another feature that we would really like to see, if possible.

I would like the ability to roll back to a prior version of the firmware, e.g., if you had a problem when you were upgrading to a newer version. They do not have this capability. This is less of a concern than it used to be. It is a much more mature product, but this would always be a very nice feature to have.

We have been using it longer than I have been in the IT management role here. I can estimate it at eight or nine years in total.

For the last several years, it has been very stable. There have been no issues.

Deployment and maintenance need a very tiny fraction of an FTE. With everything that we are doing with the appliance, it is probably a couple of hours a week.

Scalability is seemingly limitless in terms of the number of places where appliances could be deployed as well as the amount of data that can be handled. The only limitation is the amount of cache memory that is on the local appliance. So, if you needed to keep a very large amount of current data in the local cache memory, you might need to deploy multiple appliances at a site. However, it basically uses a first-in, first-out methodology for what data is kept in the cache. Any data that has been accessed or modified recently is in the cache. If it is not in the cache, it will pull it into the appliance from the snapshot history and replace the data that was accessed the longest time ago which is remaining in the local cache. However, any data can be brought into the local cache to the appliance. Therefore, we have been able to completely work within the bounds of an appliance at a given site.

All of our engineering staff are using it: designers, engineers, project managers, building information modeling (BIM) staff, and technicians. That is around 240 people in our firm.

It is being about as extensive used as it can get. It is used across all our engineering staff, covering all active project-related files. That is the extent to which we tend to deploy it. There are other file systems being used for other purposes, but we don't have the same kind of needs that would warrant using a Nasuni appliance for something like that, like we do for this. So, the Nasuni infrastructure is used really for the most business-critical applications.

Previously, the company used traditional file storage systems and big tape backup systems.

Nasuni replaced multiple older file systems and manual tape backup solutions. This has been absolutely business-critical because of the type of data that is stored on there, e.g., all our engineering client project information is stored there. Also, it is extremely resilient. It allows us to recover files if there was ever either accidental or malicious loss of data. For loss of data of any type, we have the ability to recover that data from the entire snapshot history on any file. So, Nasuni is important for day-to-day activities as well as providing disaster recovery capability on any data stored on it.

Before having the solution, it just would not have been possible to have staff in multiple offices be able to work collaboratively in some of these design applications at the same time. So, Nasuni was critical to enabling that capability, which increased productivity, allowing us to share resources more effectively across offices. Also, prior to having the Nasuni solution, if engineers wished to restore data to a prior point in time, we were limited by the capabilities of our previous tape backup solutions. This means they were not as granular as Nasuni. Our granularity is down to about 15-minute increments in time, where it might have been daily with the old tape backup solution. Nasuni is quicker when recovering data from any point in time than was ever possible with prior tape backup solutions.

Nasuni has replaced other on-premise infrastructure. It has replaced traditional file storage and tape backup solutions with a simple 2U appliance that has storage integrated into it and is connected back to the cloud for all the snapshot data.

We did have assistance from Nasuni to get the devices configured initially. It wasn't an enormously complex process. 

We did have Nasuni Professional Services help with the initial setup.

Nasuni certainly has reduced labor costs associated with managing all the data and how we manage client project data. It has greatly reduced the labor efforts and costs associated with that. It has also turned out to be a very reliable solution. As site-to-site sync performances have improved, that has enhanced the productivity for all our engineers as well.

Before Nasuni, the time investment was critical and a daily activity. It took a fair bit of time to prepare, load tapes, catalogue items, and run backups every day. Now, with Nasuni, the only time spent is when we have to customize the Global File Lock permissions for certain folders (for the engineers) so the Global File Lock mechanisms work correctly. This is a one-time activity that occurs when a project is set up and completed in minutes.

Nasuni has decreased capital costs because you don’t need to buy as much excess capacity. The CapEx cost is definitely lower with Nasuni. It is only when we either need to upgrade an appliance in an office or if we need to purchase appliances for new offices that there are CapEx costs. The rest of it is an OpEx cost.

It has reduced capital costs by over 80%.

There are annual costs that we pay for maintaining all of the snapshot history in the cloud. That is the primary cost that we pay. We occasionally buy newer Nasuni appliances or deploy them to new offices when the need occurs. That capital equipment expenses is less than the cost of buying new file storage systems. For the most part, you are trading a CapEx cost of storage equipment for an OpEx cost for management of all the snapshot data in the cloud. There are CapEx and OpEx elements to both solutions: 

• With the old school solution, you have an OpEx expense for tapes, which is relatively small. With Nasuni, you have an OpEX cost for the data in the cloud, which is larger. 
• With the old school solution, you have CapEx costs for storage equipment, which are large. With Nasuni, you have a CapEx expense when you need to purchase new appliances for offices, which is relatively small. 

It is kind of a trade off with similar costs either way.

The snapshot history backed up in the cloud is an annual OpEX expense. Occasionally we have to bump it up because the amount of storage required for all our snapshot history increases over time, but the infrastructure purchasing and support requirements are definitely simpler.

We do hardware refreshes on Nasuni appliances. So, that is not a buy it once and you're done forever kind of thing. The majority of the cost with the Nasuni is an OpEx cost for storage of all the snapshot history.

I think the pricing on the appliances is completely reasonable and fair. I have had no issues with it. 

Keep in mind that Nasuni allows their clients to choose what cloud platform all the snapchat history is saved on. Depending on the cloud platforms that your company uses, or if there are standards on such things, there may be some benefits to looking at alternative cloud providers for storing the snapshot history, because there may be some savings to be had there. At the same time, because they have that flexibility and support several different cloud platform vendors, if your company is standardized on a particular cloud vendor, then odds are Nasuni is already supported in it.

The costs are the standard licensing fees and subscription for the total size of the data repository (for the snapshot history in the cloud).

We looked at Panzura too.

The cloud piece is almost transparent to the user. Because you are interacting through the Nasuni Management Console, you are not really working directly with that cloud provider solution to access files. You could, if you wish, but you can do everything that you need to do directly through the Nasuni Management Console. The cloud happens to be the place where the data is stored and you don't necessarily need to interact with it directly.

Keep in mind the amount of data that you need to keep in your cache. So, sizing your appliance for the local cache storage needs to meet your day-to-day needs, but your actual needs are probably less than what you think they might be. If you had the ability to store 30-days worth of data in the local cache appliance, you are probably in pretty good shape. I definitely would try to understand exactly what the needs of your business are. If you have site-to-site replication needs, carefully consider the capabilities of any particular solution to make sure that the vendors that you are considering can deliver on that as well as how easy it is to work with those vendors for restoring data, if you ever needed to do that.

We haven't tried going back to a more traditional solution. This solution has done a fantastic job of meeting all our needs. Overall, we are just very happy with Nasuni.

I would rate Nasuni as nine out of 10, but I am a tough grader. It is hard to get a 10.

We needed a solution that would allow our 12 offices to collaborate from one central location of active business data that is continuously synchronized and backed up. This is the problem that Nasuni solved for us.

Our environment includes Nasuni's cloud-based file storage called UniFS, and at each site, we have a filer on-premise. Our normal SAN/NAS refresh cycle at each office location was 3 to 5 years. This IT work involved a lot of time, effort, and cost involving research, planning, and deployment of the properly sized SAN/NAS. With Nasuni, this hardware refresh cycle has literally stopped. Our capacity now scales on-demand.

Prior to Nasuni, each office had its own on-premises file server and there was no real collaboration on a single set of data. We had data silos operating independently at each location and when we would win a project, it was very difficult to collaborate between offices. Nasuni came in and looked at all our offices and data within our workflows and made the requisite recommendations. In the end, all of our active business data was consolidated and synchronized into one universal ‘global’ drive that was automatically backed up every 15 minutes and accessible by all staff in all offices.

With Nasuni, we have been able to replace multiple data silos and toolsets with a single global file system, which is important to us because we have been able to consolidate several different products and solutions. Prior to Nasuni, the normal mode of operations in IT was to employ several products to use with critical business data. For example, we have to store it, back it up, think about disaster recovery, and think about how different employees collaborate on the same data at the same time. Each of these problems required different products.

Nasuni solves your storage, backup, disaster recovery, and file sync/collaboration needs in one product/solution.

Thankfully, we have not had to use it for a ransomware attack or disaster situation. But the risk of data loss due to a ransomware attack is significantly mitigated knowing we can restore our data to within 15 minutes of the last Nasuni ‘snapshot’. We also use Nasuni on a weekly basis for simple file restores. With Nasuni, in two clicks you can restore a file. 

Prior to Nasuni, we had a completely separate software package that we purchased for data backups. This is not required any longer. As such, our IT environment is simpler and more cost-effective.

We don't use Nasuni exclusively for VDI but we do have VDI components. This is very important to us because we've been using VMware for almost 20 years.

With regard to the simplicity of management, the Nasuni Management Console makes everything very simple. Related to that is the support that we received during our implementation, as well as the ongoing support that we get whenever we have any questions about configuration or otherwise.

Nasuni has helped to simplify infrastructure purchasing and support requirements, starting with the fact that we no longer do our regular SAN refresh every three to five years. Also, we are now dealing with one vendor, rather than multiple vendors for our storage solution.

Anybody that knows about storage products will understand how they just fill up because users create more data than you have a plan for. A storage upgrade is a big IT project and we haven't had to do one for almost three years. Having the benefit of being able to forgo one of these projects saves us hundreds of hours each time.

When compared to having to do SAN refreshes, Nasuni contributes positively to business agility. When you have to plan for an IT update project, it requires time and effort. With Nasuni in place, that need goes away because the technology automatically backs up the data, synchronizes it, and maintains version control for disaster recovery. From that perspective, the business is much more agile.

One of the most valuable features is scalability. As time goes on and we begin to run out of disk space, and we start planning for deployments and upgrades, Nasuni really helps. One of the things that we love about this product in IT is that it looks at your data and identifies what is active, or what is being worked on. We can set a threshold in terms of time where, for example, if the data has not been opened or touched for at least a year then it is automatically backed up to the cloud. By doing that, it's constantly keeping your file servers lean, which means that you don't have to regularly buy new storage upgrades.

Because we don't have to continue to buy storage as we did before, Nasuni has partially helped to eliminate our on-premises infrastructure. In this regard, it has reduced our SAN refresh costs. It is difficult to estimate how much we have saved because each office had its own SAN and storage requirements prior to Nasuni, and I would have to look into how much we paid for that infrastructure. Easily, we have saved six figures.

Aside from costs, Nasuni has reduced the amount of effort that we spend on our storage solution. The IT works and planning that's involved whenever you're doing a storage upgrade or a SAN refresh is significant. It becomes a month-long project. Having Nasuni manage active data versus inactive data has meant that we haven't bought a SAN since we implemented Nasuni in 2018.

Some of the other valuable features are collaboration and disaster recovery.

Nasuni gives us a single platform with a 360-degree view of our file data, which is very important to us. It is called the Nasuni Management Console and we have everything that we need to look at in a single pane of glass. From an IT administration standpoint, there's nothing worse than having to hop onto different toolsets or different solutions to manage different things. With regards to data management, specifically, we work through the Nasuni Management Console and everything is managed from there.

The speed at which new files are created is something that could be improved. For example, if you create a new file in another country, I won't see it for between 10 and 15 minutes. The length of time that it takes depends on the speed of the internet. If it were to drop from 15 minutes to two minutes, that would be fantastic. However, I understand that there are a lot of variables involved. As such, it's probably not just Nasuni but also the speed of the internet.

We have been using Nasuni since November 2018.

Stability-wise, it has been top-notch. We haven't had any issues whatsoever. When we first implemented it, we had the occasional questions about the length of time required to create a new file. We thought that it might be quicker.

Nasuni is used daily. Literally, all of our business-critical data resides on it, so the availability has to be there 24/7/365.

Scaling is just a matter of contacting Nasuni and telling them that we need more storage. After that, they allocate it. We're using Azure, whereas some people use Amazon AWS or Google. It doesn’t matter to Nasuni which ‘backend’ you use.

We have approximately 450 users and the roles range from engineers to project managers, to administration, marketing, IT, and finance. We don't have any plans to increase usage. As the company grows, it doesn't mean that we're necessarily going to be doing anything different. We may just have to buy more Nasuni storage.

We have a small IT team of approximately four people that was responsible for the deployment and takes care of the maintenance. There is not much maintenance that needs to be done. It involves system updates and going into the Nasuni Management Console to check log files.

We received helpful support during our implementation, as well as ongoing support whenever we have questions. We also have access to Nasuni’s senior leadership team, which is fantastic!

We did not use another product prior to implementing Nasuni.

The initial setup is pretty straightforward. Nasuni comes in and they look at your data. They do an assessment and then they give you a report that estimates your sizing based on the total data that you have, as well as the amount of data that is actively being worked on at any given point in time. For example, you may have five terabytes of data but there is only 1TB that is being actively used.

With assistance from Nasuni in classifying our data as active versus inactive, we were able to then size a proper solution and purchase the right amount of storage that we need both in the cloud and on-premises.

The implementation strategy was just a matter of sizing the environment and then copying data from a traditional file server to the Nasuni file server. It took about a month for us to complete. This included sizing the environment for each location, making sure each one had a Nasuni filter, then communicating to staff that we were going to be moving data from one location to another.

The moving of data is something that we did on a weekend and the staff were told that when they came back to work on Monday, they would automatically be pointing to a different location for their data.

Nasuni assisted us with the implementation. We did not rely on a third party.

Not having to purchase storage each year has helped to reduce our capital costs. We no longer have to do our SAN refresh cycles.

We analyzed our ROI when we first purchased the solution and although I can't share the actual costs, I can say that the primary savings are in the time and effort involved to do the SAN refreshes. This is not to mention buying the SAN in the first place. A safe estimate would be savings in the six-figure range.

The cost of licensing is negotiated and billed annually per terabyte. Different clients have different pricing, depending on their agreements.

In general, the pricing is straightforward and it's an all-inclusive price with no surprises. There is no charge for additional features, add-ons, or otherwise. The fact that it's one price for all of the technology is something else that we like a lot about this product.

Prior to implementing Nasuni, we evaluated Panzura. It is the direct competitor in the market. In our opinion, the Nasuni technology was better. The cost for the product and the cost to implement was significantly less with Nasuni, although the primary reason that we chose it was the technology.

When we saw the demo, we were more impressed with what we saw with Nasuni as compared to Panzura. We were also much more impressed with Nasuni’s representation in terms of how they communicated with us promptly and honestly.

When it comes to configuring Nasuni to support organizational changes, the technology is very easy to implement. What's more difficult in any organization is communicating and implementing workflow changes required due to the new data structure. Human nature dictates that we are naturally resistant to change, especially in an organization that has workflows in place for a long time. As such, be sure to involve as many key stakeholders in your company as possible in order to communicate the many benefits of the project. With proper buy-in, the chances of any IT project succeeding are greatly increased.

Today, all of our employees realize that we now have what's called a "global drive", and this is where all of the data can be found. What used to frustrate people, understandably, is that if we're collaborating, they would go to their local office's file server and it wouldn't be there. Rather than stored locally, a file might be on the "British Columbia" server, or instead on the "Alberta" server. Consolidating all of the data and then communicating to staff that there's only ever now one location where that data or that file can be found, really simplifies finding and retrieving the file that people are looking for. Data structure simplification through consolidation and classification goes a very long way to removing friction for the end user when trying to find a file.

I have recommended Nasuni to many colleagues, and I point out that if they have any sort of multi-site collaboration problem, or if they're thinking of disaster recovery, business continuity, or backup solutions, or if they're tired of refreshing their SAN, then Nasuni is an excellent choice.

My advice for anybody who is implementing Nasuni is to take your time at doing the assessment and classifying your data. This is something that Nasuni helps with. Then, once you have a good understanding of the data classification, take time to get an understanding of everybody's workflow and what they expect things will be like post-change. If this is done correctly and you take your time then the implementation will go a lot smoother. If instead you just rip off the band-aid and do something, and then people wake up Monday and there are all sorts of changes, chaos is imminent.

I would rate this solution a ten out of ten.

We use Nasuni to provide storage at various locations. It is for office-type files that they would use for day-to-day office work, such as spreadsheets. None of it is critical data.

Each group at each site has its own data store. For example, HR has its own, and finance has its own. All of these different groups at different locations use this data, and they use these filers to store it.

The Nasuni filers are on-site, and we have virtual edge appliances on ESX servers at about 35 sites globally. The data stored at these sites is then fed up into Azure and we have all of our data stored there.

The OR and DR capabilities have been a very big help for us. Previously, with the solutions we had, it would have taken weeks sometimes to get things fixed and back up and running for people. Now, it only takes a matter of minutes.

It used to be a lot of trouble to bring data back up and a lot of the time, it was read-only, so the people couldn't use it very well. Now, with Nasuni, we're able to pretty much keep their experience seamless, no matter how much trouble the hardware is in at the site.

The Nasuni filers are easy to manage, although the process is similar to what we had before. We have a report that comes out three times a day that gives us the amount of data that's in the queue to be uploaded to Azure on each individual filer. We keep track of that to make sure nothing is getting out of hand. It also tells us if the filer has been restarted and how long ago that happened. It gives us a quick view of everything and how much total we're using within Nasuni. This report is something we created on our own to keep track of things.

If a user deletes a file or a file becomes corrupted, it's easy for them to get it restored. There is very little chance that the data is going to be done. We've had a few people delete things, or they have become corrupted, and we were able to get that file back to them in the states that it was in about five minutes before they had a problem. We were able to do this without any issues. Overall, the continuous file versioning is really helpful.

The biggest and most impressive thing for us is the operational recovery (OR) and disaster recovery (DR) capabilities that Nasuni has. If a filer goes down, or an ESX server goes down, then we can quickly recover. For example, we lost a controller the other day and all of the drives were corrupted. We were able to quickly repoint all of the users to a backup filer that we have at our data center, they were back up and running within minutes, and they still have read-write capabilities. Once that ESX server was fixed, we were able to repoint everything back to it in a matter of minutes. People were then again using their local filer to connect.

Nasuni provides continuous file versioning and we take snapshots on a regular basis. Right now, we have them stored forever, but we're trying to reign that in a little bit and keep them only for a period of time. Certainly, at this point, we have a lot of file versions.

We have not had a problem with ransomware but if we did, we would be able to restore the data pretty quickly by going back to an older version of the file before the ransomware took over. It is a similar process to the DR, although a little bit different. For us, OR and DR are pretty much the same thing. We haven't had any disasters that we've had to recover from but we've had three or four hardware failures a year that we've had to deal with. The continuous file versioning has helped to fix these problems pretty quickly.

Continuous file versioning also makes it easier for our operations group. The support team is able to restore files quickly, 24/7, and it is less work for them. They have more time to focus on other problems. The end-user also has access to shadow copies through Windows, and they've used that extensively at the sites.

Nasuni has helped to eliminate our on-premises infrastructure. When we moved to Nasuni, we moved to Azure. Before that, we had a large SAN storage that we were using, and we were able to get rid of it. That was a big difference for us.

We were definitely able to save some money because we've eliminated those expensive SAN disks completely. There were some servers at our old data center that we were able to get rid of, as well. There are some new expenses with Azure because we have to pay for the space taken by the snapshots, which is why we're going to put a retention limit in place. Overall, I don't have an exact number but we were able to save money.

Nasuni is transparent to our end-users. We have it all set up as a file server through Microsoft DFS. If you were to ask one of our end-users how they like Nasuni, they would have no idea what you're talking about.

One issue that we have is related to copying data out of Nasuni. We just sold a site and it was split into two pieces. One part of it was sold to another company and we kept the other part. At the site, they have a Nasuni filer with about eight terabytes of data. Now, we have to split that data and the problem stems from the fact that the other company doesn't have Nasuni.

This means that we have to copy all of that data back to the site and into a format that they can use, which is probably just a Windows file server, and then we have to split it somehow. I'm not really sure that there's an easy way to do that. It's going to take us a little bit longer to separate this other location, and we're having to invent things as we go along.  

In these areas, it's not as simple as it could be, but it doesn't happen very often. As such, we haven't had to worry about it too often. Although it's not affecting us too much at this point, if there's a problem such that we have trouble getting data out of Nasuni, then that could be an issue. However, for the time being, it seems fine.

When we have to rebuild a filer or put a new one at a site, one of the things that I would like to be able to do is just repoint the data from Azure to it. As it is now, you need to copy it using a method like Robocopy. To me, this seems counterintuitive or like we're going backward a little bit. I would like to see a way to be able to switch them around without any problem. That said, I'm not sure if it would then cause other issues because of how Nasuni works, so it may not be possible.

We started using Nasuni in 2018 and it's been running ever since.

Up until about a week ago, the stability has been rock solid. We've actually had a few issues after upgrading to version 9.3 that we're trying to deal with. We have a couple of sites that we're still not sure if Nasuni is the problem, or if it's VMware ESX, and we're working on that. At this point, we're not thinking about rolling back because of all of our sites, only two of them have problems. As such, we think that something else may be going on.

For the most part, it's been extremely stable, with no issues whatsoever. With Nasuni, there has been very little downtime, if any. Most of the sites have never gone down and with the sites that have, there's usually some other external problem.

Overall, it's been very stable for us.

We are limited to the amount of space that we have purchased from Nasuni. If we get close to running out then we just buy more. We still have to pay for the storage within Azure, so we're trying to make sure that it doesn't get out of control. In general, we don't need to add any on demand.

Scalability is not a problem and we can add as many servers and as many filers as we need to, which is really nice. For example, instead of buying tape drives and using that type of backup system, we decided to take a few sites where we have some smaller servers and we use Nasuni to back them up. We use a separate filer to back up all of that data. It's been nice in that way, where we've been able to do things with it that we hadn't originally thought of.

If it should happen that we make a large acquisition, and we bought 10 sites, we could easily put in 10 more filers. It wouldn't be a problem.

Amongst our 35 sites, we have between 10,000 and 12,000 users. A lot of them are office-type people such as those from HR and finance. All of us, including administrators and developers, use it for this kind of thing. The developers wouldn't store code on these because that's not what it's used for. Our Nasuni environment is specifically for data to help the business run, which isn't critical to producing goods or shipping them or anything like that. That is a completely different system. Anybody who works for the company that needs to access simple office data is going to be going through Nasuni.

We have approximately 210 terabytes stored in Nasuni right now. That continues to grow at perhaps a terabyte or two per month. I don't think we'll be moving it anywhere else at this point. Down the road, we do have a very large file system at our data center that we're considering moving, but it's going to take a lot of time to do that one because it's 400 terabytes and it's a lot of old data that we have to clean up first. But that's pretty much the only area that I would see us doing something.

Later this year, we're going to start refreshing some of the hardware because we're approaching five years on some of the older stuff. As we replace it, we'll do another rollout, but it's not going to be like before. We're just going to put a new server in and put a new filer and connect to the data.

Up until recently, I would have rated the technical support a seven out of ten. We had to open a case in Australia for a problem with one of the Nasuni filers, and I haven't got a response for it yet. We had one of the support people answer a question at about three in the morning, US East Coast time, and he said something to the effect that he would send an email giving an update. After that, we didn't hear back from him until about 25 hours later, which was a little concerning for me.

Part of the problem seems to be that Nasuni currently is not set up to do 24/7 support. They said that they were going to do that, so that was a little disappointing. Typically when we call in a problem, they jump all over it and they get it fixed in no time.

From the perspective of our end-users, the servers function the same way when they're working. We had Windows filers before and now they're Nasuni, so it's basically the same thing to them.

Although we mostly used Microsoft, we did use a backup solution called Double-Take, which is now owned by Carbonite. It did the job but it had a lot of idiosyncrasies that were very difficult to deal with at times. That was the only non-Microsoft thing that we used for the data before Nasuni, and we have since stopped using it.

In the beginning, the setup was kind of complex. We did have help from Nasuni, which was great. They were with us the whole time. We had some growing pains at the beginning, but once we figured out the first three or four sites, we were able to get everything done very quickly and efficiently, with very few problems moving to Nasuni.

When we first started with Nasuni, we had never used it before, and we had never used anything like that. We were used to using Windows servers, and there was a learning curve there to figure out the best way to set up the Nasuni filers. We really had to rely a lot on Nasuni for that. Some of it was trial and error, seeing what worked best as we started rolling it out.

We were replacing a single server that was responsible for doing everything. It was a file server, a domain controller, a print server, and an SCCM distribution point. It was all of these different things and we replaced that with one ESX server, which had multiple guest servers on it, doing all those functions separately. It is much better security-wise and much better operationally.

We started with a very slow implementation. We implemented one site, and then we waited two months before moving to the second site. We tried to start with some of the smaller sites first, with the least amount of data, to get our feet wet. Also, the first site we did was the one that I sit at. The team was all there and it was our site, so we figured we should do our site first. We staggered deployment, so it was not very quick. Then, once we had three or four completed, we did three a week for three months and we were done.

After completing the first site, choosing the next sites had to do with the hardware. We had some old hardware that we repurposed, so we did those sites next. After that, we moved to the sites that necessitated purchasing new hardware. 

From beginning to end, our implementation took a little more than a year. It began in August of 2018 and finished at the end of Q3 in 2019. The time it took was not because of Nasuni. Rather, it revolved around different ordering cycles in our company. Buying the new hardware was what stretched out the deployment time.

I was in charge of the team that did the implementation.

For purchasing and the initial negotiations with Nasuni, we used CDW. We still interact with them when it's time to do renewals, and they are great to deal with. They really help out quite a bit. They were the ones that brought us Nasuni in the first place and suggested that we take a look at it.

We're very happy with CDW. We use them for all of our hardware orders, and a couple of different infrastructure tools. We use them quite extensively.

We had four people responsible for the deployments, with one guy who was in charge of the group as the lead architect. Once it was deployed, we turned it over to our operations group, which is outsourced to TCS. Although they have supported us since then, they come to us if there's anything that's still an issue. We have a couple of guys that still work with Nasuni a little bit, but that's basically how the maintenance is done.

For the most part, there is little maintenance to do. There are situations such as when a controller card goes down, or like the issues we have been having since the upgrade. Otherwise, it's very hands-off and you really don't have to do a lot.

We don't plan on calculating a return on investment with this solution. In the grand scheme of things, it's really not very much money for what we're doing. We spend more money on the hardware, for example.

Our agreement is set up such that we pay annually per terabyte, and we buy a chunk of it at a time. Then if we run out of space, we go back to them and buy another chunk.

We thought about an agreement with a three-year plan, where we would get a small increase every year, but we decided not to take that approach at this time. We go through CDW for these agreements and they help us get all of the quotes together.

In addition to what we pay Nasuni, there is the cost of storage in Azure or whatever cloud service you're using. It can get pretty pricey if you have a lot of snapshots, which is something we've found and we're now trying to scale back on. That's the biggest thing that is extra and you may not think of right at the beginning.

We looked at a few different products that year, and we decided that Nasuni was the best way to go. It has really worked well for us.

One of the products that we looked at was Veeam, the backup software, but it would have been used a little bit differently. We also looked at Backup Exec and a tool from Microsoft. We didn't look at anything that was exactly like Nasuni. We looked at these other things that would create backups of the primary data, which would have stayed at the site. Nasuni was a completely different way of looking at it.

The difference with Nasuni is that rather than having a backup in the cloud, the primary copy of the data is what's in the cloud. For us, it's stored in Azure, whereas with the other tools, the primary copy stays at the site. If you had a major problem, for instance, this issue with the controller card, the problem with these other solutions or the way it was before was that you're down and out at least until you can get the controller card replaced.

Then, once you're back up, you're going to have to copy all of the data back. For that, it would probably need at least a week. Some of these sites have very poor connections. For example, we have a site that's in the Amazon jungle in Brazil and they are notorious for being very slow, yet we've used Nasuni there and it works fine. Some of these other solutions probably wouldn't have worked. In fact, we probably would have had to buy a tape drive and back up the servers that way.

We have a hosted data center where we don't pay for individual items, such as servers. Instead, we pay for a service. The service might include a server or storage, and Nasuni has not eliminated that because we still need our physical servers at the locations. We debated on whether or not to put the filer in Azure for each site, but we decided that it was better to have something local at this point.

For our company, we were a little ahead of the curve. We didn't have internet connections directly from each site, and they all routed through a central internet connection. Because of that, it was difficult to eliminate any hardware at the site. We needed something there physically. But, having the virtual appliance for Nasuni really helps out quite a bit, because then we only have to have one piece of hardware and we can put all of the other servers that we need for infrastructure on the same ESX server. We have five or six different servers that are doing different functions that at one point, would maybe have been three or four different physical servers. Now we've reduced it to one.

We use Microsoft SCOM as a monitoring tool to keep track of all of the filers and make sure that they are running. 

We don't use the Nasuni dashboard because we don't have to. Everything is working the way it is. We do have a management console set up and we do go into that occasionally, but it's not something that's a regular thing that our support people use.

If I had a colleague at another company with concerns about migration to the cloud and Nasuni's performance, I would talk about the fact that the OR capabilities are so different than anything else that I've seen. The performance has actually not been too bad. You would think that there would be an issue with the cloud stores, but we set up a local cache on each filer that allows it to store up to a terabyte or two of regularly used data. That gets probably 80% of what people use, which means that they're accessing a local copy that's synced with what's in the cloud. This means that they don't really have to go to the cloud to get a lot of it. But when they do, it's pretty quick. It may not be as fast as if it were a local copy, but it's not too bad.

My advice for anybody who is considering Nasuni is that they definitely want to look at all of the options, but that Nasuni does have the best setup at this point. It offers the ability to recover things and provides data security. Especially with ransomware and all of these other new things that are causing lots of problems out there, it really helps mitigate some of that.

The biggest thing that I have learned from using Nasuni is that you shouldn't be afraid of the cloud.

I would rate this solution an eight out of ten.

We use the Nasuni Filers and Nasuni Management Console (NMC) to manage those Filers.

We have four offices in Los Angeles, Singapore, Hong Kong, and Shanghai. In each office, we have a Nasuni Cloud Storage Gateway that allows end users in each office to access their data in the cloud. However, that data is cached locally.

It is an excellent solution for collaboration. We are an architecture firm. For example, we may be working on a set of architectural drawings files here in Los Angeles. We save those drawings at 17:00, then those drawings will sync to other offices. When other offices, e.g., China and Shanghai, come online, the data is there and on the network drive. They can continue working on those drawings or meet with clients. They can also access them on an iPad if they are at a job site. So, it is very useful for collaboration on a global scale.

The product integrates with industry standard platforms, like Active Directory. So, it is very straightforward to apply changes to the organization.

If we were hit with ransomware, we would have to know the time of the ransomware, then we can easily recover files using Nasuni Management Console.

It is much simpler to upgrade a solution because the data is in the cloud. You are just upgrading your gateway and pointing it to the cloud. So, it is much simpler to upgrade.

The bread and butter of what it does is the ability to sync data. Because in architecture, we are using unstructured data with a lot of big files and large file structures going from one place to another. Nasuni does that very quickly.

I can see who is logging in on files from all over the globe. For example, if a file is locked, maybe a user in Shanghai has locked files or something, I can see that from the Management Console, then unlock the file. I would rate the importance of this feature as nine out of 10.

Nasuni enables us to provide file storage capacity anywhere it is needed and on-demand. I would rate this feature as nine out of 10 because of the nature of our business. We can look at identical data for all our locations at the same time, which is very useful.

The tools are very good, and I learned them. They are relatively straightforward.

The end user has the ability (on his own computer) to recover a file.

I would like to see them improve their tools in regards to accessing data using smartphones, tablets, and iPads. I think the Nasuni app could be improved to make access to the data cleaner and more efficient.

I have been using Nasuni for four and a half years.

It is a stable product. I wouldn't be using it if it wasn't stable.

Its strength is that it is extremely scalable. It is very quick to spin up a new Filer. We have opened and closed offices in the last four-and-a-half years. So, I have had to spin up a gateway, then I have to shut it down and move it. In that sense, because the data is in the cloud, that has been a huge strength of the product.

We are limited by the subscription that we have. We have incrementally increased our data. We have increased our data by probably five percent a year. So, I suspect we will continue to add about five percent per year to our subscription.

Everybody uses it, which is about 110 employees and consultants.

I would rate the technical support as seven out of 10. 

Before Nasuni, I would use more conventional storage arrays from larger vendors, like Dell EMC and HPE. We switched because Dell EMC didn't offer a cloud option or the ability to quickly sync data to our other offices.

Nasuni has replaced multiple data silos and toolsets with a single global file system. We still have separate storage in our offices. However, that storage is really for less critical data, libraries, etc., where the most critical data is on the Nasuni platform.

Replacing multiple data silos has been extremely important for us. The alternative is the way that we did business in the old days. Previously, we worked on a storage array here in Los Angeles, then we would have to transfer the files in some way (from one place to another) to a separate storage array. With the amount of collaboration that we do globally, that is very difficult.

In the old days, we would have an architect fly to China and meet with a client about a drawing or design, maybe at a job site. We are not able to do that anymore due to COVID-19. Instead, we now can have our staff in China pull up the same drawing on an iPad and mark up the drawing using a web conference. This solution provides us reach to our clients, which is very important.

The initial setup was not simple, but not complex.

Our deployment took 30 days.

I worked with Nasuni Professional Services. Over one weekend, we migrated the data.

We also worked with Consiliant Technologies for the deployment. Our experience with them was excellent.

I do the maintenance and upgrades of the product. This takes one person (me).

I see ROI qualitatively from people in our global offices. After I made the change, their workflow definitely improved.

Continuous File Versioning definitely saves me money on purchasing expensive backup solutions.

We still use on-premise infrastructure, but it does eliminate part of our infrastructure. It is about a 20% savings versus conventional storage arrays and backup solutions.

Because you are paying for a subscription, there is less of a CapEx cost. It has reduced our capital cost by about 40%, but we are paying for a subscription as well.

It has a license fee as well as hardware costs, which we would incur if we want to use Nasuni Cloud Storage Gateway for upgrades.

We pay for a subscription.

We looked at keeping our Dell EMC storage arrays. I also looked at Panzura and Nasuni. Both Panzura and Nasuni fulfilled our requirement of syncing the data. However, I preferred Nasuni's architecture and the way that they did it.

Nasuni is the preferred solution of our CFO because the business agility and cash flow are more predictable.

Investigate the cloud provider that you want to use, whether it is Microsoft Azure, AWS, or whatever Nasuni supports. Do that research first, then investigate with Nasuni regarding pricing.

You need to determine what data you are willing to put up in the cloud, then what data you deem critical to be cached locally in your location. For example, if you have 20 terabytes in the cloud, how much of that do you really need cached in each location? Is it five terabytes? Is it seven terabytes? This information will help with the migration.

If you have a requirement where you have multiple locations that need to look at identical data because of collaboration, that is Nasuni's strength. If that is not a big requirement, then you would probably look elsewhere.

A big advantage is having the data exist in the cloud. This has certainly relieved a lot of pressure from our IT department in regards to having a backup as well as preventing some ransomware in all of our offices. That has definitely been a big plus.

I would rate it as nine out of 10.

We are using it as a file share server. The solution is for CIFS and Windows file shares. We have boxes deployed in different environments, including on-prem and, in a few locations, it's in a virtual image.

We provide support to our customers and are currently managing more than 200 devices.

We use it at the global level and it supports a 360-degree view of the data.

It's also easy to deploy. Before, with hardware, it was not possible to deploy things as quickly, but because Nasuni is available in the cloud, as well as via a VDI image, you can deploy it quickly.

Another benefit is that our RPO and RTO are very much reduced. If a user has deleted something, we can provide the latest backup. For example, if they deleted something at 11 AM, we have the backup available from 10:55 AM.

It also helps eliminate on-premises infrastructure. All the data is stored in the cloud, either in block or S3, and that means you do not need large storage hardware in your data centers. You just need an internet connection to connect with the device. That will save costs on space, air conditioning, and power.

And it will reduce your capital cost, with only OpEx contributing to the costs.

The most valuable features are the

• replication
• snapshots.

Nasuni has the capability of taking a snapshot every five minutes. If a user has accidentally deleted their data, we can recover it from the snapshot and provide the latest data to the user. It's a really great feature, one that is not provided by other vendors.

The solution is very important for us because of these features, as well as because there is a cloud version, virtual image, and the physical box.

It also replaces multiple data toolsets with a single global file system.

Also, for provisioning file storage, because Nasuni is a cache device and doesn't store any data—all the data is stored in the cloud—you can provision as much as is needed, spinning up instances as they are required. That means that even if a customer has heavy data requests, we can fulfill them in less than 24 hours. We just spin up the instance, connect it, and it's available for use.

And for some users who are accessing data on-premises, we are able to provide file storage capacity for VDI environments.

Nasuni also has an embedded feature, an antivirus, which will automatically scan for issues with any file. If a file is infected, it will not be saved on the disk.

Access Anywhere is also a great feature, allowing you to access data from your mobile and from your desktop.

And suppose a disaster happens. Nasuni's metadata is available within 20 minutes, meaning you can deploy the new instance and map the data, copying the data from the cloud.

The only issue we face with Nasuni is from the performance perspective. Sometimes, when we deploy a Nasuni device, it doesn't meet our requirements. It's a capacity-planning issue.

I have been working on Nasuni since 2018.

It's stable.

Nasuni's support is very good. They provide solutions on a priority basis.

Positive

It's easy to deploy, hardly taking an hour, on average, and requires minimal staff for both the deployment and management. A single person can easily manage it.

When we have migrated all of a customer's data to Nasuni, none have said that they had much ROI from their then-existing solution. Nasuni is a cheaper solution with good ROI compared to other solutions.

Nasuni should provide small-scale licenses, like a 20 TB license. Currently, the smallest is a 30 TB license. Smaller-capacity licenses would be good for some users and help increase Nasuni's sales.

NetApp doesn't have the same features for managing devices, whereas from the Nasuni Management Console, you can manage multiple devices at the same time. The centralized management is a great feature.

The only disadvantage of Nasuni is due to the fact that all the data is in the cloud. Other devices, like Panzura, have the data in the cloud as well as local copies.

If you're concerned about migration to the cloud, you can use Snowball to move the data to the cloud and then you can upload it to Nasuni. There are a lot of options available.

I can't think of any features that should be added to Nasuni. It's a good product.

Unified, global file sharing while reducing costs and eliminating backups.

We had a Nasuni filer in our Texas office. But due to the cold in Texas, power was down for a couple of weeks due to the inability to get fuel for the generator.  The users outside the area could work from home but they could not get to their filer in their Texas office. Since Nasuni stores our files in the cloud, we just setup another filer in the cloud with access to their files and they were back in business.

The features most valuable are 

1: Nasuni storage is immutable and the ransomware protection that it provides.

2: Elimination of file storage cost through elimination of backups as well as deduplication and compression.

3: Excellent support - the Nasuni support team is always there when you need them.

4: Centralize management and reporting capabilities provided by the NMC.

5: Ability to leverage our AWS Marketplace discount.

6: User file restoration self service.

7: Global file locking providing the ability to share any file with others in the world with the same controls that a users would have on one file server.

8: Ease of performing updates through a centralized console.

I originally felt that a Dropbox type interface would be useful but after second thought with all of the new always-on vpn capabilities that are available, I've reconsidered and decided that's not an appropriate for this platform. 

I have been using the solution for about two years.

We have not had any issues with stability.

The filers are separate devices. Admins really don't have to log into them too often. There is a Nasuni Management Console, which can do most of the management work and perform all of the upgrades, which routinely come out. You don't have to worry about shutting things down. We alert users when updates are being deployed with plenty of notice and reminders and do them manually. We typically do the updates manually during non-working hours in each region, but you can also schedule the upgrades to install automatically. 

It's a solid solution, easy to maintain.

It is very scalable. The only thing that I was concerned about initially was the global file locking. Everyone who was opening a file, anywhere in the world, has to talk to that service component. This solution was very well designed, scalable and redundant.  We've had no performance or problems with it at all. 

Nasuni's file storage system is extremely scalable and we are not close to exceeding it's capabilities or scalability limits.

Properly sizing filers is the best way to provide good performance and Nasuni does have a spreadsheet-based tool to help in that regard.

Nasuni's integration with Varonis is another plus.  We have one filer setup to read all files in the system in the event the entire file system has to be rescanned, which occurs about once per year.  When it does, the users don't even know it's happening.

The technical support is excellent. The Nasuni team knows we rarely have issues  and that we are not as familiar with the service as they are.  They are good about it and help us through all problems, all of which have been related to issues on our side.  We have not had any problem related to the service itself. 

When the Dallas Tx are had a deep freeze, we were upset because we could not access the filer there with a projected restoration of at least 2 weeks.  Nasuni support indicated that we could just do a disaster recovery to make another filer, which we proceeded to do in the cloud.  It was that simple and guidance was much appreciated.

I would give the Nasuni sales and technical support teams a 10+ out of 10. I don't do that very often, but Nasuni has never failed us and they are very easy to deal with with a top quality service organization.

Positive

Our original solution was traditional file servers and backup systems located in each remote office which we migrate to regional data centers.  Access performance became an issue.

We wanted to go to a cloud based system and back then, I was sold on Dropbox. It was fast, clean and simple. But upon a closer look, I could see it was not an enterprise solution.  Then I came across Nasuni and they had what we needed with global file locking.  We tested it, it worked as advertised and we moved to Nasuni with local office filers, supplemented with virtual filers in our regional data centers.

An additional win involved eliminating most of our disk and tape storage for backups performed by our software development team in Australia.  Our engineers had terabytes worth of source files that they used to develop our product and we were purchasing backup media for them. Once we convinced them that Nasuni could do the job, and that the data was stored in AWS, we were able to eliminate all of the extra hardware, tapes and physical storage space for it. Deduplication worked wonders for this solution too.

The initial setups varied on a site by site basis.  Some had physical filers and others were VMware based.  Our Infra team was very familiar with all of the environments and worked well setting up the sites and doing the file migrations.

It was a combination of our Nasuni Sales and Solution Architect, Nasuni Professional Services and our internal Infrastructure team and consultants.

Most of the work was related to summarizing our storage usage at each remote office and in our data centers which was then used to determine the sizing of the Nasuni resources.  During that process sizing of the physical filers was also done, allowing for projected growth.  Although there were a lot of logistical details related to the infrastructure configurations at each of our sites, we were able to get the information needed.

However, by far most of the work was in migrating the files from the old file servers to the Nasuni filers and coordinating testing with the end users.

The Nasuni caching system, if it's properly configured, will not be touching the S3 storage in AWS very often. With S3, the way they configure it, the normal S3 stores all your data and you can access it at any time. Then, there is something called S3 IA for the infrequently accessed. AWS says that they give you a break, e.g., half the price, if you write your data once and don't touch it for something like six months or a year. By setting the caching up in the filers, you can reduce the amount of access you have to S3 and cut that cost by 50% too.

The overall cost of storage for Nasuni is much lower than to setup file server, especially in light of the fact that you don't have to back them up.  There are no charges for virtual Filers - you can install as many as you want.  

Virtual filer images come in various formats depending on the technology that you are hosting them on.  There are images for various cloud-based or in house infra service being used such a AWS, Google, VMware, etc.  

ROI is also accelerated backup systems, media, off site storage and transportation/shipping is all eliminated.

They could lower the cost, but it saves so much money when you go into it (by losing all the backup).  I believe getting the experts involved pays off in the long run.

There are two packages that you can buy, but we only got the first. The first package is how you set up Nasuni. It is mainly related to selecting which virtual image you want. This depends on what target you are running it on. We didn't really have a lot of problems with that, because we purchased most of our filers right from Nasuni. Therefore, they came preloaded. It was just a matter of receiving the filers and having them set up at the site. The second package is basically setting up the file server, the directories, and doing the migration.

With the appliances, we received five years worth of all service and maintenance. Basically, they give you a rack mount PC. They actually have one desk side if you want to put it in an office environment that has encrypted disks. They follow the Fed standard. Therefore, if someone steals a disk, they can't look at the data. Even if they take it out of a machine, they still can't get to your data. 

There are five or six different filer models. One of them is an office-based unit that sits under a desk. The rest of them are all 1U and 2U rack mount devices. They have it covered pretty well.

We tested it at my previous company. There are other companies who do the same thing that Nasuni does, but Nasuni is the only one with a single global file lock. They have spent a lot on making that fast and redundant.  The global file locking was a major difference and benefit for us.

The company and its technology are solid and their solution architects and support teams are EXCELLENT!!

A proper directory and file structure/organization design is important to allow auto-failover access redundancy.  Nasuni can explain how this can be done.

If I had to rate Nasuni, I would give Nasuni 10+ out of 10. The solution has been a lifesaver. 

Nasuni is our data storage solution. In addition, it's our data backup solution. As a construction company, we have onsite offices where we're building a building, a highway, or a water treatment plant, and we use Nasuni for data storage for all of those job sites. Additionally, for all of our regional offices, Nasuni is our storage solution for our entire company's internal data.

It has on-prem and SaaS components, but for all intents and purposes, it is on-prem.

Nasuni replaced our previous data storage solution for all our job sites back in 2018. Before that, if we had a job where a data server was stolen or a file was deleted, it was a long and onerous process to get that data back. For us, just like pretty much every other company out there, our data, our intellectual property, is significantly more important than the hardware itself. Once we rolled out Nasuni, we were able to restore deleted files in seconds, as opposed to days or weeks. It takes five or six clicks and we're able to restore data.

Additionally, if one of our offices has an electrical or power issue, we are able to move our end-users to a different edge appliance where they can access their data, minimizing downtime for our end-users.

It has also replaced multiple data silos and toolsets with a single, global file system, and that is extremely important. We have one platform to manage all of our data, to see it and to quickly access it, and that is huge. On top of that, Nasuni provides something called the NMC, or the Nasuni Management Console, which manages all of our Nasuni edge appliances. Not only can we manage the data, but we can also manage the appliances from a single pane of glass. Instead of having to log in to 50, 75, or 100 appliances, we can just log in to one device and manage everything from there, monitor alerts, push out updates, et cetera. It's really helpful.

With the NMC, when we are asked to restore a deleted file, we can do that from that one console, as opposed to going to the specific appliance the end-user was using to access data. From an IT perspective and a support perspective, the fact that we can use one location to access all of our edge appliances and do the work that we need to do, such as a file restore, makes it significantly easier for us. In turn, it makes things easier, quicker, and more efficient for our end-users. When a mistake happens, we can quickly apply whatever the corrective action may be and get our end-users back to accessing the data that they need.

The NMC has made things even simpler by providing one area where we can manage all of our edge appliances, as opposed to hitting each edge appliance individually. The NMC has really made it more efficient, streamlined, and simple for us to manage our data environment.

With Nasuni, our data is stored in volumes. If we have to provide data to an internal business group, it's easy for us to set up a new volume of data, if needed, to make it unique to that business group. We can also just provide remote access for another group internally to an existing volume that we have. In terms of giving the right people access to the data they need, Nasuni makes it pretty easy to do. That makes our business more efficient and more streamlined. It cuts down on internal workload and the tickets to our department, the IT department, to give end-users access to the data they need. As a department, we have become more proactive in recognizing and giving correct access to the data the end-users need.

With continuous file versioning, the way our data is backed up allows us to recover quickly if some of our data is compromised by a ransomware attack. We can simply revert back to a different point in time before that attack took place and make that data available to our end-users. That makes things much easier for us and gives us one less thing to worry about.

In addition, with continuous file versioning, there are some tools in Nasuni to very quickly help us restore a file that's been deleted or corrupted, back to a time where it was not deleted or corrupted. We have that functionality in the NMC and we can restore a file in just a few minutes.

Another benefit is that Nasuni has helped to eliminate infrastructure significantly. About 90 percent of our jobs are scenarios where we're onsite building a building or a stretch of highway and, for those jobs, we have saved on hardware costs and have not had to purchase a server. Instead, we have been able to access other edge appliances within the company. We can utilize existing hardware and don't need to buy new hardware for a particular job. That has certainly saved a lot of money on hardware, on the order of a few thousand dollars for the cost of a job-site server.

And that has made our infrastructure support efforts a lot more streamlined. It has reduced the soft costs, including the time the entire IT department spends on getting things up and running, and the time spent supporting users when a file gets moved or deleted and has to be restored to an earlier time.

We can also accurately forecast our costs for replacing the 10 percent of our Nasuni edge appliances that are on-prem, as needed. We know what to expect, how much life we can get out of them, and forecast when we will need to replace one. There is a need for hardware replacement, but that need has decreased. While we have established, internally, that we need to have that on-premises machine, we have virtualized many of our Nasuni edge appliances going forward, minimizing that hardware footprint that we have to manage.

From an agility perspective, our onsite people who are building something have the ability to access their data from any location and they can go back to the data for jobs they previously worked on. An end-user can be starting up a new job and, at the same time, can close out a job that was run somewhere else. Nasuni gives them that flexibility, making them more productive from one location. In addition, many of our end-users work at multiple locations and may be in five different locations from Monday to Friday. They're able to access all the data they need from those different locations and that is definitely a part of what they need to be successful.

One of the things we find most valuable is how quickly we can restore a deleted file. An unexpected byproduct of this feature is the ransomware protection that Nasuni provides as well. 

Another helpful feature, in addition to restoring a file that was deleted within 24 to 48 hours, is that we have the ability to restore a file or a folder that was deleted, going all the way back to the inception of that file or folder. That means we actually have unlimited backups to the inception point of data with Nasuni.

In addition, Nasuni enables us to provide file storage capacity anywhere it’s needed, on-demand, and without limits. That's important to our company because, as a construction company, we are often building where nothing else exists. We may be adding a new stretch of highway, or replacing a stretch of highway in a remote area, or building a water treatment plant in a remote, desolate area where one doesn't exist. The ability to give our end-users their data, safely and securely, is huge. When we are informed of a new job that we have to work on, we can usually get that project management team up and running with access to their data within three to four hours. For our transient workforce, where people are at a location for 12 months or 24 months and then move, having the ability to move to a new location and access new data, as well as old data to close out an old job, is critical to the way that our workforce gets the job done.

One area that we've recently spoken to Nasuni about is single sign-on.

Another is integrating Nasuni with Azure Active Directory. In our particular case, that would allow for third-party consultants to access our Azure Active Directory environment as opposed to coming to our on-premises environment. 

Nasuni is aware of these issues which are something of a wishlist for us, and we hope they will work on them sooner rather than later.

I have been using Nasuni for 10 years.

Nasuni has developed a good product that is secure and allows our end-users the flexibility they need to access their data. We're very confident in Nasuni and in what they provide. We're hopeful that they can continue to stay up with the times, but we're completely comfortable with the stability and the footprint that they've created in the data storage field.

The product was built and designed to be scalable. We can add on new devices, new edge appliances, in less than a day, whether they are physical or virtual devices. The fact that we can do that quickly is really helpful in our environment. If we need to scale down, we can do that as well and move our end-users to a different edge appliance to access data when their primary one is being decommissioned or needs service. The scalability is definitely an asset of Nasuni.

We have about 3,500 to 4,000 employees and all of them are users of Nasuni. They include everyone from upper management and ownership, all the way down to people in the field and college interns at our job sites who help us complete the projects we're working on. Everyone in our company accesses that data.

We increase our storage by 10 to 20 percent every year. Data storage is a growing need in our company. I don't see that increase in storage diminishing any time soon.

We require two people for maintenance of Nasuni. They do things such as building a new edge appliance and monitoring for and implementing new version installations. They restore files that have been deleted or moved and work with our vendor when it comes to licensing renewal and when we need to purchase physical hardware. They are also the main point of contact for opening support tickets if an issue arises.

I give their tech support a 10 out 10. They're great.

This is the first vendor that has helped us with all our data storage. Before, we did all that internally.

We have a license that we renew annually and we recently renewed about 250 terabytes of data. There are no costs in addition to the standard licensing fees.

If a colleague at another company told me they have concerns about migration to the cloud, I would say Nasuni has put a great deal of effort into simplifying and streamlining the migration process. We did not go through that, as our process was a little bit unique when we moved our data over to Nasuni. But in the years that I've been working with Nasuni, I have seen them put a lot of time and effort into streamlining that process to move data from an existing storage solution over to their cloud data storage solution.

When it comes to the migration, the amount of time you put into preparing and organizing your data will make that transition smoother and more efficient. If your source data is permissioned properly and the overall hierarchy is as organized as it can be before you move it, that will make that process significantly easier. Also make sure that end-users are accessing the data they need to access. Put time and effort into making sure that is correct, as opposed to making it a "Wild West" and giving everyone access to everything.