Commvault Cloud Reviews

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.

I recently deployed Metallic for backup storage on Azure for a customer who lost all their data. Metallic helped me to restore the data within an hour, which is much faster than restoring from Microsoft services with a ticket on support services, which took four to five days.

I have a customer who uses it, but I am not a direct user, and I work with customers who use Metallic.

The functional integration could be better. For example, the replication function is not there in the Metallic products and can be complex. We were licensing the functionality in a different tool but not in Metallic's key. So it should be enhanced.

In future releases, I would like to see better VM replication because it's not available today. But there should also be provisions to have more integration.

Metallic is perfect for a customer because it is very easy to use. However, I find it difficult to find some use cases on my own and need to contact Metallic support. Moreover, in a SaaS project, I cannot open or function agents alone and require the support of Metallic.

I have been using this solution for two years. We are using the latest update of the Metallic SaaS solution.

It is a stable solution. I would rate it a nine out of ten. I have had no errors since the installation.

When I put it into the production model, it was very stable, and we had no time to do the next production review after a very simple test.

I would rate scalability a nine out of ten. It is very scalable.

The customer support team is responsive and very helpful. There were no problems, and their response time was very short.

Positive

The initial setup is very easy. It's quick and simple, and Metallic is already ready for use after two hours. It integrates well with Office 365 backup for Exchange roles, Teams, or SharePoint.

Our internal team deployed the solution.

The pricing depends on the functionality you require. For example, Office 365 is priced correctly because you have everything in one package, including the license for backup and storage. It is very attractive for the middle market, so I would rate it a seven out of ten, where one is the cheapest and ten is very expensive.

But for some projects, we may need to buy additional backup and storage for the retention period, making it more expensive. However, seven is good for me. Also, we could consider integrating with other cloud providers for secondary backup and storage to store backups. We only have Azure, OCI, or RWAIS, but exploring other options that offer better prices would be interesting.

I have experience using different products in the same category as Metallic, including CommVault and Rubrik. CommVault is the same product, but the trends are converted. It's an on-premise product. And Metallic is the first product of the merger of the company. It's the same product. I also saw Impacket, but I find it very old-school. We are missing old school.

I also see Hybrid. It's a very good product, but quite more known. There is still a lot to fix in Rubrik. I also find CommVault and Metallic with more experience and integrated with all our products. We have all products, like your old servers, the unique server. And it's quite more difficult with Rubrik. So, I prefer Metallic for this.

I would recommend using the product. Metallic is a very interesting product. My company also integrates Acronis and VM in some of our projects, but Metallic is one of the best products for cloud and SaaS. It has many functionalities and is simple to integrate.

For me, it's a ten. I haven't found any other product with so many functionalities that is also easy to integrate. It's not just good for my business, but it also gives me peace of mind and allows me to sleep soundly at night.

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.

We're using it mainly to back up operating systems like Windows, Linux, and databases such as Oracle and Microsoft SQL.

It has simplified disaster recovery and we have used it for migration as well. For migrating from old FX servers to new FX servers, it was not possible to use any new feature from VMware. There was just vMotion and the success rate of migration of the whole disk was less than 50 percent. It was not possible to manage it that way. We used Live Sync and it was able to migrate 150 machines every day during the weekend, without major problems. That saved us a couple of weeks of time, probably 50 percent of the time it would have taken us. Without Live Sync it wouldn't have been possible to manage it.

The fact that the solution is a single platform has definitely enabled our company to accelerate growth because you don't need to leave the Commvault console. With NetBackup or TSM (IBM Tivoli Storage Manager) when it comes to customization of scripts for databases, you have to go into the client at the operating system level and modify the scripts. With Commvault you don't have to do that. You don't need to access the operating system, which simplifies the work.

Commvault helps minimize the time spent on backup tasks, creating time for other projects. I'm able to write a workflow in Commvault's internal environment and I can automate any action I did manually before. For example, deployment of remote offices can be fully automated.

It also saves us money on infrastructure because the configuration which will be used for IntelliSnapshotting is very simplified.

Another company I worked for previously was being attacked by a ransomware virus. The company lost its whole Windows infrastructure, so it didn't have Active Directory. Commvault was on Windows as well and the Knowledge Base which ran on Linux was authenticated with AD. Everyone lost their workstations.

The recovery process was that we got the database from Commvault, because part of raising cases includes the ability to upload databases to Commvault. The Windows team found a backup of the main controller and the most important thing was to start communications and for every one to have Active Directory. With Commvault's support, we were also able to develop a process which recovered Volume C, and that was sufficient to fix the images. Within two months they were able to recover the whole infrastructure from scratch. Without Commvault, or with another solution based on Windows, I don't think the recovery would have been possible. 

I had never seen this kind of disaster. Nobody expects to lose everything. You think about losing the primary location or a remote office location, but no one thinks about losing the whole platform.

Among the best features are the BMR (Bare Metal Recovery), Live Sync, and IntelliSnap, which is used for snapshots of hypervisor storage. It's predefined so you only need to enable it and it works. I haven't seen anything like this in other backup tools like Veritas NetBackup or Dell EMC or TSM. We will use snapshotting for all our machines.

Live Sync replicates incremental data to remote locations. If you lose your primary data center, you enable the replicated machines in your DR location so you don't need to restore data.

It's great as a DR solution because it has a lot of capabilities for syncing with a cloud provider. But if you want to keep everything in-house, it's great that way as well because the replication is done by incrementals.

When it comes to the user interface for managing on-prem, cloud, or multi-cloud environments in one place, it's always better to have everything in one. I myself like multiple consoles, a Java console and an admin console. I only work with the Java console. It's great because it's possible to configure everything from there. But operations has that nice console, and having that one console is better than having multiple consoles.

They should move the CommServe outside of Windows machines and the database should be distributed among servers. It's still a single point of failure.

Also, I work a lot with workflows, which means a combination of XML files and commands. It would be helpful if they unified the use of workflows.

I have been using Commvault at my current company for almost two years but I have a total of five years of experience with it. I'm a Commvault engineer. I have built Commvault from scratch using the approach that is best for the client, and then prepared the documentation.

We are using service pack 16 because it is a new deployment so we have to deploy that before we push updates.

I haven't seen a crash of the database. The stability is great.

When I started with Commvault and compared it with NetBackup, I found that Commvault had features that NetBackup didn't have. Currently, we are able to cover 12,000 virtual machines.

Commvault has what it calls a HyperScale Appliance which is a media agent with the disk. This is the best option for storing data. The media agents are in clusters so they share data. It's a nice feature and I haven't seen any other backup company that has integrated this kind of solution. They always use a third-party vendor for this capability. But that involves communication over the network, something which HyperScale skips.

We plan on using IntelliSnaps more and we are testing the cloud backup. We will use the cloud as a hot-DR location. I expect that will happen this year.

From my experience, I have had the best support interactions with Commvault. I always get a response within a couple of hours. If there is a task for Commvault's development side involved in the issue, I get an update every three days that someone is working on it. 

I have yet to find a support engineer at Commvault who has to speak to someone else. They are always able to troubleshoot the issue on the first strike. I can definitely recommend Commvault support.

Our company previously used NetBackup and TSM. One of the reasons we switched to Commvault was that our company was not satisfied with IBM's support. It was challenging. If support is not able to help you manage problems, you can't use the solution.

The plus with Commvault is that it really focuses on automation for deploying machines and discovering databases, etc. A Commvault administrator doesn't need to understand, in-depth, the application he is backing up because he doesn't need access into the application. It's much more focused on snapshotting for the synchronization between locations. The BMR process can be used across the cloud and on-prem solutions, so you can easily move machines from your environment to a cloud environment. And from that cloud environment you can convert to another vendor in the cloud.

That is all built on the BMR process, which is better than any other backup tool I know. Some of them, like TSM, don't even include a native BMR solution. Instead there is a third-party vendor that does it, so it's not fully-integrated.

I like it when everything is in one console and things can be automated via an internal workflow and deployment is fully automated so I don't need to access the operating system or application platform. Those are all benefits of Commvault.

The initial setup was really easy for me because I already had experience with NetBackup and TSM. It wasn't difficult for me to understand Commvault's logic. But, in my opinion, it's very easy to understand because the logic involved is minimal yet it offers a lot of configurable options. Because the process for the installation of agents, such as for databases and applications, is fully automated, you don't need to touch the application at all. That is one of the main reasons I prefer Commvault over other tools, where you always need to touch the client.

A basic implementation of Commvault depends on the size of the company. Installation of the server takes a couple of hours, but that is the same as with other backup tools. But the installation of it on clients and their configurations will take days if you don't want to customize it because Commvault comes with pre-defined groups. The process will take a number of days for a small company.

In terms of staff for deployment and maintenance, it could be just one person involved, depending on the roles of the people in the company. This person has to be able to do a lot of things, so it depends on whether he has these responsibilities and the capabilities.

We have about 100 users of the solution because we have a lot of operations.

The ROI is there, but I don't have figures on it.

Our deployment is primarily on-prem. We are trying to assess the cloud capabilities but it looks like the cloud is more expensive if you want to have the whole infrastructure.

Commvault is more administrator-friendly than other backup tools.

We are using Commvault for cloud support, but that part is at the PoC stage. But it's the same as the on-prem solution. Whether the library is on physical disk or in the cloud, it looks the same in Commvault, so that's not an issue in terms of configuration or use. There are even more cloud vendors than I had heard of and it looks like Commvault supports all of them.

We don't use it, but there is an archive function in Commvault which allows you to move data from primary storage to another type which is much cheaper.

Version 11 of Commvault has been on the market for something like seven years now. They have changed the naming so what they called service packs are now called feature packs. That means they are no longer changing the version number and they do what they call a "platform release." That was changed in SP19. In each new pack they add new features every three months. They also have hotfix releases every week or so.

I'm still surprised that they continue to come out with features that are really nice and that you didn't even think were possible.

I've done almost everything with Commvault, e.g., back and forth centralization for file systems and applications like SQL, Oracle, VMware, and Hyper-V. Commvault does a lot of integration. 

Most of our installations are on-premise, but I remember doing one installation on the cloud.

We always work with the latest version of the solution.

We are not utilizing Commvault as it should be. Most installations are for backup and protecting data. We have it on cloud or on-premise. Most of the customers need only this. So, I haven't given real value other than backup and restore. However, we are working on this with our customers, trying to give them the culture of how to use this data and product with value. For example, using Commvault to migrate your applications. 

You can back up everything from this one backup solution. You can do backups, archives, and replications. You can backup 89 percent of the application.

It can support the backup to and from the cloud. The cloud integration with Commvault is excellent. It can support a lot of cloud vendors, like Amazon, Azure, and Google Cloud Platform.

The endpoint protection for PCs, laptops, and mobile devices is a feature that they have done a lot of hard work with. It can do backups anytime, e.g., when you have a device connected from on-premise, when are you connected through the WAN, and if you didn't do the right setup. This is a good feature.

If you have cloud applications and payment applications, you can migrate from the payment app to the cloud and also migrate from one cloud to another cloud. There is a lot of flexibility on what you can do in Commvault.

In Commvault, they used to use only the CommCell Console for backup and configuration. They have been working on a new console for quite some time now. The last time I installed the solution (maybe last week), I used the Web Console, which is excellent. Commvault can be a bit complex, but on the Web Console, they have done very beautiful work. You can do a lot of things easily and simply with the Web Console. It has 90 percent solved the complexity of Commvault. You sometimes need to log into the complex interface, but almost everything can be done from the web interface.

The Command Center is provided from the web interface. You can back up the data for everybody, but also you can give everybody the ability to view and restore their data. For example, if a laptop, machine, or environment is owned by X, then X can look in and see the environment and data that he has backed up. He can see everything that he owns and can manage the environment as he wishes. It gives him an excellent view of his environment and infrastructure. Also, if you are a service provider, you can back up data for multiple companies and give everyone an interface for their environment to manage, backup, and restore data. Commvault has done excellent work in this area. 

I would like them to keep working on the new web interface to migrate out of the old interface because the old interface is a bit complex. It was driving customers away because of the complexity. If they migrate everything (100 percent of the features), this would make the product be perfect.

We have been using the solution for two years.

The stability is excellent. Once you install and configure everything the right way, there is only the infrastructure. If there is a problem with the infrastructure, it will reflect on your backup. If there are no problems with the infrastructure, then there will be no problems. I have been working with Commvault for two years and don't remember opening more than 10 cases for a lot of customers.

It is easily scalable. You may need to add a gateway, proxy, or media server to the environment before adding more data to the environment. 

Something that is not commonly used is that you can use Appian as a backup storage solution in one integrated package. 

I rarely use the technical support because of the stability. The technical support is very good. Once you have a case, depending on the severity, there is an engineer who will connect with you. That's the most important thing when you have a problem. They will connect with you and solve your problem on spot. Commvault has a built-in feature that if it's connected to the Internet with one click you can upload all the logs. Then, the Commvault engineer can see all the logs he needs. Most of the time, it takes one hour for a problem to be solved as they have excellent support.

It's an excellent solution for cloud support. One of the important features that I am selling and trying to convince customers to use is the backup for Office 365, SharePoint, and OneDrive from Microsoft. Microsoft can be in your environment with high availability and everything will be good, but if you delete it by mistake, then for a short period Microsoft can't restore anything. Also, the way Chromebooks integrates with the cloud services is excellent.

I started my experience with HPE Data Protector, which I now hate, because it's now Micro Focus and it's killing me.

I have worked with Dell EMC. Their solution does the work, but there are a lot of the problems with the ESXi.

I have worked with NetBackup. NetBackup is good, but I haven't seen the new feature like they have in Commvault for integration.

I have also worked with Veritas Backup Exec.

With Commvault, if you need basic integration and configuration but no advanced features, then you can do the setup in maximum three to four hours. However, if you need to do everything, you will need everything to be organized for you to work.

For the backup specifically, you have to implement the basic design with every client. It then depends on their needs, environment, and how we can make their life easier. Every time, we have to change something in order to give our customers the best experience.

The solution enables our customers to save on infrastructure costs by being able to manage what were disparate data management solutions in one place. It is one of the most important features: You can do backup for almost everything from one platform. Plus, you can reduce costs by using any cheap storage and still have the deduplication feature. You can present any cheap storage for the backup and not have to worry about the B2B high cost appliances, like HPE, Dell EMC Data Domain, etc. When you can do everything from one place, it's always better. It will reduce cost on the infrastructure and human resources who manage the environment.

It was not very popular because of its previous cost, but they have been working on the pricing, and now anyone can afford to use Commvault. They changed the modeling criteria for their pricing. Previously, there was only the capacity modeling based on your content capacity. In this case, they would give you a license and you would have to pay it. Now, most of the environment is virtualized so you can have the best CPU, VMs, etc. You buy whatever you need and pay for what you need.

The most important feature that other backup solutions in the enterprise field are missing is a built-in feature for deduplication. It has a buildt-in deduplication engine and database. Therefore, you don't need another B2B vendor, like Appian, in order to do the deduplication. This is the most important feature that other solutions don't have. Most of them need another solution, like Appian or B2B storage. Also, the integration with storage and the snapshots (taken from the storage) have a lot of variety. 

I'm a fan of Commvault. I have worked with a lot of backup solutions for about eight years. Commvault is the best until now that I have worked with.

Commvault is the best for cloud integration. I tried VMware where you can back up to the cloud, but it's not easy. With CommVault, you can see the cloud environment, cloud machines and virtual machines (such as on-premises virtual machines). With other solutions, there are a few limitations.

I am still working with Veeam. 

There is also another solution, Cohesity. It is a good solution but it still has a lot to do.

Buy Commvault. It is an excellent backup solution. I would recommend the solution.

What is important to Commvault is the flexibility. E.g., if you have a new application that you want to integrate, but it's not supported, they can help you with that. They will start immediately working on it with the development. We have talked with Commvault many times, and this was one of the things that they are proud of. They can give you an integration, even if it's not integrated yet. In addition, Commvault has done a partnership with HPE, which helps with integrations.

I would rate the solution as a 10 (out of 10).

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.

We are using Commvault Cloud to back up a VM. We mainly use VM backup. We have kept our storage backups so that in case of a disaster or test environment, we should be able to recover within fifteen to twenty minutes. This is our benchmark.

Commvault Cloud has helped in reducing the cost for hardware as we are just using standard storage to store the backup instead of requiring special hardware equipment. It allows for server-level hardware backup, which helps in managing storage backups efficiently.

The most valuable features of Commvault Cloud include deduplication and compression. Deduplication and compression are critical for us because they provide good compression, which is essential in data management. The time to recover from the disk is a critical requirement. The ransomware protection feature was one of the key considerations for choosing Commvault Cloud.

In terms of improvement, the cost factor is a significant area for enhancement, especially during the annual renewal. Competitive products have emerged with less cost, making the pricing a challenging factor. The implementation of field-level restore where you can restore a particular table or field without having to restore the entire backup is something I would like to have.

I have been using Commvault Cloud for almost three years.

So far, we are all right with the stability of Commvault Cloud.

We have some questions regarding scalability with the current storage setup, particularly with the Synology basic storage we are using, which causes continuous issues. We are evaluating backup storage solutions due to underlying hardware issues.

I do not have any negative feedback regarding Commvault's technical support. They have been clear and helpful in addressing our concerns.

Positive

We previously used Aksel backup, but we faced challenges with VM level backups and required protection against ransomware, which Commvault Cloud provided. The ArcServe backup software did not have these features, and as a result, we switched to Commvault Cloud.

I was not involved technically in the initial setup. I was involved in the evaluation process, and subsequently, my team handled the implementation and deployment with our partners. The setup took approximately three to four months and involved minor implementation challenges.

The deployment involved our team and partners. From our side, we had two people handling it, and from the partner's side, one or two guys were involved, making it a team of around four to five people.

The major ROI was using simple storage instead of expensive high-end storage for backup. It is more compliance-related, and we utilize cloud backups for redundancy and compliance purposes. We have not seen significant ROI from the backup solution as a whole.

Pricing is a significant factor for our company as the annual renewal is challenging. There are competitive products in the market that have lower costs, which adds to the challenge of the pricing factor.

We evaluated Veeam backup as an alternative. Commvault Cloud provided better pricing at the time, along with ransomware protection and deduplication. Additionally, at our time of evaluation, Veeam did not support mixed backups, which was a consideration for us.

I'd rate the solution eight out of ten.

The solution has the fastest backup and better licensing.

Compared to Rubrik, MongoDB Data Protector, and NetBackup, Commvault is better. The licensing team was quite tricky recently because they stopped the unlimited files for that license. Commvault made a bank of 500GB only, a node-based license can take it, which is disappointing. Reporting needs to be more granular. Also, there should be a showback of data being backed up, and the backup cost to share the cost internally with the department.

I have been using Commvault HyperScale X as a customer. I have almost nine HyperScale nodes and expect four more nodes this year.

The product is scalable. To scale, we need to buy more agents. We’re using HP hardware for HyperScale. We’ve three backup administrators working with the solution.

The customer support is interesting, but they need to work on their competency. My team is happy.

Positive

I work with a couple of other solutions, such as HP Store, Veeam, NetBackup, MongoDB Data Protector, and Rubrik. Commvault is the most competitive in the market because local support is easy and faster.

The solution is easy to implement if you have a proper infrastructure and require two people to set up.

The solution is bundled with hardware licensing. If I want to increase the hardware, I have to buy exactly the same because it's based on the core hardware license. We cannot tell discount because we have an NDA signed with Commvault because of my academic license. The solution is more expensive than NetBackup and Veeam but cheaper than Rubrik.

The solution is easy to use after four months of training. Before implementing, make sure you negotiate well and agree to the terms and conditions in advance. Once you implement it, you will use it for at least the next five to six years. So, you must negotiate and file a contract, the best way to know the cost of ownership in the beginning itself. Overall, I rate the solution an eight-point five out of ten.