NetApp Cloud Volumes ONTAP OverviewUNIXBusinessApplication

NetApp Cloud Volumes ONTAP is the #1 ranked solution in top Cloud Storage tools, #1 ranked solution in top Cloud Software Defined Storage tools, #2 ranked solution in top Cloud Migration tools, #4 ranked solution in top Public Cloud Storage Services, and #8 ranked solution in top Cloud Backup tools. PeerSpot users give NetApp Cloud Volumes ONTAP an average rating of 8.8 out of 10. NetApp Cloud Volumes ONTAP is most commonly compared to Azure NetApp Files: NetApp Cloud Volumes ONTAP vs Azure NetApp Files. NetApp Cloud Volumes ONTAP is popular among the large enterprise segment, accounting for 65% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 25% of all views.
NetApp Cloud Volumes ONTAP Buyer's Guide

Download the NetApp Cloud Volumes ONTAP Buyer's Guide including reviews and more. Updated: November 2022

What is NetApp Cloud Volumes ONTAP?

The leading enterprise-grade storage management solution, delivers secure, proven storage management services and supports up to a capacity of 368TB. Software service supports various use cases, such as: File shares and block-level storage serving NAS (NFS, SMB / CIFS) and SAN (iSCSI) Disaster Recovery, Backup, and Archive DevOps Databases (SQL, Oracle, NoSQL) Cloud Volumes ONTAP is offered in a standard single-node configuration or in a High Availability (HA) configuration.

NetApp Cloud Volumes ONTAP was previously known as ONTAP Cloud, CVO, NetApp CVO.

NetApp Cloud Volumes ONTAP Customers

Rohit, AdvacnedMD, D2L, Trinity Mirror, Eidos Media, WireStorm, Cordant Group, JFK Medical Center, ALD Automotive, Healthix, City of Baton Rouge, ON Semiconductor

NetApp Cloud Volumes ONTAP Video

NetApp Cloud Volumes ONTAP Pricing Advice

What users are saying about NetApp Cloud Volumes ONTAP pricing:
  • "If we wanted to use the AWS solution, we would have to manage two or three different platforms and pay more money than what we should have to pay, as some of the features don't even exist. If we wanted to, we could use AWS cloning, but it is useless because it uses more space, is more expensive, and takes more time."
  • "The pricing of this solution is definitely higher than what the typical Azure Files and AWS solutions charge, but given the features and the stability NetApp has provided, we are okay with it. We are not complaining about the pricing."
  • "It is expensive. There are no costs in addition to their standard licensing fees."
  • "Overall, the pricing of NetApp is aggressive and the pricing becomes more aggressive as the amount of data increases. The cost for a given volume of data that you are storing becomes lower. The greater the volume of data, the cheaper the license."
  • NetApp Cloud Volumes ONTAP Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    John Boncamper - PeerSpot reviewer
    Technology Consultant at a tech services company with 501-1,000 employees
    Reseller
    It's easy to set up and schedule replications from the cloud manager
    Pros and Cons
    • "The Cloud Manager application that's on the NetApp cloud site is easy to use. You can set up and schedule replications from there, so you don't have to go into the ONTAP system. Another feature we've recently started using is the scheduled power off. We started with one client and have been slowly implementing it with others. We can cut costs by not having the VM run all the time. It's only on when it's doing replication, but it powers off after."
    • "Cloud Volumes ONTAP's interface could use an overhaul. Sometimes you have to dig around in Cloud Manager a little bit to find certain things. The layout could be more intuitive."

    What is our primary use case?

    Cloud Volumes ONTAP is used for disaster recovery right now, and the primary use case for our current clients and environments is CIFS. Most clients use Cloud Volumes ONTAP as a replication destination for CIFS. It's a way to back up their documents and files offsite for disaster recovery. They have VMs that they spin up and connect to. 

    In most cases, we have not deployed anything that uses the service protocol, like iSCSI or NFS. It's strictly CIFS. We haven't used one solution—matching DR for CIFS volumes—which is a destination that replicates from on-prem to the cloud, but we've done DR tests with that. 

    The other two instances we're currently running will be the same scenario, but we're not there yet. Right now, they are being used for SnapMirror destinations of CIFS volumes only, and that's all three. We've been running Cloud Volumes ONTAP in Azure as a VM along with a connector. They had one deployed before I took it over, but it's typically done within the NetApp Cloud Manager system. Once we connect to the Azure portal or subscription, we push out the CVO from there.

    How has it helped my organization?

    Our clients see most of the benefits. Cloud Volumes ONTAP provides offsite backups. We used to host our backups on physical infrastructure in a data center or on remote sites. There were a lot of storage costs for replication. By implementing Cloud Volumes ONTAP in the Azure portal, we eliminated the cost of additional hardware and everything you have to maintain on-prem in a physical environment and put it up to the cloud. That was a considerable cost savings for the customer.

    Cloud Volumes ONTAP is a massive improvement in terms of manageability. It's easier for customers to perform certain functions from that interface, knowing it sits on a high availability platform. We don't worry about paying all these separate vendors for replication solutions. Other costs are associated with maintaining physical infrastructure in a data center, like electricity or storage space, RAM, and other hardware. It has improved our clients' bottom line because they spend less on disaster recovery.

    What is most valuable?

    The Cloud Manager application that's on the NetApp cloud site is easy to use. You can set up and schedule replications from there, so you don't have to go into the ONTAP system. Another feature we've recently started using is the scheduled power off. We started with one client and have been slowly implementing it with others. We can cut costs by not having the VM run all the time. It's only on when it's doing replication, but it powers off after.

    What needs improvement?

    Cloud Volumes ONTAP's interface could use an overhaul. Sometimes you have to dig around in Cloud Manager a little bit to find certain things. The layout could be more intuitive. 

    Buyer's Guide
    NetApp Cloud Volumes ONTAP
    November 2022
    Learn what your peers think about NetApp Cloud Volumes ONTAP. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    656,862 professionals have used our research since 2012.

    For how long have I used the solution?

    I haven't been using NetApp Cloud Volumes ONTAP for too long. It has been a little under three years since we started working with it. We were mostly doing a lot with data centers, so we only really started getting into cloud systems about three years ago.

    What do I think about the stability of the solution?

    Cloud Volumes ONTAP seems to be fairly stable so far. The only time we have issues is when there is a circuit interruption, but this product has been pretty stable. We haven't had issues with crashes or data getting corrupted. We've had interruptions due to internet problems or leaks between the sites. 

    These are things we have no control over because they're different providers. That's the only issue that I've seen. But once those come through the actual system itself, it's been fine as far as resiliency, performance, and availability.

    What do I think about the scalability of the solution?

    We can expand on it as needed. In particular, it's easy to add storage, and storage expansion is probably the feature we utilize the most. We don't mess with any other features, like within the protocols or anything like that. Those are fine, but storage scalability is pretty good.

    Our clients' storage needs vary. Typically, it's somewhere in the range of 20 to 30 terabytes, but at least 15 to 30 terabytes. Each client is a little different, but the one that uses the most storage has a capacity of about 30 terabytes.

    How are customer service and support?

    NetApp technical support is pretty good. We sometimes have to wait a bit, but they're good at resolving issues once they find out what the problem is. They come back with solutions, so I would rate them pretty well.

    How was the initial setup?

    Deploying Cloud Volumes ONTAP can be complex at times, but I think it's a learning curve. You have to put in many different pieces, and it's not always easy to find the documentation you need on the web. Some parts are straightforward, but sometimes you need to do some digging before deploying. 

    It really comes down to planning. When implementing, we ensure each case is planned and deployed to the networking part for Azure. We also put together a template. That way, other engineers can follow or use it as a guideline when building it. I make a basic template of the required information, configuration settings, etc. 

    These were all deployed as part of a much larger project, which included new hardware that was upgraded. The Azure and NetApp Cloud Volumes ONTAP were part of that upgrade experience. It was in conjunction with the client getting a new on-prem NetApp system and other infrastructure, like switches. Once everything was migrated, we implemented the Azure part in Cloud Volumes ONTAP.

    We have a small team for handling deployment. I think they have maybe two people. One person could do it, but there is an alternative if somebody is out on vacation. The managed service division covers all the maintenance for our clients. The managed service team takes over all the backend IT work for our clients. Instead of having a full staff, the client pays us to manage the backend of their servers and other infrastructure. As a managed service, we go in and take care of their switching, patches, upgrading, etc.

    What about the implementation team?

    We do all of the implementations for our clients in-house who are the end-users. We sell them the solution and deploy it for them.

    What was our ROI?

    I believe our clients see a return because they don't need to purchase hardware. It's much easier and quicker for them to get additional storage when needed compared to an on-prem system. 

    They save on costs associated with ordering additional storage for a physical on-prem system versus expanding what you have and you pay a little more in Azure. One client saw significant cost savings on their electricity bill. They reduced their bill by almost half just by shutting these things off.

    What's my experience with pricing, setup cost, and licensing?

    Our management and salespeople deal with pricing. I'm not part of the price negotiations or anything like that. I work on design and implementation.

    What other advice do I have?

    I rate Cloud Volumes ONTAP nine out of 10. It's an excellent solution that is cloud-based, so you don't have to worry about leasing or purchasing hardware. All costs of purchasing lines and circuits are upfront. Since this product works over the internet, you only need data access, which most of them have. 

    Overall, I would say this is better than an on-prem solution that requires physical hardware at remote sites. You don't need to invest in buying or maintaining physical hardware. In this case, you're paying a monthly cost for something. You can decide at any time to stop using it if you don't need it anymore. That's a problem with owning physical infrastructure. You have to dispose of it when you don't need it anymore. Cloud Volumes ONTAP is also easier to manage and upgrade than on-prem systems.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    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. The reviewer's company has a business relationship with this vendor other than being a customer: Reseller
    PeerSpot user
    Lead Storage Engineer at a university with 10,001+ employees
    Real User
    Easier to control data since we can run queries across all our platforms with a single solution
    Pros and Cons
    • "It is much easier to control data since we can run queries across all our platforms with just one solution. Not only that, we can also monitor all the platforms with Active IQ, where we can see all the alerts, messages, and space consumption through a single application. This is regardless if the data is on-prem or AWS. It is much more efficient."
    • "The solution is not stable when using single nodes. This is a problem. NetApp should work on this solution to make it more stable with HA nodes and resolve this issue."

    What is our primary use case?

    We use it for multiple cases. We use it for DR and backup tiering. 

    We have some Oracle Databases in AWS that need backing up. We back them up to CVO. From CVO, we tier them out in a FabricPool scenario, then tier them off to StorageGRID. This way, we are putting minimum space on CVO, which has expensive storage. Instead, we are pushing them on a stream. This is really efficient in terms of performance and backup. I like it because we are able to restore quickly. 

    We also use this for dev test data. For Oracle database, we are putting the data file for Oracle Database on a CVO data file. This way, we are able to replicate and clone the Oracle Database very quickly and efficiently with minimal space consumption.

    How has it helped my organization?

    It is much easier to control data since we can run queries across all our platforms with just one solution. Not only that, we can also monitor all the platforms with Active IQ, where we can see all the alerts, messages, and space consumption through a single application. This is regardless if the data is on-prem or AWS. It is much more efficient. 

    What is most valuable?

    The number one feature is the solution's space saving, which is great. 

    They are on AWS and Azure. Because we use both cloud options, we have access through them from everywhere. It is a big colo facility, where we can have access to our data wherever we want. 

    We use NetApp technology for deduplication and compression as well as the cloning technology and Snapshot. This usually helps us to restore everything. It is really helpful.

    It is a unified solution for storing data across the board. This data fabric lets us have data across the board.

    What needs improvement?

    NetApp has a big problem with the HA pair model on this solution. If you want to use it with CVO, you need to run lots of tests. The problem with HA pair and CVO is that it has a huge impact on performance. We also can't use HA pairs with CVO because the cost is higher. It is really more expensive than a single node since you have to pay for the data twice, using their single-node solution with an AWS or Azure data center and causing redundant data. We have had many meetings and discussions with our NetApp account manager and their engineers about this issue since we can't have redundant data. 

    Since it is too expensive, we haven't implemented the HA pair solution. Since we don't have an HA pair solution, we make the trade off of data loss. This happened once. We were lucky that we didn't lose data because we were able to recover it.

    For how long have I used the solution?

    We were one of the first customers. We have been using Cloud Volumes for a long time. I think that it has been five years.

    What do I think about the stability of the solution?

    The solution is not stable when using single nodes. This is a problem. NetApp should work on this solution to make it more stable with HA nodes and resolve this issue.

    What do I think about the scalability of the solution?

    NetApp has to make improvements on the scalability. It is not really scalable for a bigger scope because of many reasons. NetApp is limited to using six disks and the biggest disk size that they can use is just 16 terabytes. Six disks with 16 terabytes is not enough for a big environment. Right now, NetApp CVO can accept 350 terabytes, but it is 350 terabytes including tiering. In many cases, this is not enough for big data.

    How are customer service and support?

    Initially, technical support was not good at all. We were one of the first customers and couldn't get any support from NetApp in the beginning. Then, we had to communicate with the guys from Israel through Slack, which was so difficult. In the beginning, I would rate the technical support as two or three out of 10.

    Within the last year, it has gotten much better. Based on my experience, they help quickly every time that I call, which is great and more solid than before. I would now rate their technical support as seven out of 10.

    How would you rate customer service and support?

    Neutral

    Which solution did I use previously and why did I switch?

    This was the first solution that we used. We were one of the first customers. There were very few options for solutions back then to utilize cloud storage.

    How was the initial setup?

    The initial setup was great. It was so easy and straightforward. Everything was automated with no confusion.

    What was our ROI?

    It has saved us a lot of money. If we don't use it and want native AWS, then we have to pay three or four times more. 

    We are also using it for other use cases. We use CVO for replicating product data to the dev test environment in AWS with a SnapMirror technology, using data from CVO to the dev test environment in AWS data using SnapMirror. This is much faster than any other solution that you can imagine for moving data from on-prem to AWS. We tried many methods, including some native AWS methods. We tried FTP server, file transfer, etc., but none of them were as fast and as quick as SnapMirror replication.

    When we store more data with the solution, we can save more money. The savings depends on how many copies we make of each stage of the environment. If we need to clone the environment four times, then we save a lot of money. If we have to clone the data 10 times, then there are huge savings.

    Which other solutions did I evaluate?

    We evaluated AWS and Azure file transfers for replicating data between on-prem and cloud. We also tried AWS and Azure native volumes for cloud and those solutions were much better. 

    The reasons that we went with NetApp:

    1. The data fabric technology created a single standard for everything.
    2. Cost.
    3. Our familiarity with it. We didn't have to learn anything new.

    If we wanted to use the AWS solution, we would have to manage two or three different platforms and pay more money than what we should have to pay, as some of the features don't even exist. If we wanted to, we could use AWS cloning, but it is useless because it uses more space, is more expensive, and takes more time.

    What other advice do I have?

    We use NetApp storage when we want to use NFS methods. If we don't have to use an NSF method, then we use native cloud sets. So, we use both.

    I recommend using this technology for now as there isn't another technology that can cover transferring data across sites, provide reliability of data, money savings, and space savings. If you want to compare these factors with any other solution, then NetApp is the best for now.

    I would rate the solution as eight out of 10 because they still have to work on the HA pair issue.

    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.
    PeerSpot user
    Buyer's Guide
    NetApp Cloud Volumes ONTAP
    November 2022
    Learn what your peers think about NetApp Cloud Volumes ONTAP. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    656,862 professionals have used our research since 2012.
    Sandeep Gawde - PeerSpot reviewer
    Principal Enterprise Architect at a computer software company with 10,001+ employees
    Real User
    Top 10Leaderboard
    Real-time dashboard is excellent for providing support and helps with decision-making at business level
    Pros and Cons
    • "In terms of administration, the portal which provides the dashboard view is an excellent tool for operations. It gives you volume divisions, usage rates, which division is using how much data, and more. The operations portal is fantastic for the support team."
    • "The only area for improvement would be some guidance in terms of the future products that NetApp is planning on releasing. I would like to see communication around that or advice such as, "Hey, the world is moving towards this particular trend, and NetApp can help you do that." I do get promotional emails from NetApp, but customer-specific advice would be helpful, based on our use cases."

    What is our primary use case?

    We store our user documentation repository in NetApp. We are serving multiple divisions, and there are use cases grouped by divisions, by user access rights, et cetera. We also have specific requirements for the backups and restores.

    How has it helped my organization?

    The main use case for us in going with Cloud Volumes ONTAP was to ensure the IOPS or performance. There are other solutions available that are probably more cost-effective than NetApp, but given the criticality of our application, the performance expectations, and the availability, those were the factors that helped us to zero in on the NetApp solution.

    What is most valuable?

    In terms of administration, the portal which provides the dashboard view is an excellent tool for operations. It gives you volume divisions, usage rates, which division is using how much data, and more. The operations portal is fantastic for the support team.

    Cloud Volumes ONTAP provides unified storage, no matter what kind of data you have. In terms of our data, it's mainly Word and PDF files, but we have a specific use case where applications are using XML files for document management.

    What needs improvement?

    The only area for improvement would be some guidance in terms of the future products that NetApp is planning on releasing. I would like to see communication around that or advice such as, "Hey, the world is moving towards this particular trend, and NetApp can help you do that." I do get promotional emails from NetApp, but customer-specific advice would be helpful, based on our use cases.

    For how long have I used the solution?

    We started using NetApp Cloud Volumes ONTAP in production in April of this year. But we had been working with the NetApp team before that, from October of 2020, to get the configuration right in the test environment. Overall, we have been using it for about one year and two months.

    What do I think about the stability of the solution?

    There has been just one incident since we started using it, in which a node refresh needed to be done. The stability is pretty good with only one incident in 14 months. We're pretty happy with that.

    What do I think about the scalability of the solution?

    We have been pretty impressed with the scalability because when we started, we had to immediately onboard two more divisions and it was pretty straightforward, once we had the base setup going. We were able to scale it up pretty quickly and we were able to do it on our own.

    We are using Cloud Volumes ONTAP daily. Our departments are copying the files on it and sharing them. It's a part of their daily work.

    At the project level, we are not looking to expand our usage of NetApp, but at the organizational level, there are plans. They are looking at additional use cases that can be  onboarded to NetApp.

    How are customer service and support?

    After we deployed we had a couple of queries in terms of optimizing uses. We raised a support ticket and the help was available within a couple of hours. They had people on a call supporting us.

    We're pretty happy with the support we're getting and with our account manager. Everyone is prompt in responding, so we're quite happy.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    We used a typical Windows file share. Then, when we moved to the cloud, we worked with Azure Files. But in terms of performance and stability, we found that NetApp was way ahead of the other solutions.

    How was the initial setup?

    Overall, the setup process was excellent. It was pretty straightforward but we also had NetApp engineers available and dedicated to us on a call when we were setting it up. To help us get going, there was tremendous support available, which was good.

    The setup time was about six hours and there were about two hours during which we had conference calls with the NetApp team. 

    What about the implementation team?

    The NetApp team was very helpful. The engineers worked with us to understand our use cases and advised us on the configurations. They weren't just checking what we were doing but were contributing to the overall setup. That was a good experience.

    What was our ROI?

    It's too early to comment on ROI because we're just a little more than one year into a five-year business case. We'll probably see a return in the third or fourth year.

    What's my experience with pricing, setup cost, and licensing?

    The pricing of this solution is definitely higher than what the typical Azure Files and AWS solutions charge, but given the features and the stability NetApp has provided, we are okay with it. We are not complaining about the pricing.

    Which other solutions did I evaluate?

    We looked at Azure Files and the Amazon EFS file system.

    The pros for NetApp were definitely the stability, performance, and availability, out-of-the-box. Even Cloud Volumes ONTAP can be set up in HA. With Azure as well as AWS, you have to have your own custom solutions on top of them. Another advantage with NetApp is the admin portal which has a very good dashboard. Because it gives a good view of usage in real time, decisions become easier for the business.

    The only challenging part that we faced with NetApp was that it would have been good to have a sandbox available for a PoC scenario. Without it, what we had to do was get a trial license and set it up. With Azure and AWS, you go directly to the console and just provision it. With NetApp, we had that initial period where we had to set it up on a trial license for a month, and when that was getting close to expiring, we had to extend it.

    What other advice do I have?

    First and foremost, test the use cases where you need availability and performance as the key drivers for a solution. In those scenarios, NetApp is way ahead compared to what the competitors offer. But given the cost of the other solutions, there has to be a three- to five-year view if you are going to go with NetApp. You will not see a return on your investment after six months or one year.

    I'm happy with the way it is handling our use cases and meeting our performance requirements.

    Which deployment model are you using for this solution?

    On-premises
    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.
    PeerSpot user
    Senior Systems Engineer at Cedars-Sinai Medical Center
    Real User
    You don't need to spend time and resources planning and setting up physical storage equipment in your data center
    Pros and Cons
    • "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."
    • "The encryption and deduplication features still have a lot of room for improvement."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

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

    For how long have I used the solution?

    We first deployed Cloud Volumes ONTAP four years ago.

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

    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. 

    How was the initial setup?

    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. 

    What about the implementation team?

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

    What was our ROI?

    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.

    What other advice do I have?

    I rate NetApp Cloud Volumes ONTAP nine out of 10. 

    Which deployment model are you using for this solution?

    Hybrid Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Junaid Maumdar - PeerSpot reviewer
    Principal Devops engineer at a tech services company with 1,001-5,000 employees
    Real User
    Good file sharing and extra security with great flexibility
    Pros and Cons
    • "ONTAP is great for helping you migrate on-premise workflows to cloud environments."
    • "The cost needs improvement."

    What is our primary use case?

    The solution is for file sharing and networks. If we have a cluster in a network, for example, two servers needed to use a common file, NetApp is a good tool. You can spin up a network from the other cluster, so if your application is a multi-node cluster and you need a common place to share the drag with, you can use NetApp for that. 

    How has it helped my organization?

    At the time we implemented it, there wasn't any other solution. We needed a cluster, and we needed a common place where both nodes can share a file. There was not a good solution at that time besides NetApp. Now, there is. There's EFS. EFS is for Linux only. NetApp works for Windows. However, now, AWS is competing with NetApp with FSx. However, NetApp also has a feature for FSx.

    What is most valuable?

    The cluster needs to use a common file share, so NetApp just does that.

    They provide extra security, backups, and many other features with it. 

    One of the most important aspects is the flexibility to expand it. It's very scalable. 

    We can easily file share with AWS. 

    ONTAP is great for helping you migrate on-premise workflows to cloud environments. I would rate it a solid eight out of ten. It does what it's supposed to do. It was just expensive.

    My impression of ONTAP against native AWS integrations is that FSx is much cheaper. That said, NetApp has more flexibility. Therefore, it is competitive against AWS. NetApp has an advantage in its class, and FSx has an advantage in terms of its low cost. FSx just lacks features.

    In terms of ONTAP integrations with AWS native services like AWS Backup, NetApp uses AWS, so in a way, it's already backed up. If you want to provision one terabyte being backed up, they would provision ahead of time, so that way you protect your data. 

    What needs improvement?

    The cost needs improvement. Cost should go down. If you have a company with many servers, then the cost is down. However, if you're in a situation where you only need it for one function, then the cost can be overwhelming.

    For how long have I used the solution?

    I've been using the solution for two years. 

    What do I think about the stability of the solution?

    It's pretty reliable. It's an HA solution, so even if one cluster goes down, another cluster can support everything.

    What do I think about the scalability of the solution?

    The solution is extremely scalable. For example, if you initially subscribe to one terabyte, and then all of a sudden, you need two terabytes, you can dynamically expand it. You can add a feature within NetApp, and it will automatically increase it for you. You never have to worry about the space getting out of control.

    How are customer service and support?

    Technical support is not bad. NetApp does a lot, quietly in the background. I don't even have to look for support for the most part. In most cases, when I do look for support assistance I get my questions answered. 

    They could improve their response time. Once, there was an AWS outage and it took a long time to get a response. 

    How would you rate customer service and support?

    Neutral

    Which solution did I use previously and why did I switch?

    We started using this solution before AWS developed its own tool called FSx. It's very similar to FSx. However, NetApp provides even more features than FSx does.

    NetApp is a multi-cluster. Like FSx, the cluster is controlled by AWS itself, so you don't see that background feature. Unlike NetApp, all the deployment is in our control, so we can use that. Then there was a node feature that you can get with NetApp support in addition to the cloud support. Those are the key features. It's a little more expensive than FSx. However, there are good reasons for it.

    We've been using NetApp for a while, so we'll just stick to it.

    How was the initial setup?

    The initial setup was extremely easy. It was extremely simple to set up; it's a couple of clicks of a button, and it will then have an HA cluster for you. That's one of the good features of NetApp, the ease of setup.

    What about the implementation team?

    I deployed the solution basically by myself.

    What was our ROI?

    We needed an HA solution, which we got from NetApp, so that's the only return we've received. Otherwise, we would have to go with another risky option. We do now have the option of moving over to FSx as well.

    What's my experience with pricing, setup cost, and licensing?

    Cost-wise, ONTAP is a bit high.

    Which other solutions did I evaluate?

    We looked into FSx, which came out after implementing NetApp. We tried to use the AWS NetIQ solution with the EFS. That said, their EFS is only for Linux. There was a way to do EFS for Windows also by using Samba Share, yet that gets a little bit complicated and unreliable, so we chose NetApp at that time to keep things simple.

    What other advice do I have?

    We have not reduced the amount of our storage with ONTAP. That was not our intention. We are not using NetApp to reduce our storage costs. We needed a reliable HA solution; that was our main goal.

    We have not reduced any costs by using ONTAP. With our services, we are only using them for one thing. If we start using the product for many other functions, it's definitely a good solution. So we are trying to find other use cases for NetApp. The more we use it, the more we reduce costs.

    NetApp does offer a ransomware solution, which AWS NetIQ does not offer yet. That said, we haven't faced an issue with ransomware yet. Still, that is one of the key features of NetApp that AWS does not provide yet.

    I'd rate the solution eight out of ten. I'd rate it higher if the price were cheaper. 

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Senior Systems Engineer at a computer software company with 10,001+ employees
    Real User
    Top 20Leaderboard
    Cloud Manager is a nice tool for managing the environment, and we can easily pair on-prem with the cloud and the cloud backup feature
    Pros and Cons
    • "I like how you can easily pair on-prem with the cloud and the cloud backup feature. I like the whole integration with on-prem and the cloud for SnapMirror relationships."
    • "They definitely need to stay more on top of security vulnerabilities. Our security team is constantly finding Java vulnerabilities and SQL vulnerabilities. Our security team always wants the latest security update, and it takes a while for NetApp to stay up to speed with that. That would be my biggest complaint."

    What is our primary use case?

    We are using it for Virtual Desktop Infrastructure in AWS. I believe we're using the latest version.

    How has it helped my organization?

    We were able to move our VDI environment into AWS. It has been a big performance boost. It has helped our customers all around the globe access virtual desktop.

    Upgrades are much easier in terms of upgrading ONTAP. It is so much easier with CVO.

    It provides unified storage and gives us better access to our data. We're able to manage it. I don't really see that any different than the on-prem solution, but it does give us the ability to manage access and permissions.

    CVO enables us to manage our native cloud storage better than if we used management options provided by AWS. That's because we're more familiar with ONTAP. So, it is not like we had to change how we manage storage. That was the big thing, and it has an easier user interface. Managing AWS storage is also pretty easy, but to me, the easiest thing was the fact that we're familiar with ONTAP.

    What is most valuable?

    I do like the cloud manager. It is a nice way of managing our environment. It definitely is a nice tool to do basic ONTAP tasks such as setting up backups, creating volumes, and managing permissions.

    I like how you can easily pair on-prem with the cloud and the cloud backup feature. I like the whole integration with on-prem and the cloud for SnapMirror relationships. 

    I like the backup feature because it is all SaaS, and it is easy to set up. My data is encrypted in transit. 

    The compliance feature is also good, but we haven't used it yet. From what I've seen in the demos, it is really a nice feature. I like the fact that we can analyze our data. We can do data analysis with artificial intelligence and categorize data. 

    What needs improvement?

    They definitely need to stay more on top of security vulnerabilities. Our security team is constantly finding Java vulnerabilities and SQL vulnerabilities. Our security team always wants the latest security update, and it takes a while for NetApp to stay up to speed with that. That would be my biggest complaint.

    For how long have I used the solution?

    We have been using this solution for two years.

    What do I think about the stability of the solution?

    I haven't had a problem yet.

    What do I think about the scalability of the solution?

    We have not had a scalability issue, so it scales easily. We are using about 20 terabytes. We have about 200 people who are using it on a day-to-day basis. They are mostly from the finance team.

    We have plans to increase its usage. We are investigating it. It is all based on the business.

    How are customer service and technical support?

    I've had many support cases. Sometimes, it takes a while for them to give me a solution that works. Sometimes, they give me a solution that works, but it depends on the problem. I would rate their support a seven out of 10.

    Which solution did I use previously and why did I switch?

    We were using NetApp, so we were using NetApp arrays. The main reason for switching was that we wanted to move our VDI environment into AWS. So, the main reason was to use the NetApp in AWS. One of the reasons why we went with Cloud Volumes ONTAP was that it was easy to migrate our on-prem solution into AWS because of SnapMirror.

    We worked with Amazon FSx for a little bit, but it wasn't really ready yet. It was just released, so we decided to stick with CVO.

    How was the initial setup?

    It was straightforward, but we were mandated to use Terraform. So, I had to create a Terraform code, but it was easy to set it up. It takes a couple of hours to just set it up if you know what you're doing, but planning, designing the application, and everything else took about three months.

    We had an on-prem solution running on arrays, and we wanted to move our VDI infrastructure into AWS. In terms of the implementation strategy, first of all, we wanted to figure out the kind of array and what can we do in terms of ONTAP to make it work. We had to set up a PoC and get some test users and a VPC in place. We had to get security rules and security in place. So, there was a lot of stuff just besides ONTAP. Obviously, we needed to get the whole cloud infrastructure in place to support the VDI users, and CVO was just one part of this project.

    What about the implementation team?

    I did it myself.

    What was our ROI?

    Our users are happy, so I guess that's a good return on our investment.

    What's my experience with pricing, setup cost, and licensing?

    It is expensive. There are no costs in addition to their standard licensing fees.

    What other advice do I have?

    My advice would be to go for it. It is a great product. It is a great piece of software. NetApp is cutting edge when it comes to software in the cloud. I don't really have any warnings.

    I don't know if we're saving more money by putting in more data. It does have tiers, and I guess there is data reduction that does help us save more money. We're using cloud on CVO, and we take advantage of reduction capabilities that do help us. 

    I would rate this solution a nine out of 10.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    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.
    PeerSpot user
    Technology Advisor Director at a tech services company with 11-50 employees
    Reseller
    Snapshots and multi-cloud dictionary reduce data replication and saves on costs
    Pros and Cons
    • "One of the features our customers like is that it can be used from one cloud provider to another. They can use it from Azure to AWS or vice versa. That way, they don't need to use the same provider for backups. If something goes wrong on the primary site, having the same data in another cloud service provider is important."
    • "We have customers that are still using IBM mainframes and that very old SNA architecture from IBM. There are questions about how you interconnect the data on the mainframe side... But I don't know if it's worth it for NetApp to invest in developing products to include mainframes for a few customers."

    What is our primary use case?

    Generally what we show our customers are possibilities for using Cloud Volumes ONTAP for multi-cloud environments, to do disaster recovery and to back up sites.

    Our company provides backup and DR professional services. We allocate people to support our customers' needs in these areas. We implement the solution that the customer requires.

    How has it helped my organization?

    By creating snapshots and a multi-cloud dictionary, the solution doesn't have to replicate all the data. The dictionary can point to some of the data on another site and create a correspondence between sites. It's going to lower the storage cost. For example, it saves my clients between 50 and 60 percent.

    What is most valuable?

    One of the features our customers like is that it can be used from one cloud provider to another. They can use it from Azure to AWS or vice versa. That way, they don't need to use the same provider for backups. If something goes wrong on the primary site, having the same data in another cloud service provider is important.

    What needs improvement?

    We have customers that are still using IBM mainframes and that very old SNA architecture from IBM. There are questions about how you interconnect the data on the mainframe side. Those requirements are just for our big customers. We have one, here in Brazil, that is very big that uses a lot of mainframe storage. But I don't know if it's worth it for NetApp to invest in developing products to include mainframes for a few customers.

    For how long have I used the solution?

    We have been a NetApp partner for three years. We have been distributing this solution for about a year and a half.

    What do I think about the stability of the solution?

    I cannot precisely say what the SLA availability is for the platforms, but in general, the stability of the cloud service provider, whether you put it in AWS, Azure, or even in GCP is very good. There are very few moments during the year that those platforms have instability. Normally their availability is at "four-nine's."

    How are customer service and support?

    We have people assigned to us from NetApp to support us in both pre-sales and post-sales. On the post-sales side, our customer may open a case with us and we will open a case with NetApp.

    NetApp's support is responsive.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    We started using Spotinst and then NetApp acquired the company. From that point on, we have done a lot of business together with NetApp.

    How was the initial setup?

    The setup is familiar because many software as a service providers have created the same types of stacks and permissions and roles. We are able to use the same skills to do these kinds of installations.

    What's my experience with pricing, setup cost, and licensing?

    Overall, the pricing of NetApp is aggressive and the pricing becomes more aggressive as the amount of data increases. The cost for a given volume of data that you are storing becomes lower. The greater the volume of data, the cheaper the license.

    With increased volume, it is expected that the cost of each megabyte will be less. It's not a "wow," or a compelling feature. It's much more compelling when you say that, by using the solution, the data replication will be improved. Those are more technical arguments and better than saying if you increase your volume you're going to decrease your price per megabyte. Other features are also more compelling than that.

    The licensing is very straightforward, with the cost based on the volume.

    Which other solutions did I evaluate?

    In the past, we have tried to resell other solutions, like Wasabi, and we evaluated the Commvault solution. NetApp has many solutions for us, not just the storage and itself. It doesn't just create a repository for saving things with a lower cost. NetApp has cloud products as well as an open-source project. That variety of offerings is the main aspect that is important for us.

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner Reseller
    Flag as inappropriate
    PeerSpot user
    Infrastructure Architect at a legal firm with 501-1,000 employees
    Real User
    Simple with seamless migration capabilities and meets hybrid/multi-cloud requirements
    Pros and Cons
    • "The ability to do a straight SnapMirror from our on-prem to the cloud with no other data transitions is excellent."
    • "We've just been dealing with general pre-requisite infrastructure configuration challenges. Once those are out of the way, it is easy."

    What is our primary use case?

    The primary use case is for a transition off of our on-premises ONTAP and secondarily to add functionality as we migrate.

    What is most valuable?

    The ability to do a straight SnapMirror from our on-prem to the cloud with no other data transitions is excellent.

    The simplicity of cloud.netapp.com has been helpful. The fact that you're managing your on-prem and cloud and Snapshots all through one UI makes it very easy.

    We currently run ONTAP across multiple physical data centers, and our file services are critical for our firm. The ability to migrate and keep the status quo of protection of data and ease of management are the biggest benefits.

    This meets our hybrid or multi-cloud business needs since it fits right in. We decided to go with hybrid cloud and multi-cloud. We wanted to continue working with the same vendors that we did in our physical data center. We've invested time, energy, and staff training to build those relationships. Carrying them to the cloud with little friction is critical.

    What needs improvement?

    We've been dealing with general pre-requisite infrastructure configuration challenges. Once those are out of the way, it is easy.

    For how long have I used the solution?

    We've been reviewing and testing the solution for three months. 

    What do I think about the stability of the solution?

    So far, the product is as stable as anything else in the cloud. It's up to us to make sure if we need a high availability to put it in. Other than that, standard nodes allow for faster and easier deployments for lower critical environments. Stability-wise, the product has been fine.

    What do I think about the scalability of the solution?

    Our global footprint is, with reduction, about 300 terabytes. 

    I haven't attempted any scaling yet.

    How are customer service and support?

    Technical support is as good as any other enterprise support. Luckily, we haven't had a call yet, so I can't really evaluate it properly.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    We did not previously use a different solution. 

    How was the initial setup?

    The initial setup is straightforward. Once you understand the prerequisites, the deployment from your cloud.netapp account is straightforward.

    What about the implementation team?

    We work closely with our local SE that is assigned to our account. He brings in his cloud support team as needed for any questions and evaluations.

    What's my experience with pricing, setup cost, and licensing?

    I haven't gotten deep into pricing. I can't speak to costs. 

    Which other solutions did I evaluate?

    We were looking at a few solutions, including AWS FSx for Windows. FSx for Windows, at the end of the day, was a step back from the abilities for file shares for us. We would be stepping back to a Windows-based file server versus NetApp Snapshot, SnapMirror, and global replication of functions. The other option was a complete platform shift, which would've been more of a migration platform than we were willing to commit to.

    We're evaluating FSx for ONTAP as well. If that looks attractive, we will transition some workloads to that as well. Potentially, in the future, we could use Cloud Insights as the other NetApp product.

    What other advice do I have?

    We haven't done any migration yet; we're in production. That said, the whole point is to have the ability to just extend our existing NetApp and valve structure straight to the cloud.

    I'd rate the solution nine out of ten. It serves all of our needs. I have not known the product over a long enough period of time to just rate it at a perfect ten out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user