NetApp Cloud Volumes ONTAP Reviews

I work as a cloud architect in the multicloud team. We have customers that run NetApp services like CVS or CVO on Google or AWS or Microsoft Azure. We help them, support them, and we do migrations from their prime workflows to the cloud.

The primary use case is the migration of workloads from on-prem to cloud. We use the SnapMirror functionality to move to GCP, for example. The second use case is that we also have some file services which we need on the cloud platforms. Our customers use file services like NFS and  CIFS or SMB to address their requirements.

We save money using CVO because there is a data-tiering concept. There are algorithms that make sure that data which is frequently accessed is kept on the faster disks, and data which is less frequently accessed is stored in a cold tier. Deduplication and compression also provide storage efficiency and savings..

The feature which I like the most is that it has the capabilities that the traditional storage system offers. It provides all the functionality. The deduplication and compression work exactly like ONTAP's traditional storage. So people who have experience with that find it very easy to manage. And, exactly like the traditional NetApp system, it provides you SnapMirror and the Qtree functionality, which means you have the multi-protocol mechanism. That is something that many of the cloud-native file services do not have. 

The capacity is also flexible. You can start from a small disk and you can go with a bigger disk size.

CVO is quite well when it comes to use the file services on a cloud-native platform. 

It does have some compliance features. If a person is looking for compliance with GDPR, he can use the compliance feature provided by Cloud Volumes ONTAP. Most companies have some kind of compliance software for example, Data Custodian.A second option would be to go with the compliance feature provided by Cloud Volumes ONTAP. You can implement policies that would restrict the usage of data. NetApp doesn't control the data, the data stays with the company.

Currently, Cloud Volumes ONTAP is not a high-availability solution. When you deploy the solution it comes in single-node. It supports a single-node deployment in Google Cloud Platform, but with other cloud providers like Microsoft Azure and Amazon it does offers dual controllers deployment models. However, the RAID protection level isn't quite well designed since it is laid out at the RAID 0 level. So even though you have a dual-controller deployment in place, you do not have high-availability and fault-tolerance in place during a component failure.

NetApp has said it will come out with HA as well, but even if they come out with HA, the way CVO data protection is quite different than a traditional NetApp storage system. Hence, in my opinion It needs to be improvised with RAID protection level on CVO to have better redundancy in place.

In addition to it, when it comes to critical demanding workload or read-write-intensive application, it doesn't provide the expected performance that some of apps/DBs require for example SAP HANA Database. The SAP HANA database has a write-latency of less than 2 milliseconds and the CVO solution does not quite fit there. However, It could be quite well worked with other databases, where the requirements are not so stringent or high demanding for write-latency. I don't know if NetApp has done some PoCs or evaluation with the SAP HANA databases so they are certified to use with.

A last thing, it is an unmanaged solution, it means  someone who has no storage background or technical experience for them it's quite challenging to manage the Cloud Volumes ONTAP. They may need a NetApp managed-service model so the NetApp support team can help them to maintain or manage or troubleshoot their environment. When you deploy the solution to a customer environment, you shouldn't expect they will have some storage experience.  They might be software or application developers but this product would require them to upgrade their knowledge on the storage track. In my opinion NetApp should consider selling the solution with some add-on services model for example   CVO Manage Model support service models to support and manage customer CVO infrastructure.

I have been working with Cloud Volumes ONTAP since 2018. We are using two kinds of solutions from NetApp. One is the Cloud Volumes Services  managed cloud storage services and second one is Cloud Volumes ONTAP.

The stability is only lacking when you have a problem with the underlying subsystem and the hardware has failed. I have not encountered that problem so far. 

When doing tests for some of our LOBs, I realized that if your aggregate goes offline then you would have to do a manual failover. That means if you are using CVO for instances, like VMs or, on the on-prem world if you are doing hybrid-cloud connectivity, then you would have to unmount your disks and mount them back. That would be a disruption. 

But when it comes to overall product stability, if you don't have any underlying issues, it works fine. But if you have a subsystem level issue, then you will have a problem.

There are capacity limits. It has a maximum of 368 terabytes.

I have never used technical support from NetApp. I know people there whom I was working with two years back, and they are my points of contact if I need something. I haven't used technical support because if I have issues I directly contact the people I know. They are usually quite responsive. I have not had any problem with the support so far.

I have done the deployment end-to-end for our customers. The CVO setup is quite simple and straightforward.

You need to have a cloud account, a service account, which CVO can be used with for a cloud provider like Google. You cannot download CVO directly from the marketplace, you need to be on the NetApp website. If you have a service account already created, it will authenticate. You just feed it the information. It's a GUI interface. You just click "next" and it will ask you for the information, like "Which network do you want to deploy?" and "What is the name of your machine?" etc. I don't think anybody needs experience to do the set up.

The challenge comes with configuration, such as if you want to do a multi-protocol or an AD integration. Those things are a little bit deep. A person who has already worked on those kinds of things can easily do them. And other than that, the deployment is quite easy.

The deployment time depends on what you feed to the appliance but it should take about 20 to 45 minutes, everything included, except things such as Active Directory integrations or multi-protocols.

There are many people in our company using CVO but, from an architecture standpoint, I am the one who is helping the LOBs. Some LOBs have some experience because they have been using NetApp. But when it comes to the deployment on the cloud, they are not aware of how the service account works.

If a customer is only using, say, less than 10 terabytes, I don't think CVO would be a good option. A customer using at least 100 or 200 terabytes should get a reasonable price from NetApp.

Because we have been a NetApp customer for a long time I think we do get some discounts when we buy this solution from NetApp on a large scale, although I am not involved with the pricing side.

I work with file solutions from other vendors. We have vendors like Elastifile which I used to work with but it was acquired by Google. I also checked a Google-native solution. And Azure has file shares as well as something called NFS Blob, but it also uses the NetApp in the backend. It's a NetApp CVS. It's not like CVO, it's quite different, but it does provide the same functionality, such as file services like CIFS or NFS. But that solution lacks other things. It doesn't work like CVO because CVO provides a lot of features.

CVO provides all the functionality any customer would need on cloud. It's a single solution that covers everything.

It's not a managed solution, so a person who uses this solution should have some prior knowledge using NetApp storage. It is your responsibility to manage the solution.

CVO does provide unified storage, We use CVO's cloud resource performance monitoring. It provides you overall performance stats, such as your disk level, your egress traffic going from the disk, the read/write, random data and sequential data. But for databases, you need specific tools like DB Classify. While CVO does give you information, it doesn't give information at a more granular level. It only provides information from the disk side, such as the IOPS and the throughput you're getting. But there are other things that play a vital role, such as your instance size or type. If your instance-type  or size configuration is not properly configured or if it is fighting for resources, you won't get a good performance. In conclusion, it provides a holistic view, but when you want to drill down you need different tools to look at the subsystem level, like the DB or application level.

CVO provides quite good  file services that no other cloud provider offers so far, from what I have seen. It has all the mechanisms, such as NFS and SMB and it has multi-protocol. It does provide exactly what a normal storage system provides. The thing it misses is performance/fault tolerance. 

We use it for file services, both CIFS and NFS.

The university didn't have a centralized file service before we moved to NetApp. Now, departments can share information across 24,000 students, across 10,000 faculty and staff. They can share data without doing it through email, which was the old way.

It has definitely helped reduce the overall costs of storage. We actually started out with the IBM M-Series seven years back. We switched to NetApp. The same hardware from NetApp is a better price than it was through IBM, and the support is better. So it has reduced our expenses through that path. And since it's so easily supported, we don't need a lot of people to support it, so our support costs are lower.

We've had a lot of centralization going on. We have 13 schools, each of which had its own IT department. All those IT departments are now out of business because their work has been centralized into our department. Part of that was due to the economy changing and the school changing its business models, but that put our NetApp storage heavily into use. So it's hard to distinguish cause and effect.

I can't specify the amount of space saved, but the deduplication and compression in ONTAP are very effective. We're probably getting 35 - 40 percent savings because of dedupe and compression. And because every volume we put out is a quoted Qtree on a volume, we don't have wasted whitespace. I'm billing for 800 terabytes every single month, that's running on one petabyte of rotating disk. So, it's very good at saving me space. I'm running with about 20 percent available disk, above and beyond what I'm billing. So it's pretty good at that.

We're charging four cents per gigabyte per month and, unfortunately, I'm making money at that rate. We're not allowed to make a profit. I've been looking at reducing what we're charging our customers because it is so cost-effective.

The ability for our users to restore data from the Snapshots is very valuable.

I would like to see more cloud integration. NetApp had nothing for cloud integration about three or four years back and then, all of a sudden, they got it going and got it going quickly, catching up with the competition. They've done a very good job. NetApp's website has seen phenomenal changes, so I greatly appreciate that.

It's very stable. We've only had two outages with NetApp in seven years. One was a planned outage to fix a problem - that one was seven minutes long. The other was an unplanned failure, which caused us to be down for about five hours. Overall, we're still within our five- and six-nines of availability, so we're happy.

It's completely scalable, as long as you're willing to buy the hardware. That's why we're looking at cloud for the future, so we can stop buying hardware and maybe use the cloud instead.

It's excellent. The technical support has been very good.

One thing I find very annoying is the new web interface, where it takes you through a little AI assistant, a little robot thing, to try to answer your question first. That thing is infuriating because we've already done the research, we know we need support. Fortunately, there's a link so you can get past that quickly.

What I like about NetApp Support is that, generally, the person who takes your case is the one who works it to the end. There aren't a lot of handoffs or a lot of callbacks.

We had always done block storage and we had a large IBM infrastructure, a large ESX infrastructure, physical servers. We knew that we needed a file service, so we set that up. It was really a first for our university. We switched from IBM to NetApp because we thought we'd get better support from NetApp, and we really have. IBM did a good job, but it was obvious that IBM and NetApp didn't always play well together. IBM was slower to put out patches and fixes compared to NetApp. When IBM was telling us to go to the NetApp site to find support, we figured we'd just switch to NetApp.

The initial setup was quite straightforward because we knew what we were going to do with it and we hired Sirius on for a limited part of the job. We did most of it on our own.

I know we're providing our service very cost-effectively, and it's selling faster than we expected. Money is coming in faster than we expected and, therefore, I need to drop what I'm charging per gigabyte per month so I don't make a profit, because we're not allowed to. So it's obviously successful.

Our shortlist was really only NetApp. We looked at about a dozen other products, Hitachi and everything else, but NetApp really had the best product.

Talk to any peer you can find about what products they looked at. We spoke to a dozen peer institutions - universities, colleges - about what they were doing for file services. We found a lot that were failing and a lot that were successful. The successful ones were mostly on NetApp.

It's a very solid product. I've been using if for about seven years, and it's been mostly bulletproof. They have very good support and a very good quality hard drive.

We use it for mission-critical applications but less than we used to. A lot of our mission-critical stuff is now going out to cloud. That's why I'm here at NetApp Insight 2018, to see how we can tie this into the cloud. Absolutely, all of the university's "crown jewels" used to be on NetApp storage. Now, some have gone out to AWS and we're integrating into AWS more and more. For example, Blackboard is no longer running off out NetApp storage. It's now running out of the cloud. The same is true for all the financial stuff, all the Workday and the like. They've moved off of NetApp and out to the cloud.

In terms of machine-learning, AI, real-time analytics, and those kinds of ground-breaking apps for storage, that's more the research support side. We're not doing that. We're doing more of the general file systems support, for general-purpose use.

I don't have any opinion about NVME over Fabrics, I haven't researched it yet.

We bought our equipment through Sirius Computer Solutions, and we're very pleased with that. They care. We've had a couple different senior salespeople with them over the years and they've both been excellent. They're very committed to their customers.

I rate NetApp ONTAP Cloud at eight out of then. I won't give a ten. There's always something that's better out there, but you're going to be paying double or triple for it. For the price, the quality of the hardware, the quality of the support, the features it offers, I'm thrilled with NetApp.

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. 

We rely on NetApp Coud Volumes ONTAP for a wide range of purposes, including VMware, SQL, Oracle, and file storage. It serves as our go-to storage solution for almost every use case.

The transition to the AFF storage solution significantly improved our organization by reducing our physical footprint. We went from a FAS system with two controllers and twenty drive shelves to just four controllers and two drive shelves with the AFF. This led to substantial reductions in power consumption and space requirements in our data center.

The most valuable feature is its exceptional performance and storage efficiency. This efficiency translates to significant cost savings for us.

There is room for improvement in tier one support, especially with potential language barriers and communication challenges.

I have been using it for ten years.

We've experienced a few minor issues with stability, but we haven't encountered any significant outages.

Scalability has been a trouble-free experience. When we decided to increase our storage capacity by incorporating an additional drive shelf, the engineer collaborated with us, and the expansion process was executed smoothly, ensuring there was no downtime or interference with our production operations.

We rarely encounter performance issues, and we prefer to handle most of our troubleshooting internally. Our experience with tier-one support from NetApp has been somewhat lacking, and it varies depending on the support representative. We aim to resolve issues ourselves whenever possible, despite paying for support. On an overall scale of one to ten, I would rate the support as average.

Neutral

Over the years, we've tried various storage solutions like Nessus, Nimble, and IBM. However, about a year ago, we made the switch to NetApp, and we've been quite satisfied with their performance and have remained loyal to their products ever since.

The initial setup has been quite straightforward.

Cost reduction has been a significant benefit. We've been able to lower our expenses by minimizing the number of devices and drive shelves needed. Instead of having twenty drive shelves, we now only require two. This reduction in hardware has had a positive impact on power consumption, cooling, and maintenance costs, leading to overall cost savings.

We find the pricing to be favorable due to the educational sector we belong to.

Overall, I would rate it nine out of ten.

We use the solution on premises for files and in AWS for the target.

We are definitely in the process of reducing our footprint on our secondary data center and all those snapshots technically reduce tape backup. That's from the protection perspective, but as far as files, it's much easier to use and manage and it's faster, too.

The solution has definitely helped reduce our organization's data footprint in the cloud. The data-tiering helps a lot. I would say improving data tiering to S3 reduces our footprint by about 90-95%, which is huge. That is instead of just sitting on EBS, which is expensive storage.

The solution's Snapshot copies and thin clones is a really fast and easy method for recovery.

I think the challenge now is more in terms of keeping an air gap. The notion that it is in the cloud, easy to break, etc. The challenge now is mostly about the air gap and how we can protect that in the cloud.

So far, it has been very stable. We haven't had any downtime or other stability issues.

This product is very easy to scale.

Most of the time they're very timely. Sometimes you just need to wait, which is okay because those times are not critical issues. When we do have to wait, the response time is usually a day or two, but that's fine with that level of criticality.

I've used NetApp for many years. It's something that I know is very stable and reliable. Recommending it to the current company was an easy pass. When I joined the company we were using a different vendor. It was an EMC solution for file, but we moved to NetApp. NetApp has more storage efficiency, the Snapshot feature, and better performance when you have multiple snapshots.

It's very straightforward to set up. It was very easy and fast.

We used NetApp Cloud Manager to get up and running with Cloud Volumes ONTAP. It was very easy and there was almost nothing to do. It's just a click of a button.

We used NetApp Build Engineer to deploy. We had a good experience with them.

Definitely check out this file solution. We are using that and the cloud solution. It's something you need to see in your environment if you are not using it yet.

NetApp is nine out of ten. If we address the air gap concern, it would be a 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 are using it for storing files, to get high-performance access to files. We are also using NetApp for DR. We copy the information to the same system in other regions.

The solution's high-availability features are cost-effective for us because we are able to use the cloud benefits to reduce the cost of DR. For example, if we have it in one region, we can copy the data to another region. They keep it powered off and then they power it on for a few minutes, copy the data, send the data again, and shut it down again. That reduces the costs by approximately 80 percent.

Similarly, the data protection provided by the solution's disaster recovery technology is cost-effective and simple.

We're using Cloud Manager to automate some of the management. We use it for bringing the DR environment up and down as well as for scheduling data synchronization between different regions, worldwide. It's almost impossible to do that manually. Compared to an engineer doing it manually, it's about 90 percent faster. That's specifically for this kind of operation. In reality, the automation is enabling such capabilities. It's not actually reducing the time taken. If it didn't exist, we would never do it. That's even better than saving time.

Overall, NetApp has standardized and certified file services, both on-prem and in the cloud, corporate-wide. In addition, by using the automation, it has provided us cost-effective DR and management. In the cloud it has enabled us to provide tailor-made storage solutions for each of our cloud customers. The storage efficiency has reduced our storage footprint because we are offloading all the data to the storage account. So it has reduced the cost of corporate storage. And the data-tiering has also saved us money.

What is most valuable is that the system is the same as what we use on-prem. So the guys who are responsible here for managing NetApp feel comfortable with it& and that they have enough knowledge to manage the system in the cloud. We are able to& keep the same standards that we have on-prem in the cloud.

The usability is& great. We don't have any issues with it.

We're using snapshots as well and it's a pretty useful feature. That is one of the main NetApp benefits. Knowing how to use snapshots in the on-prem environment, using snapshots on the cloud solution was natural for us.

The DR has room for improvement. For example, we now have NetApp in Western Europe and we would like to back up the information to another region. It's impossible. We need to bring up an additional NetApp in that other region and create a Cloud Manager automation to copy the data. So we do that once, at night, to another region and then shut down the destination. It's good because it's using Cloud Manager and its automation, but I would prefer it to be a more integrated solution like it was in the NetApp solution about a year ago. I would like to see something like AltaVault but in the cloud.

We have been using it for about half a year in production; longer when we include the PoC.

The stability has been great. We haven't had any issues.

We still haven't needed to scale up, but I think the scalability is good.

We are using it for a system which stores files and parts of databases, but the system is used by hundreds of customers. NetApp is not used directly by them, rather through the system. We may plan to increase NetApp according to the usage of the system but we still have no specific plans.

We are using NetApp engineers and they are great.

Before NetApp we used a home-grown server in the cloud, a Linux server with a big disk. It was less simple to manage.

We're also using Avere, a storage solution that was purchased by Microsoft a month or two ago. It's mainly responsible for real-time data synchronization between on-prem and the cloud environment. It's different than NetApp which doesn't provide the kind of synchronization solution that Avere does. It's two-way, real-time data synchronization between the Oracle storage solutions which we have on-prem and the Avere solution that we have in Azure. NetApp does not help with such requirements.

The initial setup was very simple. It was quite easy to set up the environment in just one day. We started with a small implementation and then added more and more parts of the solution. We started with just one desktop and then added additional ones and then added tiering.

It required a small number of staff members. That's all we needed because it was pretty simple. We did a few sessions online and one or two onsite, for the entire solution. For our specific case it requires almost no maintenance. It only requires management to expand the disk capacity or perform the management operations, per-request. Generally we wouldn't require an increase to our storage team to manage the solution.

We used a NetApp engineer to help us.

In addition to the standard licensing fees, there are fees for Azure, the VMs themselves and for data transfer. The DR environment is billed by the hour and paid to Azure directly and NetApp is paid on a yearly license.

We checked Dell EMC and HPE but we chose NetApp. The Storage team made the decision. One of the main reasons they chose NetApp was the existence of NetApp on-prem and the knowledge of it the team had. We are familiar with NetApp and the products are good, so we decided to extend the success to the cloud as well.

Implement it. Do not think about it. It's very simple and very useful.

We use CVO for NFS data storage, NFS sharing, and SMP sharing.

CVO helped us migrate to the cloud. We were already using the same software on-prem. We just migrated it to the cloud, so it helped us with that. 

The workload migration was outstanding. It was seamless. We have on-premise CVO within BlueXP. We just drag and drop the on-premise workload to the cloud workload. It just migrated and cut over. That was it. The time required depends on the volume size. Our largest volume took us three-and-a-half weeks. It takes some time to migrate the data from on-prem to the cloud. 

We have on-prem NetApp AFF, and we're looking into using NetApp Data Sense or Blue XP Data Sense for the backup servers as well. Everything integrates perfectly. We have some on-prem workloads that run on NetApp, and CVO on a cloud. We can migrate between the two if needed.

Snapshots are one valuable feature within ONTAP, but CVO's appeal is that it acts just like the on-prem solution. It's the same OS, but in the cloud. We can continue to use ONTAP as we did on-premise. 

I would want more visibility and data analytics where we can see anomalies within the shares within the GUI.

I have used CVO for four years.

CVO is highly stable, and the performance has met our expectations. It does exactly what it needs to do.

Scaling CVO is straightforward. It's super easy to grow the cloud environment compared to the on-prem solution. It's easier to scale.

I've had no issues with NetApp support so far. It's been excellent.

We had the on-premise version of ONTAP. We also have a Nutanix array for our hypervisor. 

I've set up four NetApp CVOs. They all took around five minutes to set up. It's super easy.

The licensing is good. They make it easy for you. You go to the sizing site. It's a bar that you drag and drop.

I rate NetApp Cloud Volumes ONTAP nine out of 10. If you're a fan of the on-prem version, you'll like CVO on the cloud.