What is our primary use case?
We use it for a couple of business units that need to quickly transfer data from the field to our offices. They run tests in the field and then they have to get that data uploaded quickly. They connect to the filers in our cloud, and that allows the data to snapshot across to all the Nasuni environments within our organization.
It's deployed through a combination of on-prem and cloud. It's more of a platform as a service or infrastructure as a service because we have hardware appliances that connect to our Azure infrastructure in the cloud.
How has it helped my organization?
When our field techs collect data from the units they're inspecting, that data is being uploaded and made visible on-demand. The way we're configured, those snapshots commit every five minutes. Within a five-minute window, based on bandwidth, that data will be available to any of the business units that are looking for it at our various locations.
Nasuni has definitely simplified our data management. Before we implemented it, we were struggling to figure out how to get data to different locations. It was a challenge. But the unified file system turned that into a very straightforward process. Everybody uploads their data to that directory structure and the data becomes available for everybody in all our locations.
Thankfully, we've never had a ransom attack, but the fact that we can restore data within that five-minute window, after each snapshot, has been extremely helpful. The continuous file versioning also makes recovery of a deleted file a very straightforward process through the NMC, the Nasuni Management Console. One of the server administrators for Nasuni follows a few quick steps to restore that file. We've had to do that several times, and it has been a very straightforward process.
In addition, the snapshotting, which is our backup, has made Nasuni extremely easy when it comes to maintenance. It's a set-and-forget type of operation. With that snapshot continually running and always capturing the latest data, it's providing a backup at that point. It's very straightforward in terms of the impact on our IT.
What is most valuable?
The snapshot functionality and the unified file system are definitely the most valuable features for us. The UFS allows everybody across the organization to see the exact same data at the same time, instead of having different file servers with different structures on them, and that's mission-critical. We have different branches throughout our organization that have to act on that data. When it's uploaded to Nasuni and it's snapshotted out to all locations, each one does something specific with that data. It has to be consistent across the board, with multiple people accessing it. We have to make sure that everybody's on the same page.
What needs improvement?
I would like to see improvement in the training Nasuni provides. Compared to some of the other vendors out there, like Microsoft, where you can find how-to videos, Nasuni only has a lot of PDF documents that you have to go hunting for. It's workable, it certainly isn't a problem, but video walkthroughs would always be helpful. Microsoft offers that a lot for its infrastructure.
Buyer's Guide
Nasuni
April 2025
Learn what your peers think about Nasuni. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
849,190 professionals have used our research since 2012.
For how long have I used the solution?
We've been using Nasuni for about six years.
What do I think about the stability of the solution?
Early on, there were some concerns, but over the last couple of years, the stability has been flawless.
What do I think about the scalability of the solution?
It seems that if we were to have to scale out, it would be a very straightforward and simple process.
We have a couple of hundred technicians who connect to Nasuni, and on our engineering team there are 30 to 40 people who are retrieving and relying on the data that's coming in.
In terms of maintenance of the solution, it's taken care of by our infrastructure team that consists of three to four members of our IT team, but it does not require full-time attention. They handle administrative duties, assigning access to folders and directories. It uses Microsoft's NTFS permissioning and they add members to the group. It's not really Nasuni maintenance, it's actually the directory structure that makes up the day-to-day maintenance. There is also quarterly maintenance when we provide software and security updates, and that's a very straightforward process.
We have no plans at this time to increase our usage of Nasuni, but the potential is always there. It really has served its purpose in our particular use case scenario.
How are customer service and support?
Over the later years, I would definitely give their tech support a nine or a 10 out 10, as they've been responsive. Early on, when we were implementing, it was a little bit of a challenge, but in recent years, which is what matters, they have been excellent.
Which solution did I use previously and why did I switch?
We didn't use a solution before Nasuni. We just had a legacy file system, legacy Windows Servers on a standard network.
How was the initial setup?
The initial setup was straightforward, but we had the assistance of a product specialist that they assigned. They held our hand through the whole implementation process. It could have been complex, but the product specialist came out and gathered our requirements and made the whole process very straightforward. They walked us through the whole implementation process, including how to set a filer up and the proper way to configure our file system for our scenario.
The configuration portion was very straightforward. After shipping out the filers to each of the locations and getting the hardware set up, the configuration process took just a few days. But the process took a bit of time because we were transferring large amounts of data from our legacy systems over to Nasuni. That wasn't really a Nasuni issue, it was a bandwidth issue with the amount of data that had to be transferred. That ended up taking closer to a month but through no fault of Nasuni.
Our implementation strategy was to move all data from the legacy system over to the Nasuni system. We then had to train all of our technicians on how to use that system. It was a straight cut-over from legacy to Nasuni.
What's my experience with pricing, setup cost, and licensing?
Licensing for the data is something that is handled on a yearly basis. Pricing is calculated per the number of terabytes to be utilized with Nasuni. We're in the 60 terabyte range. We have to keep in mind our cloud storage costs. Although that's unrelated to Nasuni, Nasuni consumes cloud resources.
There are no costs in addition to the standard licensing fees.
Which other solutions did I evaluate?
The original business unit did do some investigations but I don't know which products they looked at. When Nasuni offered to do a pilot, they ran through a pilot with it. I don't think the other vendors ever got that far with us. Nasuni stood out as soon as the pilot was kicked off.
What other advice do I have?
Get together with a product specialist, as we did, so they can walk you through the process based on your use case scenario. That's what they did when implementing it for us, which made it very easy. There is no way we would have been able to configure this on our own, without that support at the very beginning. It's a completely different type of technology. But they handled it and performed the knowledge transfer very well and it was easy to take over supporting it once it was working.
We haven't really had to use Nasuni's on-demand abilities. We renew our storage capacity once a year for a fixed price. We're not continuously changing that. We have to contact Nasuni and get an estimate on any price increase for additional demand.
We've been running in the same configuration the entire time, but if we had to make any changes it would be very fairly straightforward. It's all done within a central management console that communicates to all the hardware appliances and filers in the cloud.
And while Nasuni has not eliminated on-premises infrastructure for us, because we use hardware filers, it has the potential to do so. We have to have our data in the data center to create that local experience for the end-user. If we were to push those filers up into the cloud, we'd be looking at more latency, perhaps, due to network connections. We're using their hardware appliances by design, as opposed to putting them in the cloud, as we're dealing with very large files.
What I would tell a colleague at another company who has concerns about migration to the cloud and about Nasuni's performance is that Nasuni is straightforward. Once you get migrated over to Nasuni and get your data in place, it's a very easy, very secure process to maintain that data, as opposed to having to run different backup agents for particular servers. I would also say that you've got the unified file system, which allows all users at different locations to see the same data, and that is very difficult to do with a Microsoft system. And the snapshot technology is very reliable and very simple. Once it's configured, you can pretty much set it and forget it, with just some basic monitoring of it.
Overall, it has been straightforward and we're very pleased with the Nasuni system. I would definitely give it a high rating.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.