We primarily use the solution as a backup.
We primarily use the solution as a backup.
Our other solution deploys every agent on every single server, and then you back up that way. However, when you have to deploy to the APIs using the Commvault to their instance, due to the fact that we are a VMware shop, we are capable of leveraging the snapshot capability within the VPI. And then we back it up, the entire VM.
The license is counted as one VM. The other option is based on the capacity model. The cost on a capacity model is more expensive than the VM path model. That's why we switched. The functionality is very similar.
The VSA, the virtual system agent backup, is the most useful aspect of the solution for our organization. Based on our use case, it cuts our costs significantly. Early on, when we had the software at one point, we were using the front-end data protection, the DPE model, with the licensing using an agent. Then, as the technology continued to evolve, they added additional features like the VSA path, VM path model and other things. We are switching from the DPE model to the VSA model. That helped us to eliminate some of the costs.
Once you get comfortable with the solution, it becomes pretty easy to use.
People are going to be very impressed with that kind of support that they get from Commvault. It's excellent.
It's a comprehensive data management for all platforms. It works with multiple clouds and vendors.
They have a strong development team and are market leaders in the space.
With any product, there could be improvements made.
I can't think of exact features that are lacking.
It's been a while, however, it's my understanding that they have new features coming out.
Our cloud is still pretty old-school, I continue to use the console as the traditional admin tool for daily troubleshooting. In a newer version, they're using something called Command Center. I haven't played around with that yet. I heard that it's very sleek. At this point, the console is pretty dated, so it's good they're doing an update.
The Chargeback feature has recently changed as well. I haven't had a chance to explore it, however, I believe they've improved on it quite a bit.
The solution can be a bit complex for new users.
The solution needs better Office 365 data backup management.
I've been using the solution for six years now.
The product is very solid. They are the number one data management platform on the market. They are leading in that sense above the competition.
At this point, there are no plans for increasing usage right now. We are reducing our footprint on-prem and we've moved everything to Azure. Unfortunately, we leveraged some of the native protocols from Azure side. Commvault has gotten reduced. Due to that change, the pricing or licensing that supports the functionality of it may be impacted a little bit.
While you can call support for anything, they have great online documentation that you can reference for assistance. It's easier to check out that before reaching out to them directly.
Their support is the best. They're worldwide, 24/7. I give credit for that. I deal with a lot of other vendors. Their support model is far superior. Once you open the ticket, if, after an hour, it's not resolved, you can click on it and another engineer will come online within the hour to assist, depending on the severity of the case.
I'd rate them nine out of ten for sure.
At one point, we almost tried to switch to another vendor. However, due to the economic scale and other factors, we didn't move forward. We decided to stay with Commvault in order to leverage all the modeling and pricing, and we were able to accomplish what we needed.
Since I have worked here, the company has always used Commvault.
The initial implementation has a moderate amount of difficulty. It's complex at times, however, it depends on what it is. Once you know it, it's not that complex to set up. Overall, it is easy to use. It's not that difficult.
Deployment is probably just a couple of hours. In that time, you can spin up the environment and then you can set it up and deploy it and get a backup.
While we have a lot of users on the solution, I am the main person who handles the maintenance.
Most of the upgrades we do ourselves. In the cases where we have a major upgrade, we typically use a consultant. We did use a couple of consultants in the past for the upgrade. Early on, we didn't have the resource and personnel to handle everything.
After using Commvault for six years now, I'm a bit more comfortable and confident in handling everything myself more and more.
We work directly with Commvault consultants.
The ROI comes from the fact that it's a solid product that works the way it is supposed to. When you need data recovery, it's perfect. That's your money's worth right there.
The licensing costs are determined on a yearly basis. It might be around $40,000 or $50,000. There are no costs in addition to the standard licensing fees.
Originally, we were on a private cloud, however, we've since moved to a public cloud.
I'd advise others that the implementation depends on the skill level of those setting it up. It's best to consult with the technical manager or the technical team. They can give recommendations. The costs are very reasonable. It may be only $4,000 or $5,000 for three or four days worth of consultant work. They handle the consulting remotely, not on-premises.
Of course, if you don't know the answer to something at any time, you can always call support. That's for break/fix scenarios. For most other things, the online documentation will get you through.
Overall, I would rate the solution nine out of ten. We've been very happy with the product.