NetApp Cloud Volumes ONTAP Reviews

We use the full suite of ONTAP use cases across both on-premises and cloud environments, covering various applications and scenarios.

The primary reason for our continued loyalty to NetApp is their Snap technology, which is widely recognized as the main factor. It offers ease of use and a comprehensive suite of applications, including features like SnapMirror, SnapVault, and unified snapshot management, all bundled into a single product. With just three individuals, we're able to efficiently manage petabytes of data, which significantly reduces our operational costs.

My main concern with ONTAP is the rapid pace of technological advancements. For instance, NetApp introduced features that I'm still trying to find a solution for, specifically in the realm of cloud file storage services and infrastructure. There is currently no direct cloud integration, and you need to establish connections through Active Directory or access data via SIPs or NFS mounts. It would be fantastic if NetApp could offer a solution that's as user-friendly as Google Drive for seamless cloud storage integration.

I have been using it for twenty two years.

Its ability to detect ransomware or external threats has been highly effective. While we haven't experienced any actual ransomware attacks, we have encountered threats. These threats are promptly addressed by our vigilant security team before they can infiltrate our environment. The stability has significantly improved over time. In the past, there were challenges, but now it's much more reliable. It simplifies our workflow, eliminating the need to navigate through various steps on our desktop.

Regarding scalability, it performs admirably. I haven't encountered any issues with its ability to scale. However, it's worth noting that NetApp faces stiff competition in the realm of private channel solutions.

The support services have undergone significant changes over time. While they were excellent during the initial phase, the experience has become challenging lately. The positive aspect is that I have a long history of working with NetApp, so I possess in-depth knowledge, but for new team members or peers, it's quite a struggle to work with support. When you call in, you often start at the first level, but most of our issues require third-level assistance, which means navigating through the first and second levels before reaching someone who can effectively address the problem. This process can be frustrating and time-consuming.

The complexity of the initial setup varies depending on the individual handling it. If I'm the one setting it up, it's relatively straightforward as I have extensive experience working with it.

The current process is quite straightforward. However, I believe there is room for improvement, particularly when it comes to migrating non-NetApp data to ONTAP or the cloud. While there are some existing tools, they don't offer the robustness required for seamless migration of third-party data to ONTAP.The integration with AWS native services, like DataSync and backup, is actually quite impressive. We've tested it, and while it's a good product, regrettably, we currently don't have a need for it.

The cost is quite high.

Overall, I would rate it nine out of ten.

Our organization utilizes a hybrid cloud in which Cloud Volumes ONTAP is a single node. We have multiple instances of Cloud Volumes on a single node in AWS, and we primarily use it to take snapshots for disaster recovery.

We save many snapshots at that location so we can redirect users if something happens on our primary site. 

The other use case is backup. We enabled SnapLock, which acts as the WORM, making those snapshots immutable. In other words, they can't be deleted.

Those are the two use cases. One is disaster recovery, and the other is to preserve a third copy of the snapshot. This is typically for Tier 1 applications. We have a third copy, and no one can delete the volume's snapshot. The end-users don't work with Cloud Volumes directly, but if our operational team needs to restore some files that aren't on-prem, they sometimes go to those instances in Cloud Volumes. That's only when they have to restore something beyond the date range of the on-prem snapshot.

The main benefit we get from this product is the ability to deploy it anywhere we want, whether that's on-prem, a remote physical location, or in the cloud. It doesn't matter from an operational perspective where it is. The command line and operating system are the same. 

If I give it to someone to manage, they don't know if the product is running in the cloud or on the physical location. That's great because you don't have to worry about knowledge transfer. The product runs the same regardless of how it's deployed. Cloud Volumes has also significantly improved performance and storage efficiency because it has capacity tiering, which is helpful if you're cost-conscious. 

It provides unified storage, so you can use it for NAS or block. However, we segregate a separate cluster for files and another for block storage. Fortunately, it's the same ONTAP operating system, so a user doesn't need to understand a different set of command lines or another method if dealing with block storage or files. It's all the same for them.

It helps us manage our native cloud storage. Cloud Volumes allows us to choose which storage types are applicable for us. In our case, it lets us choose a cheaper EBS storage, and then we can perform capacity tiering in S3. It gives us the flexibility to determine which type of native AWS storage to use, which is cool.

We mainly use Cloud Volumes for two features: SnapMirror and SnapVault. Those are the two that our use case requires. Data deduplication and capacity tiering are the main primary reasons we adopted the solution. The data is deduped and encrypted, and we use capacity tiering to cut down on our S3 storage costs.

The encryption and deduplication features still have a lot of room for improvement. 

We first deployed Cloud Volumes ONTAP four years ago.

Cloud Volumes has been stable so far. We haven't had many issues. If there are any issues, it's typically during an upgrade. Some tools are upgraded automatically through the cloud manager, but it's nothing major, and the upgrade has been smooth as well.

Cloud Volumes added an option to stack licenses to increase capacity. Before, you were only allowed one license per instance, which gave you 360 terabytes. Now, you can stack the licenses to add a second license of the same instance to get another 360 terabytes, totaling 720. 

That's vertical scalability, but we haven't scaled horizontally. We just use it for a single node per instance. We started with one instance, and now we are on the seventh. As we add new on-prem projects, they always require a copy of their data somewhere. That's when we deploy additional instances.

My experience with technical support has been positive overall. I would rate NetApp support eight out of 10. I would deduct two points because they don't have complete control of the solution. It's more of a hybrid setup. They provide the software level, but the underlying infrastructure is AWS. If there's an issue, it's hard to distinguish if Cloud Volumes is to blame or AWS. That's why I would say eight because there is that question. When you have multiple layers, it takes more time to troubleshoot. 

Installing Cloud Volumes is quick and straightforward. I can deploy an instance in half an hour. Compare that to an on-prem serverless instance, which requires a lot of planning and work with other teams to lay cables and plot out space in a data center. That takes three to six months versus 30 minutes. It's a big difference. We only need one staff member to maintain it. 

We used our in-house engineers to deploy Cloud Volumes.

As we store more data, we save more money using Cloud Volumes. The deduplication engine can find more commonalities as you accumulate more data, which has helped. Of course, it depends on the data type. It doesn't help if you have compressed data, but it's suitable for unstructured data.

Deduplication is one of the most significant improvements I've seen in the product. In the past, Cloud Volumes could only dedupe on the volume level, but now it can dedupe on the aggregate level, which means you can look at more volumes and commonalities. You have a greater chance to dedupe more data in that scenario.

We save on storage in general. One of the biggest selling points of Cloud Volumes is that you can deploy it quickly. You don't need to spend time and resources planning and setting up physical storage equipment in your data center. Real estate in a data center is precious, so cost savings makes Cloud Volumes enticing. In our case, we don't need a physical disaster recovery location. Anything that isn't Tier 1 goes to the cloud.

I rate NetApp Cloud Volumes ONTAP nine out of 10. 

It is managing services in our production environment that are in Azure. It provides file shares, both NFS and CIFS, that are used by other applications that are also in Azure.

NetApp Cloud Volumes ONTAP is part of the production environment of our company so the entire company, over 5,000 employees globally, is touching it somehow. It's a part of an application that has data that resides on it and they may consume that application.

Cloud Volumes ONTAP is great because of the storage efficiencies that it provides. When you look at the cost of running Azure native storage versus the cost of Cloud Volumes ONTAP, you end up saving money with Cloud Volumes ONTAP. That's a big win because cost is a huge factor when putting workloads in the cloud. We had a cost estimate survey done, a comparison between the two, and I believe that Cloud Volumes ONTAP saves us close to 30 percent compared to the Azure native costs.

Azure pricing is done in a type of a tier. Once you exceed a certain amount of storage, your cost goes down. So the more data you store, the more you're going to end up saving.

The storage efficiencies from the NetApp platform allow you to do inline deduplication and compaction of data. All of this adds up to using less of the disk in Azure, which adds up to savings.

We have two nodes of the NetApp in Azure, which means we have some fault tolerance. That is helpful because Azure just updates stuff when they want to and you're not always able to stop them or schedule it at a later time. Having two CVO nodes is helpful to keep the business up when Azure is doing their maintenance.

The solution provides unified storage no matter what kind of data you have. We were already using the NetApp platform on our on-premise environments, so it's something we're already familiar with in terms of how to manage permissions on different types of volumes, whether it's an NFS export or a CIFS share. We're able to utilize iSCSI data stores if we need to attach a volume directly to a VM. It allows us to continue to do what we're already familiar with in the NetApp environment. Now we can do them in Azure as well.

It enables us to manage our native cloud storage better than if we used the management options provided by the native cloud service. With CVO, all of your data shares and volumes are on the one NetApp platform. Whether you are adjusting share permissions on an NFS export or a CIFS share, you can do it all from within the NetApp management interface. That's much easier than the Azure native, where you may have to go to two or three different screens to do the same stuff.

The storage efficiencies are something that you don't get on native.

Also, because of the NetApp product, we're able to use the SnapMirror function and SnapMirror data from our on-prem environment into Azure. That is super-helpful. SnapMirror allows you to take data that exists on one NetApp, on a physical NetApp storage platform, and copy it over to another NetApp storage platform. It's a solid, proven technology, so we don't worry about whether data is getting lost or corrupted during the SnapMirror. We are also able to throttle back the speed of the SnapMirror to help our network team that is paying for a data circuit. We're still able to copy data into Azure, but we can manage the transfer cost because we can throttle back the SnapMirror. It's just very solid and reliable. It works.

And all of us IT nerds are already familiar with the NetApp platform so there was not a major learning curve to start using it in Azure.

NetApp also has something called Active IQ Unified Manager, and it gives us performance monitoring of the CVO from an external source. There are several people on my team that utilize the CVO and we each have a personal preference for how we look at data. The Active IQ Unified Manager is a product you can get from NetApp because, once you license your CVO, you are entitled to other tools. CVO does have resource performance monitoring built in, but we primarily utilize the Active IQ Unified Manager.

Beyond that, it provides all the great stuff that the NetApp platform can do, but it's just in the cloud.

I think this is more of a limitation of how it operates in Azure, but the solution is affected by this limitation. There's something about how the different availability zones, the different regions, operate in Azure. It's very difficult to set up complete fault tolerance using multiple CVO nodes and have one node in one region and one node in another region. This is not something that I have dug into myself. I am hearing about this from other IT nerds.

We've been using NetApp Cloud Volumes ONTAP for two years.

We had issues with Azure when they did maintenance on the nodes. They just do their maintenance and it's up to us, the customer, to make sure that our applications are up and data is flowing. When Azure does their maintenance, they do maintenance on one node at a time. With the two nodes of the CVO, it can automatically fail over from one node to the node that is staying up. And when the first node comes back online, it will fail back to the first node. We have had issues with everything failing back 100 percent correctly.

We have had tickets open with NetApp to have them look into it and try and resolve it. They've made improvements in some ways, but it's still not 100 percent automated for everything to return back. That's an ongoing thing we have to keep an eye on.

It is definitely scalable. You can add more disk to grow your capacity and you have the ability to add more nodes. There's a limit to how many nodes you can add, but you can definitely scale up.

Tech support is good. A lot of it depends on the technician that you get, but if you're not happy with one technician, you can request that it be escalated or you can request that it just be handled by another technician. They're very eager to help and resolve issues.

We had some issues with permissions and with getting the networking correct. But we had a lot of support from NetApp as well as from Azure. As a result, I would not say the setup was straightforward, but we got the help and the support we needed and you can't ask for more than that.

I've always found NetApp support to be accurate and good with their communications. Rolling out this product in Azure, and working with the IT nerds in our company and with Azure nerds, occasionally it does add another layer of who has to be communicated with and who has to do stuff. But my experience with NetApp is that they are responsive and very determined to get situations resolved.

It took us about a week to get everything ironed out and get both nodes functional.

We had done a PoC with a smaller instance of the CVO and the PoC was pretty straightforward. Once we rolled out the production CVO that has two nodes, that's when it was more complicated. We had a plan for getting it deployed and to decide at what point we would say, "Okay, now it's ready for prime time. Now it's ready to be put into production."

For admin of the solution we have less than 10 people, and they're all storage administrator analysts like me.

Our licensing is based on a yearly subscription. That is an additional cost, but because of the storage efficiencies that the NetApp gives, even with the additional cost of the NetApp license, you still end up saving money versus straight Azure native for storage. It's definitely worth it.

Make sure that you can stay operational when Azure is doing their maintenance. Make sure you fully understand how the failover and the give-back process works, so that you can deal with your maintenance.

NetApp Cloud Volumes ONTAP is where we host our NAS storage on which we keep our files, et cetera. We have three clusters of CVO, each serving close to 300 terabytes of data. We have our SQL backup workloads and the application data residing in it. We are using the tiering policy, which pushes the inactive data down to cold storage to help save on costs.

Cloud Volumes ONTAP is all cloud-based and we have our workloads on Azure.

At one point we were paying close to $80,000 a month for cloud resources, and now it's down to $25,000 to $30,000 after using the tiering.

Also, using Unified Manager we are able to resolve issues before they have an impact. For example, there were conditions where bulk operations were happening against a particular volume, and our business was also writing the data. We caught it using Unified Manager. The IOPS were low and there was a high latency, close to 1,500 milliseconds. We had a look at exactly what operations were happening and, before the user even reported it, we reached out to the team that was doing the bulk operations to stop whatever process they were running. That's just one example. We have had a lot of occasions where the tool has been really handy when it comes to proactive monitoring. 

And it's not only for proactive monitoring. The same tool is also used for a lot of root cause analysis.

The storage tiering is definitely the most valuable feature. With the pay-as-you-go plan, we can choose between standard and premium storage, but we use only premium for high performance. High IOPS and low latencies are the main features of the premium storage. With respect to tiering, the inactive data is pushed to a lower tier where the storage cost is cheap, but the access cost is high.

NetApp also has something called SnapMirror replications and that's how we replicate our data from production to the DR site, for our BCP. It has pretty solid solutioning for the replications so the SnapMirrors are pretty handy when it comes to BCPs.

In terms of cloud resource monitoring, we use Unified Manager and it's pretty cool. It has both Excel-based metrics as well as graphical representations, which give us a clear idea of which particular file systems have performance problems. We can go over the statistical information and it comes in very handy. At the same time, it has an alerting mechanism where any sort of conditions can be configured and alerts are then sent to your mailbox or your mobile SMS.

It definitely needs improvement with respect to clustering and with respect to more collaborative integrations with Azure. Right now, we have very limited functionalities with Azure, except for storage. If CVO could be integrated with Azure that would help. When there is any sort of maintenance happening in the cloud, it disrupts the service in Cloud Volumes ONTAP. 

If those could be rectified, that would be really good news because it would reduce the administrative overhead my team and I are facing.

I have been using NetApp Cloud Volumes ONTAP for close to two years now.

It is stable, at least with respect to Azure, which is what we use.

NetApp is scalable. When we initially started with Cloud Volumes ONTAP, it had a hard limit of 378 terabytes as its maximum capacity per cluster. Beyond that you couldn't expand. So we had to spin up another cluster. When that was almost full we had to get a third cluster. But I believe that in the recent build of CVO they have introduced the ability to stack one license on top of another cluster, so you can have infinite data per cluster. So there were challenges, particularly with vertical scalability before, but that has now been fixed in the recent release.

In terms of increasing our usage in the future, we definitely will if required. It gives us the flexibility to perform automations and it has its own encryption tools. Right now, we are using it for one particular region in Europe, but we do have plans to get it out to other regions as well, but that's not going to happen immediately.

We have used their technical support on a lot of occasions and they have been pretty helpful. I'm completely satisfied with the resolutions they have come up with. We have created more than a hundred tickets in the last two years. Those were all submitted initially, when we had an older version of CVO, but now we hardly create tickets with support because our team has the ability to administer it.

We had ONTAP before CVO. We also used Dell Isilon and SoftNAS before we migrated to CVO. We switched because we found that SoftNAS was not stable enough to handle the workloads. We often had problems with the applications.

The initial setup of Cloud Volumes ONTAP is pretty straightforward. We didn't have any sort of difficulties getting it spun up. It was also pretty quick. We had everything needed in Azure. It hardly took us three to four hours to have the entire environment set up and ready.

We did some architectural planning for setting this up and we got all the approvals and licenses well in advance, before we actually configured it.

When it comes to maintenance, it depends on what kind of coverage an organization wants. We are a team of four who administer NetApp clusters alongside the cloud resources. We have roughly 2,000 users.

We worked only with NetApp. We had one architect and one contractor from Professional Services.

Now that we have started using tiering, we could still actually save more costs, but we haven't gone to that specific area. We know it is definitely going to affect the performance if we keep all the data in the cloud tier. That's why we haven't. But Cloud Volumes ONTAP has the flexibility to dump all the data to the cloud tier to save every penny possible.

We have an annual license renewal for all the clusters. The license comes with annual training and with some Professional Services time. We have used all of those. I'm not sure if that's standard or it's an agreement between our organization and NetApp, but that's what we get as a part of our licensing.

The money you can save with CVO depends on what type of configuration an organization needs. They can also push all the data down to the cold tier. The pricing model for the Azure Cool Blob offering is pretty low compared to the premium or the standard. The cost of cold storage would probably be 10 cents per GB.

Very few of the cloud service solution providers have that tiering option. Tiering results in a lot of savings.

NetApp, on the whole, is a whole different tool for me. Two years back, when I started, when I had my hands on it for the first time, I found it pretty interesting. I would note its simplicity. It's simple and, at the same, time very powerful and able to handle any sort of storage workloads.

NetApp is really cool. If your organization is looking for cost savings, NetApp is the way to go.

Overall, I would rate CVO a nine out of 10. We had a lot of problems with NetApp, but those were in the very early stages. And NetApp always promises to upgrade their products and they actually listen to the customer's problems. We have raised a couple of defects with NetApp, and they have always been supportive, getting these resolved as soon as possible. 

The NetApp organization, on the whole, is pretty good. They're coming up with go-to-market products like Azure NetApp Files, etc., which is actually the beta version of Azure Sites.

The primary use case is to move age old data to the cloud.

It is deployed on the cloud.

The tool saves us time and money. Now, it's easy to retrieve data back, where you can go back and look at the statistics to study them. Because my company is focused on healthcare, there's no time limit on the retention of information. It's infinite. So, instead of having all our data on tapes and things, which takes many hours to try to retrieve information back. This is a good solution.

The migration is seamless. Basically, we shouldn't be spending a whole lot budget-wise. We would like to have something reasonable. What's happening right now is when we try to develop a cloud solution, we don't see the fine print. Then, at the end of the day, we are getting a long bill that says, "Okay, this is that, that is what." So, we don't want those unanticipated costs.

We use the solution’s inline encryption using SnapMirror. We did get Geoaudits and things like that. In other words, everything put together is a security. It's not like just storage talking to the cloud, it's everything else too: network, PCs, clients, etc. It's a cumulative effort to secure. That's where we are trying to make sure there are no vulnerabilities. Any vulnerabilities are addressed right away and fixed.

The solution’s Snapshot copies and thin clones in terms of operational recovery are good. Snapshot copies are pretty much the write-in time data backups. Obviously, critical data is snapshotted more frequently, and even clients and end users find it easier to restore whatever they need if it's file-based, statical, etc. 

The solution’s Snapshot copies and thin clones have affected our application development speed positively. They have affected us in a very positive way. From Snapshots, copies, clones, and things, they were able to develop applications, doing pretty much in-house development. They were able to roll it out first in the test environment of the R&D department. The R&D department uses it a lot. It's easy for them because they can simulate production issues while they are still in production. So, they love it. We create and clone for them all the time.

The solution helped reduced our company's data footprint in the cloud. They're reducing it by two petabytes of data in the cloud. All of the tape data, they are now writing to the cloud. It's like we have almost reached the capacity that we bought even before we knew we were going to reach it. So it's good. It reduces labor, because with less tapes, you don't have to go around buying tapes and maintaining those tapes, then sending them offsite, etc. All that has been eliminated.

Right now, we're using StorageGRID. Obviously, it is a challenge. Anything that you're writing to the cloud or when you get things from the cloud, it is a challenge. When we implemented StorageGRID, like nodes and things like that, we implemented it on our bare-metal. So the issue is that they're trying to implement features, like erasure coding and things like that, and it is a huge challenge. It's still a challenge because we have a fine node bare-metal Docker implementation, so if you lose a node for some reason, then it's like it stops to read from it or write to it. This is because of limitations within the infrastructure and within ONTAP.

How it handles erasure coding. I feel it the improvement should be there. Basically, it should be seamless. You don't want to have an underlying hardware issue or something, then suddenly there's no reads or writes. Luckily, it's at a replication site, so our main production site is still working and writing to it. But, the replication site has stopped right now while we try to bring that node back. Since we implemented in bare-metal, not in appliance, we had to go back to the original vendor. They didn't send it in time, and we had a hardware memory issue. Then, we had a hard disk issue, which brought the node down physically. 

It needs better reporting. Right now, we had to put everything one to the other just to figure out what could be the issue. We get a random error saying, "This is an error," and we have to literally dig into it, look to people, lock files, look through our loads, and look through the Docker lock files, then verify, "Okay, this is the issue." We just want it to be better in alerting and error handling reports. Once you get an error, you don't want to sit trying to figure out what that error means in the first two hours. It should be fixable right away. Then, right away you are trying to work on it, trying to get it done. That's where we see the drawbacks. Overall, the product is good and serves a purpose, but as an administrator and architect, nothing is perfect.

There's always room for improvement. Overall, it's still stable.

60 percent of our tape data is sitting in the cloud now.

There's a limitation to scalability. Right now, when you want to expand the initial architecture, we have to add additional loads just so it can handle the data without hurting the performance. Then, we have to go back and request for more licensing. It adds to our licensing, thus adding to the cost. In regards to scalability, unless you have a five to six year plan ahead, we can't say, "Great, we have run out of space. Okay, let's try to increase space." It's not like increasing volume.

Unless a much more experienced person comes, I think the print and tech guy is only reading what he sees on the website. He pulls up their code or whatever, because what we see when we open a case is already there is an automatic case that's opened. We see typical questionnaires, but nothing pertaining to the case. For example, you run out of space or high nodes, the technical support is sitting there asking us something else. Nothing to do with high nodes and the volume being down or offline. It's not relevant. It is a generalized thing. You have to sit down and explain to them, "This has nothing to do with the questions you're asking. It's out of context, so you might want to look again and get back with the proper input." That's a pain.

However, the minute we say, "It's very critical," we see a good, solid SME on the line who is helping us.

I'm not experienced as many of my colleagues. They're really frustrated. We did convey this concern to our account person and have seen a lot of change.

The company has always been a NetApp shop even before I entered the company. We continue to use it because of the good products. We do market research, obviously. We do see good products, and every year there is improvement. When we want to do hardware upgrades, it's still very good. The way we are trying to develop, it's very seamless for us and not a pain. 

We have never felt, "We are done with NetApp. Let's move onto something else." I love to introduce other vendors into the mix, just so it's not a monopoly. We still love NetApp as our primary.

It is a little complex. It's completely different from the regular standard ONTAP, and how you manage and the learning code. Half the time you get confused and try to compare it with a standard cloud. You start to say, "Oh, this feature was here. How come it's not there? That was very good there. How come it's not here?"

We used NetApp Cloud Manager to get up and running with Cloud Volumes ONTAP. The configuration wizards and its ability to automate the process was good. We liked it. It's all in one place, so you don't have to go around trying to use multiple tools just to get things worked out. You see what you have on the other side plus what do you have on your end, and you're able to access it.

Mostly, we did it ourselves. When we went to MetroCluster, we used their Professional Services. For the rest of ONTAP, we deployed it ourselves. It is pretty much self-explanatory and has good training.

Cloud is cloud. It's still expensive. Any good solution comes with a price tag. That's where we are looking to see how well we can manage our data in the cloud by trying to optimize the costs.

I do know our licensing cost to some extent, but not fully. E.g., I don't know overall how much we have gone over the budget or where did we put costs down just to maintain licensing on it. That part of it, I don't know. 

I know the licensing is a bit on the high-end. That's when we had to downsize our MetroCluster disks and just migrate to disks that were half used. We migrated into those just to reduce maintenance costs.

We use Caringo. It's object storage migration for age old data. It is a cheap solution for us, so that's why we use that. When we compared prices, Caringo was much cheaper.

Once we migrated everything to Caringo, there were challenges because it's another vendor, and then you're working with two different vendors. We started having issues, so now we use StorageGRID.

We chose NetApp because we already had the infrastructure. Adding additional resources and features into the mix is much easier because it's one vendor, and they understand the product. If we needed to add something and improve on the solution, it's much easier.

I would recommend NetApp any day, at any time, because there's so much hard work in it. It's more open and transparent. Nobody is coming from NetApp, saying, "We're going to sell this gimmick." Then, you view all the good stuff but begin to realize, "This is not what they promised." For this reason, I would recommend NetApp.

They make sure the solution fits our needs. It's not, "Okay, we'll go to the customer site and tell what we feel like regarding their products." Even if it fits or not, it doesn't affect that they've gone through the door. A lot of people do that. NetApp makes an assessment, then they make sure, "Okay, it does fit in."

The product: I would give it an eight (out of 10). The company: It's a six (out of 10).

We have not yet implemented the solution to move data between hyperscalers and our on-premises environment. It's just from our NetApps to the cloud, not from the hybrid. The RVM team is planning on that. So, they can have the whole untouched thing put on the cloud rather than being hosted on our data stores.

We use it mostly for distributed files. For example, one of our customers is in construction. So they have centralized NetApp storage and set up replication with the Cloud volume ONTAP. Several branch users access the Cloud instance. And whatever work that they do on the Civeo instant gets replicated to the client's data center on the on-premise NetApp storage. And they use GFC with Seavio for a seamless experience.

So a lot of these licenses are at the rate that is required for capacity. So they're they're able to reduce the license consumption and also the consumption of the underlying cloud storage. 

So one of the clients had an on-premise 100 terabytes. When that same data went to CVO, he was able to reduce it to somewhere around 20/25 dB. So he was able to reduce using DTO compression, the consumption of this underlying cloud storage. And, obviously, with the licenses, now you need only 25 terabytes instead of 100 terabytes.

There's not much scope for improvement. I think the solution is more restricted with the underlying cloud. The performance of the single instances depends on the performance of the underlying cloud resource. 

I have been using NetApp Cloud Volumes ONTAP for two years. 

NetApp is stable. 

NetApp is scalable. 

The technical support team is wonderful.

Positive

It is easy because Blue XP makes it very easy. Just a few clicks. It's a little bit tricky for customers who are very new to Cloud. While they are the traditional customers who use their data center, if they are not well versed with cloud, they might face challenges in setting it up because that's more dependent on public cloud vendor, not the NetApp.Sometimes the internal support renewal is an issue because the NetApp system sees it as an expired license. So when you try to renew it, it is not reflected in the NetApp portal. So the flow of the support could be improved.

For enterprise customers, it's a very cost effective. But in the SMB segment, yeah, pricing is a little bit challenge for your time.

I rate the overall solution a ten out of ten. 

It is for our databases and for Linux. We also use it for backups. We are replicating snapshots across, so we have different scenarios.

By implementing this solution, we wanted to achieve simplicity. We were trying to get away from reconfiguring everything all the time to work so that we could just get down and implement things within a very small window of time. They would not require a lot of reconfiguring each time.

The main benefit is accessibility. We are able to access it from anywhere. We are able to move things to what we need or are able to pull back the data when it is needed very quickly. We can restore the databases when I need to.

We have a single pane of glass. It helps a lot because time is always the essence. The simplicity comes in handy. It saves quite a bit of time. I do not have to sit down and do all the things. I am able to go in and hit a couple of things. I can deploy, modify, or do whatever needs to be done. It takes seconds versus hours. Once you learn the tool, it is very simple to work from the same point. When it first came out, it was very clunky. It took some time. It took some learning, whereas now, you can catch up pretty quickly. After you start to fine-tune it a little bit, you are able to work with it. Earlier, it was a pain.

I can see how much storage I have left and what I am working with. I can see the alerts. It gives me time to start working on what I need to procure at that point.

It has helped to right-size our workloads. It has been great. It has significantly dropped our downtime for volumes and improved the access for clients. It has helped out a lot in those aspects, so I can stay ahead of the game instead of behind the game. That is where that tool comes in handy. 

It is great when it comes down to pinpointing problem areas. It catches things before they become a problem, so I can keep my clients up and going and functioning. It has been great in that aspect.

I am a big fan of analytics because they give me the chance to be able to keep the clients up and going. That is my biggest thing because when they are down, we lose a lot of money, and we lose a lot of clients, so the ability to make sure that I am up almost 100% percent and being able to stay ahead of the game is a huge win for us.

The ease of use in terms of how the product works is valuable. We are able to work with it and deploy the storage that we need.

The dashboard is a little bit clunky. I like to see it a little bit more on the simplistic side. I would like to be able to create my own widgets and customize what I want to see a little bit more versus what is currently there. That would be helpful so that when I log in, I go straight to my widget or my board without going to multiple places to get to what I need to find or build.

We have been using NetApp ONTAP for 18 years.

It is very easy to scale. It takes next to no time to be able to do that. It is very simple and easy to do that part. You just need to get a license and add the storage.

I love NetApp support. If the first level cannot help you, then the next level can. We can get to them fairly quickly. If not, the reps or the sales can jump in and help us as well. We have never gone without some kind of help in one way or another. If there is a problem, they will jump on and bring on tier two and tier three, and write a script, or do whatever needs to be done. I would rate their support a nine out of ten.

Positive

We have been mostly using the NetApp tools. We have been trying to stay native as much as we can for a long time.

It has been a while. From what I remember, it was not too bad. It could be a little bit more simplistic, but it was not too bad to be out. Once you learn it, it gets easier.

It is a great product. It gives you the heads-up for what you need. You can move clients around and access the clients from different locations. You can also do a restore when you need to be at different locations. That has helped enormously. It has helped drive the cost down. Our clients are able to stay up and function consistently. There are a good 30% to 40% savings. 

We did evaluate other products, but that was a long time ago.

I would rate this solution a ten out of ten.

We use it to store all kinds of data, both structured and unstructured.

The way that it has helped our organization is that it requires less time to manage. It's almost like a set-it-and-forget-it type of solution. We don't have to do too much maintenance. Compared to other products, it doesn't need so much babysitting. It's easy to set up and it works. It does the things it is expected to do.

In addition, it provides unified storage no matter what kind of data you have. It has multi-protocol support. It does shares and it does block, so it's a one-stop solution that can fit all of your needs. You don't need multiple solutions for your different types of data.

The most valuable features are that it's 

• reliable
• simple 
• performs well.

It also helps to keep control of storage costs.

The only issue I can think of is metrics, but I think they have improved that in the newer versions already. There should be an easy place to see all your metrics.

I've been using NetApp Cloud Volumes ONTAP for more than 10 years.

It's very stable. We haven't had any issues since setting it up. It all depends upon the disk. The faster it is, the better the performance.

It is a very scalable solution. We are looking at how we can grow in the cloud and it can definitely scale in the cloud.

The support is good in general but the initial, frontline support could be improved. Because I have already been using the product for so long, when I call support I would rather talk to somebody who is a little bit more advanced or senior, rather than talking to the first-level support. Usually, it takes some time to reach out to their senior support. The advanced support is good. The frontline support can still be improved.

Positive

We've used Dell EMC in the past. We switched because NetApp definitely provides us with multi-protocol support and it is a one-stop solution.

It's fairly easy to set up. For a new SAN it takes a couple of hours to get the setup done. The additional configurations take another three or four hours. You can get the whole thing, a new system, set up within a day so that it is ready to go to testing.

Our implementation strategy is that we use CIFS shares and NFS shares in our environment. We also have block storage for SQL and Oracle. That has been our general plan all along. We separate these protocols by virtual servers. Once the necessary cabling is done, it's a matter of setting up the network interfaces for each, provisioning some storage, and testing things out. Overall, it's fairly straightforward.

I strongly recommend the solution. The biggest advantage is that it works as expected. There's less maintenance so you don't need too many people to support it and you save money in the long run.