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