Commvault Cloud Reviews

We use the solution for backup and recovery.

The solution's most valuable features are compression and duplication ratio.

The solution's pricing could be better.

I have been using the solution since 2020.

It is a stable solution. I rate its stability as an eight.

It is a scalable solution, and I rate its scalability as an eight. Currently, we have three solution users in our organization.

The solution's initial setup was complex. Our team contacted the vendor for assistance. They logged in remotely with us and solved the issue.

We implemented the solution with the help of our in-house team.

The solution is highly-priced.

I recommend the solution to others and rate it as a nine.

We use Commvault to back up our NetApp environments to a file and data server. Commvault backs up everything, including our databases and the log files from these databases. We have a cloud, but we're not managing it with Commvault yet. We are also not using the isolation and segmentation features. We're only using Commvault internally, but it's still important for us to have those features. We've chosen Commvault for its full capabilities.  

Commvault is faster than NetApp's native Snapshot technology. Management and restoration are easier. We don't need to mount or unmount volumes from NetApp before restoration. With just a few clicks, we can immediately get to the data we need to restore, and the restoration is completed instantly. It's fast, accurate, and up to date.

We save a lot of time doing backups and restoration with Commvault. Our goal is to do everything within eight hours. We have several terabytes of data that need to be backed up daily, and we do it overnight during a period of eight hours maximum. We can usually get that done in three or four hours.

However, it hasn't cut back on our storage or infrastructure costs. Our NetApp environment is already a network cluster, meaning the data is saved in two locations. Then we installed Commvault on a third location, so we can restore from that if the other two fail. We were forced to invest in putting servers into that small data center, so there were no direct cost savings.

Backup is the reason why we bought Commvault. We need to ensure that all of our backups are done daily. This is very important because we use it for disaster recovery, and we need this data back. We're a production environment. If we cannot restore in the event of a failure within X number of hours, it has a considerable impact on our company. Five thousand people are working at the factory who depend on this data. If it's not available, they can't work. 

Consistent recovery is also essential. Every day, we have users who delete a file and need to restore it. Our backups must be up to date.

Commvault's interface has a lot of sub-menus, and sometimes it's hard to find the information you need. You have to click a few times before finding the right window. The overview could be better.

We've been using Commvault for almost three years now.

Commvault is stable. We've never had problems with it. It's always available, and it's doing the job without any issues. It never fails. Sometimes we miss a backup, but there's always a reason for it, and it's not the fault of Commvault. In the last three years, we've never had to open a ticket with Commvault. That shows how stable and well-performing it is.

We are looking into scalability because we're not yet using Commvault for the whole organization. The main limitation is the cost of implementing it at a lot of sites. Every year, we put it on our agenda to adopt it across Europe. We've selected some spots, but sometimes we've had to scrap a few because of the cost. However, soon we'll have the data we need for broader implementation. 

We have around 15 affiliates, including five big ones. Currently, it's running at two of those. Every national affiliate is responsible for its own budget, and it's up to them to decide if they want to spend the money on it. They have the built-in Snapshot technology from NetApp that they can use, with all its limitations, or they have the full-blown Commvault option, which needs investment first. Every year, we evaluate if we replace the NetApp Snapshot technology with Commvault. Quite often, there are other priorities.

But that hasn't stopped us because sometimes we use Turkey's Commvault to take backups from all those countries. So the scalability is excellent. It's easy because you just add the server, and it's up and running.

Installing Commvault is straightforward. It's a "next, next, finish" installer. For deployment, we had help from a third party who had experience with Commvault, so it was pretty easy to configure all those things.

Altogether, it took four or five days. We had to do some fine-tuning. It was a new product for us, so we had to learn how to use it too. The installation itself only took a day and a half. We spent the rest of the time learning tips and tricks and all that stuff. For management, we work with a third-party partner in India called Infosys. We also have a team of three people here in Europe supervising it.

When we installed everything in Turkey, we used a partner over there called Datacore. They were outstanding. We vetted them first using the same process we use for approving projects. I would rate them nine out of 10. 

For us, the return is that we can get our data back in the event of a disaster. That's the most important thing. We're not looking at it in terms of a return on investment in hardware. The data is what matters the most. If we lose that, it will cost us a fortune compared to the money we spend on installation. You cannot compare those two things.

Commvault's price is quite high. You have to pay for the licenses and the hardware you need for the Commvault environment. If you don't have all the hardware, you have to buy it, which can cost a few million. In the end, it's vital to protect our data, so the price isn't an issue. However, it can be a hard sell to your top management. They say, "Well, you have your NetApp snapshot technology. Why go for something else when that is doing the job? Why should you spend a few million to implement another backup solution?" 

If you can find a decent reason, then it's great. With the pandemic, it's becoming difficult to justify expenses like this. Everybody is afraid about the impact and wants to avoid extra costs as much as possible.

In the beginning, we were looking at around six or seven products, and then we made a shortlist that included Veeam and Cohesity. We looked at solutions from most of the big, traditional companies. We chose Commvault because it has all the features we want. It's also a good fit for us because it supports a wide range of platforms, including NetApp and Windows, and we use several different platforms. 

I rate Commvault nine out of 10. If you want a stable product that you can rely on, you should definitely go for the Commvault environment.

We use it for endpoint backups. They are laptops and we needed a solution that could handle Linux, Macintoshes, and Windows, in different locations, and Metallic was the best option available.

We needed a solution that could handle Linux and Macintosh and Windows, all together. Metallic seemed to be the only one on the market that could provide an all-endpoints SaaS solution.

In terms of the manual work required to manage our backup operations, I don't have to manage it that much. There is not much that needs to be done or manual work involved. It works well. There's not much I have to do on our side and I don't have to dedicate any time to it.

Metallic has also saved our organization money on infrastructure costs because the price was amazingly affordable, and we didn't have to create an on-prem solution. Especially since we're moving the Parsons data centers to the cloud, we're reducing our on-prem footprint. This SaaS gives us a full cloud solution to take care of that . There's a huge cost savings for us with this. 

We're only using the endpoint backup solution part of it. It works very well. There's no impact on the endpoint. It runs in the background and it's something that you install and then forget about.

It's very easy to use. You don't really need to change anything or do anything different. For non-technical people it can be a little challenging trying to understand the GUI options because it can go a little bit deeper, but for basic use it's very simple to use.

It's definitely appropriate for an enterprise-level environment. Its performance for both backup and recovery is amazing. It runs very well. I don't even know when it's running and that's true during the backups as well. It completes successfully and there's zero impact on the endpoints.

The compression and deduplication are great for optimizing bandwidth and speed. I don't have to worry about it or think about it, and, because it's a SaaS solution, I don't have to worry about the storage size.

It's also very flexible in terms of where data is stored. You can choose what you would like. We're going to Azure cloud and the issue for us was more whether the security protocols were in place, and they are. As long as they met the security requirements, we were okay.

It has the AES-256 encryption. It meets that requirement and there is no issue with the amount of time it takes. The backups are very quick. There's no delay.

Adding new users who are non-technical can be a little challenging. You can push the software out through SCCM and install it that way, and that works great, but it would be nice to have another option where somebody could download an executable and run it and it would work. It's a little challenging to get it on other systems. I work from home but I have to go and help them because sometimes they don't know. I might send them the authentication code and they'll try to install it... I'm still working out the details, trying to figure out where they went wrong, but I've had several users try to do it and it hasn't worked.

I would like to see more customizable reports. I have reports going right now, but the daily report, for example, shows something like 40 jobs that ran when there are just a few endpoints on there. I'd like to just know if the endpoint was successfully backed up, not how many times. More customizable reports would be nice to have.

I've been using Metallic since it was released. We jumped onto it as soon as possible.

The stability is great. It just runs. I've had zero issues with it.

The scalability is great. It's very scalable.

Currently, I only have 10 endpoints that I'm protecting and I'm trying to roll it out to more. There are a lot of employees in our company. Right now, we're using Metallic for just critical systems, critical endpoints. I'm hoping to create more awareness throughout Parsons so that others learn about it and see it and, maybe, start using it. But for now, it's going slowly trying to get Metallic in through the door.

Commvault's technical support for Metallic is great. I really enjoy working with Commvault tech support. They're very knowledgeable and I love how they handle tickets. They're on top of things. They're always kind and polite and understanding. I wouldn't want to go through third-party support. I'd want to go directly through Commvault.

Our company used to use PC Backup but that's gone away and now they want to use OneDrive. A lot of executives feel that OneDrive is sufficient and that we don't need an actual backup solution.

The reason for going to Metallic was that PC Backup couldn't do Linux or Macintosh. We needed something that could do everything. It is a complete SaaS solution, backing up to the cloud.

The initial setup was straightforward. It was me that set it up. We got our plan configured on the website and I installed it for myself and for somebody else. It was pretty straightforward and pretty easy to configure. The instructions work well. 

The interface was a simple webpage, which is something I like about it. It's something I'm used to and there wasn't much to add. You just add the endpoint into the policy and away it goes. You don't have to really configure it.

We enabled it with SAML, so it uses our Active Directory and automatic login, and that worked out pretty well. It's been a long time since I've dug into it and done it. I tried to add some other users and they just emailed me and said they couldn't get it to work. I'm not sure what they're doing. Somehow they went wrong and I'm not sure yet how.

Overall our initial deployment took about 10 to 15 minutes. It was quick. In terms of deployment and maintenance, I'm the sole person who is working with the solution.

We didn't have an implementation strategy. We were trying it out. I had a certain number of laptops that I knew that needed to be added to it. I went through and configured them to work with Metallic. It was a really quick, easy setup, and it just runs with no issues. It doesn't matter where the laptop is at, where it's connected.

For me, it works great and it does exactly what it says it does. I love having it. I would put it on my home computers if I could. I'm still working on trying to get it implemented throughout all of Parsons.

We looked at PC Backup. We also looked at other cloud solutions. Metallic was the one that offered all the options.

It's simple and it has very low-to-no impact on endpoints. It runs in the background and has some really cool features for the end-users to use on the computer, if they want to look at their backups, do restores, or to find their computer location. But it is very simple and basic for non-technical people to use.

I like the interface, how it works, and being able to get daily reports of any failures or anything that happens is very useful.

I would rate it a 10 out of 10. I haven't come across anything that's better.

Customers who can’t afford storage on their on-premise servers can easily use the product to move to the cloud.

I like the Metallic Endpoint feature. Whoever has an Endpoint license can store unlimited data on the cloud. Commvault provides unlimited restoration for free. Other products have a limit on restoration. When we cross the limit, we must pay for restoration.

The product does not provide an option to save a copy of data on-premises.

I have been using the solution for three to five months.

I rate the tool’s stability a nine out of ten.

The solution is scalable. We have three to five customers using the tool.

Whenever we raise a ticket, the support personnel connects with us at the exact time that they committed to. I can rate the support team a ten out of ten without a doubt.

Positive

The on-premise solution is a lengthy one to configure. We can deploy the solution in three to four clicks, though. The product is purely cloud-based.

To deploy the tool, we must authenticate our email ID on Commvault. Then, we will get a link from which we need to generate a username and password. Once we enter that username and password, we'll get a region of the cloud where we need to configure the storage tool.

The solution is worth the money. Depending on the customer’s feasibility, they pay for the license every year or every three years. The evaluation is given for 30 to 90 days, which has to be paid.

A sales manager, a technical manager, a COO, one of my colleagues, and I handle Commvault in our company. Overall, I rate the tool a nine out of ten.

My customers are not satisfied with the tool because there is a little trouble with the throughput of Metallic. If you go very large, you run into some problems, especially when moving things into the cloud and out of the cloud. This is not a problem of Metallic but a cloud provider problem. However, that's a normal thing we have with the cloud providers.

I wouldn't want any more features since, at the moment, it's very simple to do a SaaS backup and so on while doing more complex things since it is on-premises.

I am a reseller of backup products, not only Metallic but also for Veritas, CommVault, and so on. I am trying to resell the solutions. I like to resell it in combination with our hardware. I am not interested in selling the solution for the cloud because that's not with our hardware. I am a partner of CommVault, so I resell Metallic. My company also has a partnership with Veritas and Veeam.

I have been dealing with Metallic for my customers.

The product's stability is good enough. But, you have to compare it with other products. For example, I am using Veritas, and I am using it for CommVault, perhaps at home for myself. For the rest, I am selling. I am not doing the implementation. I'm only selling it.

Technical support is fine if you speak English. So, it is good enough if you speak English. If you prefer your native language, then it becomes a little bit more difficult.

Speaking of Metallic's competitors, they have an advantage in terms of pricing and buying deals or doing some more things in a smarter way. For example, Veritas provides better tools than Metallic. 

You need something in the cloud to do the backup. For example, I use CommVault on my laptop from work, and we use Commvault in the cloud, which is very easy and very good to use. Not Metallic, but with only Commvault, we are backing up to the cloud and our desktop. So, we can use it everywhere. If you have some problem, then you can restore it at home, which is very nice. It works very fine.

My suggestion to others is to size it correctly. I do recommend the products.

Overall, I rate the solution an eight out of ten.

I use it for backing up the database of our Microsoft People server system.

Commvault has saved us time in managing our backup and restore processes, as well as backup management. It has definitely made our backup administration more efficient.

The most valuable feature is the ability it gives me to automate backups well and consistently, and to follow up on them as well. It also provides consistent recovery processes. Whenever we have needed to do a restore, it has worked quickly and efficiently.

The completeness of Commvault's coverage for databases is also pretty good. It covers all the bases with the major databases that we utilize within an enterprise.

I also like it because it's pretty easy to use and that it is pretty reliable. The user interface for managing it is good.

In addition, it auto-discovers the databases and that means lower maintenance on my side for individual database configuration.

There are two ways to use it and I prefer the web-based one over the app. I wish they were a little bit more matched in what they offer because the features aren't as available in the web-based interface as they are in the app.

I have been using the Commvault solution for about two years.

It's pretty stable.

It seems to be scalable. I'm not really involved in that side, being a user and not an administrator of it, but I know that they've had to add on and do upgrades to it. It seems to be working well. I haven't seen any disruption from that.

I use my internal company support team and they reach out to Commvault as necessary.

We were using Dell EMC NetWorker. We switched due to bad support and because we were having lots of issues. They were also slow in keeping up with the technology.

In general, I would give Commvault a thumbs-up. Make sure your people are involved in the procurement process so that they understand what it offers, and be sure to do PoC testing. But that's generic to any implementation.

Because my work with Commvault isn't necessarily technical in nature, it's more process-oriented, people in a similar situation should work closely with their administrators to make sure the admins understand what they need to do. The problems that we have with it are mostly to do with internal workflow.

The Command Center for getting a view of your data is okay. We have some internal issues with the way that the people who manage the system display things to us and give us access to certain things. But otherwise, it's okay.

We use it to backup and protect our virtual environments. We do Active Directory, SQL, file server, and some application levels backups. We do Office 365 and SharePoint backups too.

We back up everything locally first, then store it in the cloud.

It provides us a single solution to recover data. We haven't had a lot of restore requests. There have been a couple of them where we had to restore a full server and the work involved was very minimal. We were able to run a quick restore job. We did not really run into any challenges doing this. Every once in a while, we receive requests for files or emails that people have lost and those files are in SharePoint or OneDrive. We have the ability to restore it within 30 days directly from the portal. But if it's beyond the 30 days, we use Commvault to restore data and that has worked absolutely fine.

It has helped us drive innovation and accelerate growth. From a growth perspective, this storage solution has clearly helped us. The option for us to save the data in the cloud is very valuable for the organization.

The solution has helped our admins to minimize the time they spend on backup tasks and other projects. We have an administrator who manages the system. I'm more of an architect. Compared to the previous product where the administrator had to go around and look for a lot of information before he could find out whether the backup had competed successfully and the reporting structure was not that great, the reporting structure now with Commvault is where he can get daily emails from the jobs which have been completed. If there are any issues with jobs, he can directly drill-down to the details and find out why the job failed or why it did not run on time since there may be other dependencies that won't allow the job to run.

All the features used right now have been very valuable. The biggest advantage for us right now is the ability to back up our Office 365 mailboxes along with all our SharePoint and OneDrive data. Because all our users mostly store all their data in these locations, it is important for us that we back up all these services.

It provides us a good holistic view of everything that we have backed up so far. It also provides us all the recovery points. If we look at an an object that has been backed up, we can tell how many retention copies it has, how far we can go, and recover any data, if needed.

I have written a lot of different reviews about the product and every time I have mentioned the user interface is not user-friendly, e.g., the admin portal is not user-friendly. It definitely takes a lot of understanding to get familiar with the portal. However, once you are completely familiar with it, then it is pretty easy to manage. It's not something that you can jump in right away and start, knowing what exactly is going on. There are a lot of places that you need to look around to understand how the backups are configured.

The administration of the solution could be simplified. This would really make the administrator's life easier.

We've been using Commvault since early 2017. We are in our third year right now.

It has been pretty stable. We have not run into a situation where our systems were compromised. However, we have run into system corruption issues and were back in business within about two hours.

Right now, we only have one primary administrator for this product. We have a couple of backups in case this person or another is on vacation. We have other people who have been provided good knowledge transfer on how this product works. This way, if either of them is unavailable, there is somebody who can do the job.

It is definitely scalable. We are able to scale as we need, whether we need to add any compute, storage, or additional licenses for user accounts. All of that is very flexible when it comes to scalability. If we want to add more users to our Office 365 backup, we can quickly get new licenses from the vendor with a quick turnaround time. As soon as we get that, we are able to add those users' data to our backups. We generally have a buffer. However, sometimes if there are a lot of new hires, then we need to go in and secure new licenses.

We are using more space than what we were previous using, mainly because we did not have a lot of flexibility with the previous product that we were using. So, there was not much room for us to store the data for a long duration. At the same time, we did not have enough on premise storage capacity to leave the data around for a long time. Therefore, data growth has been significant over the past years because we have been able to store data. So, we are leaving the data on-premise for 30 days, then we moving it to the cloud. Most of the data is now in the cloud, but even on-premise we are now able to back up a lot of systems that we were not able to back up earlier. We have seen significant storage growth on long-term systems, because we are now backing those up and the data is there.

It is only my team managing the system. We back up all the data that the end user has. If they need help restoring their data, then one of my team members will go in and restore the data. The user has no direct interaction with the product.

It is pretty extensively used right now. It is backing up all the data that we have right now. We are looking into some additional features, so we might not start looking at those until later this year. Commvault has come out with some new features and we want to look into those. For the first two years, it was a stabilization period for us to get the product implemented, ensure everything was stabilized, all the important data was being protected, and data was being stored in necessary places. We also looked at all the trending over the last two years to ensure we had enough capacity in all the areas to maintain the server and storage space. Now, we are at the stage where we are pretty comfortable on how we can scale this product when needed. We are looking into additional features that Commvault has, and we will start looking into these towards the end of the year.

Tech support has been good. I haven't had a lot of interactions.

Every once in a while when we have to make any architectural changes to the deployment, my administrators reach out and consult with me. We sometimes engage with the support team or Professional Services team. Their responses have been pretty good so far. We have never had a situation where we were kept waiting for days to get an answer or solution.

I used Commvault from 2011 to 2012 at one of my previous organization, but it was only for a short period of time that I worked with it. I then had to move onto other things. That experience helped me when we deployed the newer version of Commvault. At the time, it was Commvault Simpana, and now, it's only Commvault. That experience helped us to understand its requirements and how we could set it up.

We were using Dell EMC Data Protection Rapid Recovery. It wasn't flexible nor scalable. It did not meet all our requirements. It wasn't able to back up physical and cloud environments. It could not store data in the cloud, so we had to look at options to store and protect our data. We were unable to back up our Office 365 and SharePoint data. With Commvault, it has made it seamless for us to store data in the cloud, not only protect it. 

We can set up proper retention policies now. So, if we need to store any data, for example, over a year, seven years, or 10 years, we can accordingly store it. We can then apply policy to that storage, which after that retention period, we will not have to go in and do a manual cleanup.

The deployment took about a month. The planning was another month or two.

We wanted to ensure that we were able to protect all our systems and data not protected up until then. At the same time, the strategy was that we did not want to incur a lot of significant costs on just deploying the solution itself. Plus, we did not want a lot of administrative overhead while maintaining the servers and application environment. We did not want that routine daily administration activity. We wanted to set up the environment and not worry about it until something went wrong.

We had assistance from the vendor, so they did assist with the setup. The system was completely new for some of my team members who had never worked with it before, so it did take them a lot of time to get familiar with it. Those administrators are able to manage the system very well now compared to what they were able to do in their first year when they had to frequently go back to the vendor and ask them, "How do we do this? How can we do that?"

We worked directly with the vendor. The vendor's Professional Services team was able to assist us with the deployment.

After deploying the Commvault solution, we are saving four to five hours a week.

We have been able to save on infrastructure costs by not storing long-term data onto systems. Instead, we have been able to store them on cheaper cloud systems. There is a lot of savings there if you consider all the cost involved to store data on an on-premise server storage system, plus the maintenance, and the support which goes behind maintaining that system. 

I have seen return of investment.

There is a bit of cost involved with signing up the entire solution. It's not a cheap solution.

We did evaluate Veeam and Cohesity. 

At the time, Cohesity was not mature, as they were fairly new to the business. We had a few meetings with them, and after our discussions, we found that the solution might not meet all our requirements. E.g., the physical server backup was one important feature that was not supported at the time. 

Veeam is a platform that I have extensively worked with in all my previous roles at other companies. So, we do have a Veeam implementation that is used by a different team in our organization. They manage all their backups through Veeam. Our plan was not to use the same solution in all environments. We wanted to use different solutions within the entire organization for exposure to multiple data protection solutions. Also, Veeam did not support physical machine backups and only supported virtual machine backups.

In my previous deployment, there were no cloud features. The cloud was not popular and everything was on-prem. Even when we moved to Commvault, Veeam lacked a lot of features, which is why Commvault seems to be the best choice for us.

We already had our cloud solution in place. After understanding that Commvault does work with that cloud provider and it would help us store our data, we did not have any further concerns about cloud vendor selection. The cloud environment and Commvault environment were set up around the same time. We moved to the cloud at the end of 2016, and then, in early 2017, we moved to Commvault. So, everything worked out well.

Go through an assessment first before selecting the product. Every business is different and has different requirements. Do a complete assessment with the data protection partner, whether it's Commvault, Veeam, Cohesity, or someone else. Go through a proof of concept, if possible. Mind your business requirements, RPO, and RTO. Look at your budget too. This should help you to make the right decision.

The biggest lesson would be to have a proper data protection strategy for the organization. There were a lot of things that we had to implement after implementing the product. It's better if you completely understand your business requirements, then implement this product.

I would give it a rating of an eight (out of 10) because it does not have an easy deployment. The deployment is not something that just anybody can go in and deploy. It needs a good level of understanding for deployment. Once you deploy, you need to be familiar with how to administer the product, how to set up all the reporting, etc. Just navigating the admin interface is not really that easy.

This solution is mainly used for virtualization and Oracle data protection. The customers I work with use it to protect their machines and active databases.

It's a complete software that can protect all the main applications. Perhaps that's the feature I like most. The integration with the NetApp and other apps is also very nice.

I think the one thing that could be improved is the customer experience. The interface should be more user friendly.

The price could perhaps be lower as well.

I believe it's very stable. That's why the customers who buy Commvault stay with Commvault.

The solution is scalable, because you can add app features. It's very possible to scale.

We have four or five customers, so that's probably around 20 users. We are in a small country.

The technical support is very good. It was not very difficult. I had a bug and the Commvault supporter helped perfectly.

The initial setup is straightforward. We need one or two integrators to deploy and maintain this solution.

We evaluated other options, but Commvault is a very complete solution. In the end, it's a very useful tool. Our customers will already know Commvault. Their software always compares well with other vendors.

Perhaps, my best advice is to look for an integrator with expertise in Commvault to help deploy this solution. It's not that easy to install. It's not even possible after they all installed it. Customers should have someone with good expertise with Commvault to supply it.

I would rate this solution as eight out of ten.