Please share with the community what you think needs improvement with NetApp Cloud Volumes ONTAP.
What are its weaknesses? What would you like to see changed in a future version?
I suspect ONTAP will just end up being a portion that runs on StorageGRID. Ultimately, everything will be object-based, then you'll just have a little dock of ONTAP that will do your NFS and CIFS.
NetApp CVO needs to have more exposure and mature further before it will have greater acceptance.
In the next release, I would like to see more options on the dashboard. Local support needs improvement.
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.
Only AWS and Azure public clouds are currently available from China, and I would like to see support for Aliyun (Alibaba Cloud).
I would like to see better integration with Active IQ. I know they're making strides for that, and some of the tools are being mimicked in Active IQ now so that I can look at the same information. If the footprint looks right and the GUI looks the same to us, it'll be more effective for us down the road in the long-term. Encryption is very important for us going forward because we sometimes store data out of the country, and sometimes overseas. We are looking forward to more in terms of encryption, including the inline encryption for SnapMirror and things of that nature.
The inclusion of onboard key management in CBL would simplify the way we have to do our security. Multipathing for iSCSI LUNs is difficult to deal with from the client-side and I'd love to see a single entry point that can be moved around within the cluster to simplify the client configuration.
We would like to have support for high availability in multi-regions. There is no support for Microsoft Azure.
In terms of improvement, I would like to see the Azure NetApp Files have the capability of doing SnapMirrors. Azure NetApp Files is an AFF system and it's not used in any of the Microsoft resources. It's basically NetApp hardware, so the best performance you can achieve, but the only reason we can't use that right now is because of the region that it's available in. The second was the SnapMirror capability that we didn't have that we heavily rely on right now.
Maybe I need more speed, but so far, I don't have any feedback for improvements. I would like to see something from NetApp about backups. I know that NetApp offers some backup for Office 365, but I would like to see something from NetApp for more backup solutions.
Some of the area's that need improvement are: * Cloud sync * Cloud Volume ONTAP * Deployment for the cloud manager These areas need to be streamlined. They are basic configuration error states to acquire late provisioning. I would like to see the ability to present CIFS files that have been SnapMirrorroed to the Cloud Volume ONTAP and the ability to serve them similarly to OneDrive or Web interfaces. We are talking about DR cases, customers who are trying to streamline their environments. In the case of DR, users can easily access that data. Today, without running it as file services fully and presenting it through some third party solution, there is no easy way for an end-user to access the appropriate data. This means that we have to build the whole infrastructure for the end-user to be able to open their work files. The integration wizard requires a bit of streamlining. There are small things that misconfigure or repeat the deployment that will create errors, specifically in Azure. As an example, you cannot reuse that administrator name, because that object is created in Azure, and it will not let you create it again. So, when the first deployment fails and we deploy for a second time, we have to use a new administration name. Additionally, it requires connectivity from NetApp to register the products and the customer is notified that Network access is not allowed, which creates a problem. This issue occurs during the time of deployment, but it isn't clear why your environment is not deploying successfully. For this reason, more documentation is needed in explaining and clarification steps of how it needs to be done.
I would some wizards or best practices following how to secure CVO, inherit to the Cloud Manager. I thought that was a good place to be able to put stuff like that in there. I would like some more performance matrices to know what it is doing. It has some matrices inherent to the Cloud Volumes ONTAP. But inside Cloud Manager, it would also be nice to see. You can have a little Snapshot, then drill down if you go a little deeper. This is where I would like to see changes, primarily around security and performance matrices.
I would like this solution to be brought to all the three major players. Right now it's supported only on AWS and Azure. They should bring it to Google as well because we would like to have flexibility in choosing the underlying cloud storage provider.
Right now, we're using StorageGRID. Obviously, it is a challenge. Anything that you're writing to the cloud or when you get things from the cloud, it is a challenge. When we implemented StorageGRID, like nodes and things like that, we implemented it on our bare-metal. So the issue is that they're trying to implement features, like erasure coding and things like that, and it is a huge challenge. It's still a challenge because we have a fine node bare-metal Docker implementation, so if you lose a node for some reason, then it's like it stops to read from it or write to it. This is because of limitations within the infrastructure and within ONTAP. How it handles erasure coding. I feel it the improvement should be there. Basically, it should be seamless. You don't want to have an underlying hardware issue or something, then suddenly there's no reads or writes. Luckily, it's at a replication site, so our main production site is still working and writing to it. But, the replication site has stopped right now while we try to bring that node back. Since we implemented in bare-metal, not in appliance, we had to go back to the original vendor. They didn't send it in time, and we had a hardware memory issue. Then, we had a hard disk issue, which brought the node down physically. It needs better reporting. Right now, we had to put everything one to the other just to figure out what could be the issue. We get a random error saying, "This is an error," and we have to literally dig into it, look to people, lock files, look through our loads, and look through the Docker lock files, then verify, "Okay, this is the issue." We just want it to be better in alerting and error handling reports. Once you get an error, you don't want to sit trying to figure out what that error means in the first two hours. It should be fixable right away. Then, right away you are trying to work on it, trying to get it done. That's where we see the drawbacks. Overall, the product is good and serves a purpose, but as an administrator and architect, nothing is perfect.
Some of the licensing is a little kludgey. We just created an HA environment in Azure and their licensing for SVMs per node is a little kludgey. They're working on it right now. We're working with them on straightening it out. We're moving a grid environment to Azure and the way it was set up is that we have eight SVMs, which are virtual environments. Each of those has its own CIFS servers, all their CIFS and NFS mounts. The reason they're independent of one another is that different groups of business got pulled together, so they had specific CIFS share names and you can't have the same name in the same server more than once on the network. You can't have CIFS share called "Data" in the same SVM. We have eight SVMs because of the way the data was labeled in the paths. God forbid you change a path because that breaks everything in every application all down the line. It gives you the ability to port existing applications from on-prem into cloud and/or from on-prem into fibre infrastructure. But that ability wasn't there in Cloud Volumes ONTAP because they assume that it was going to be a new market and they licensed it for a single SVM per instance built out in the cloud. They were figuring: New market and new people coming to this, not people porting these massive old-volume infrastructures. In our DR infrastructure we have 60 SVMs. That's not how they build out the new environments. We're working with them to improve that and they're making strides. The licensing is the only thing that I can see they can improve on and they're working on it, so I wouldn't even knock them on that.
Scale-up and scale-out could be improved. It would be interesting to have multiple HA pairs on one cluster, for example, or to increase the single instances more, from a performance perspective. It would be good to get more performance out of a single HA pair. My guess is that those will be the next challenges they have to face. One difficulty is that it has no SAP HANA certification. The asset performance restrictions create challenges with the infrastructure underneath: The disks and stuff like that often have lower latencies than SAP HANA itself has to have. That was something of a challenge for us: where to use HA disks and where to use Cloud Volumes ONTAP in that environment, instead of just using Cloud Volumes ONTAP.
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.
They're making the right improvements right now. The only issue we had lately was that outside our VPC we could not reach the virtual IP, the floating IP. I heard that they have fixed that as well. That's a good advantage.
It does not have tutorials in languages such as French, German, Spanish. Adding these options would improve the support service of NetApp Cloud Volumes ONTAP.
El producto mantiene un enfoque arraigado en los procesos no alternativos. Esto logra dificultad en la conexión de la vulnerabilidad en los procesos. Me gustaría verlos mejorar la perspectiva de inicio y búsqueda en los paneles. Esto permitiría una mejor visualización de los contenidos que se capturan en la herramienta.
The key feature, that we'd like to see in that is the ability to sync between regions within the AWS and Azure regions. We could use the cloud sync service, but we'd really like that native functionality within the cloud volume service.
AWS has come into the picture, so we want to move into AWS. Therefore, we don't want to do anything more on on-premise anymore. NetApp has to come up with a cloud version. I would like to have more management tools. They are difficult to work with, so I would like them to be a bit more user-friendly.
The data tiering needs improvement. E.g., moving hard data to faster disks.
NetApp could certainly improve on the support side. They do not need to improve so much on the product side for now, because we have procured a high end system.
The navigation on some of the configuration parameters is a bit cumbersome, making the learning curve on functions somewhat steep. I would like them to make upgrading simpler. I would like it if they could offer a simpler upgrade guide which you can generate through their website, because their current version is full of dozens of complicated CLI commands.
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.
Just more scale out. It can only do two nodes. One SVM, which would be okay as long as I can scale easily. It needs to be matured with more capabilities.