Commvault Cloud Reviews

We use it for server, laptop, and desktop backup.

We are using the latest version.

Commvault helps our admins minimize the time that they spend on backup tasks and other projects since we are now managing a single console to administer all the backups, instead of a full console.

It is a very good tool for server backup. We can restore any server, e.g., physical or VM, in a very short amount of time.

Commvault Command Center is very good and user-friendly. We can select any user's data or a server in its Console.

Commvault provides us with a single platform to move, manage and recover our data across locations. Especially for our IT, this is a very important part of our data storage.

The recovery option is very good. It is a user-friendly option to recover any data.

When we started using Commvault, we felt that there were some technical issues with managing it, but we are comfortable enough with managing it now. There were many issues, like index corrupting, when we first started, but all those issues were resolved by the Commvault tech team.

Its major disadvantage is it's expensive. Otherwise, the solution is good.

I have been using it for the last six months.

It is a very stable solution.

Scalability is very good.

We use a third-party to resolve issues first. They first try for L1 or L2 support. If they are unable to fix it, then they escalate it to Commvault technical support. 

The support is very good. I would rate them as eight out of 10.

Positive

We were using Symantec Backup, which did not have features like centralized management. Commvault has a centralized, single console where you can manage multiple locations of user's desktop data, which is one of the important features of Commvault.

We switched to Commvault because we were looking to centralize management. This reduced IT administrator time as well as providing stability and reliability for data backups in a single console, and we didn't get these features from Symantec. 

It reduces IT man-hours by an hour per day.

The cost for Commvault is very expensive, even support is very expensive. The full cost of the solution is 50,000 INR per year, which includes 20 VM backups, server data backup, and 200 desktop and laptop agent licenses.

They have recurring support changes.

They should reduce the support and license costs so anyone could start using Commvault. Due to its cost, customers are reluctant to use Commvault.

The first time, when building infrastructure, the cost is quite high.

We evaluated Veeam and Veritas NetBackup. 

We chose Commvault based on some customer feedback and technical reviews of Commvault. The main difference of Commvault is the single console to manage everything.

Go for Commvault. It is a very strong, stable solution. Technically, it is a very reliable solution with a single window console to manage all backups. Definitely, we recommend customers should go for Commvault. Though, it would be nice if Commvault could compromise on the pricing part.

I spend two hours every day on Commvault monitoring and managing performance as well as fine-tuning.

We implemented on-premises, so it is not connected to any public networks. Therefore, hacking is very difficult.

I would rate Commvault as eight out of 10.

We use Commvault to back up our employees' data. I work for a retail organization, so our users aren't in a single office. Before we were using a backup solution that could only take a backup in one office at a particular time. This was a disadvantage for us because the users kept shifting from one office to another. In some cases, we'd need a critical backup, but we couldn't do it. That's why we switched to a cloud-based solution.

Commvault can perform a backup no matter where you are, and it takes a backup every four hours. No matter when you come to the office, it'll take a backup if you're connected to the internet and check the system for online availability. Commvault has reduced the time administrators spend on admin tasks. I can monitor all users from a single place and see when they have performed the backup or when they've notified us of a lost backup. 

Before, I spent at least one or two hours each day monitoring the backup solution. With Commvault, I log in once in the morning or the evening for 10 to 15 minutes, and I can check everything on my laptop. Now it takes me, at most, half an hour to oversee the backups of the 300 users I monitor.

The interface is easy to use. I would rate the interface nine out of 10. It's a single console where you can create, modify, and delete users or you can transfer permissions to other users. Even if I remove the license, the laptop will still be there in Commvault for some time. If your laptop is dead, it's still a live location, so we can check it. If the laptop is connected to the internet, we can see exactly where it is, whether it's in India or the US. Restoration is super easy. From the admin console, we can restore a user's data no matter where they are. If a Commvault instance is installed on that laptop, we can restore it.

Ransomware protection is another special feature in Commvault. They have predefined some extensions. When Commvault identifies a ransomware attack, it will stop taking the backup on those extensions. We haven't had that happen yet, but Commvault can contain and control a ransomware attack.

We've been using Commvault for three years. We completed our two-year subscription and renewed it, so we're now in our third year.

Sometimes the web page doesn't work. I don't know if it's an outage or if there is maintenance going on in the background. From time to time, Commvault will suddenly stop taking backups for some intervals. We'll raise a ticket to the support team, and they'll get it sorted out. Still, I would say it's working 99 percent of the time. We can take the backup, restore data, and everything else. But sometimes it stops work. For example, today it went down for a minute.

There are no limitations for us. We are interested in indefinite backup for deleted files. Even if I delete the file, it'll be there permanently. I don't foresee any issue with that.

I rate Commvault support nine out of 10. When you raise a ticket, they immediately assign the engineer. If that person can't solve the problem, they will escalate to a higher engineer or management, who will get it fixed immediately. The size of the account doesn't matter either. If you have an issue, they will try to fix it quickly. They don't give special preference to their larger customers. 

Positive

We were previously using a homegrown solution called Retrospect. We switched to Commvault because it's cloud-based.

I was at the company when we first deployed Commvault. The overall deployment takes time because it depends on the users' availability. We can't take all the backups together also because we also have time constraints. It depends upon the user availability we have completed this activity. Our IT team has five members responsible for maintaining Commvault, so all five know how to work with Commvault. We also have different offices with varying levels of access, but they can't perform configuration changes, 

Commvault worked with our team during the user acceptance testing. In the UAT phase, everyone was a little uncomfortable because we didn't know what all the options were. But Commvault has a team in India who helped us to check everything. We were satisfied with that. When we had issues, an engineer took the call and sorted everything out. After that, we didn't have any problems with the configuration.

I feel like we've gotten a lot of value relative to what we've spent. Employees no longer have to be in the same office to access the backup solution. If a user working from home wants to restore data, I can directly restore it to his laptop. There's no time delay for solving user issues. We've also cut down on storage costs because an in-house solution requires you to spend money to keep that much data.

We have evaluated three or four cloud-based backup solutions, but the other ones in the market didn't even come close to Commvault. We looked at solutions by Sophos and Veeam, but those didn't have even 50 percent of what Commvault offers.

I rate Commvault nine out of 10. It's a wonderful platform for IT professionals. I would suggest Commvault as the backup solution for any company. However, it still has some room for improvement.

We are doing backups for a customer's 365 tenant details. This is for 365 backup and recovery. The applications that it protects with backups include: all the details on 365, SharePoint, Team, and mailboxes.

Our client does the needed backup within our required window. We have a daily backup at 11:00 every day. We have not felt any pressure or performance issues with our 365 tenant.

The restore has been great. It has been faster than doing restores with the on-premises solution.

Quick backups and restores of data are the most valuable features. It is important that it is an easy solution to integrate with the SAML authentication of the tenant, so we can have the users log into the systems and do their own restores, if needed.

Metallic's backup & granular recovery of data for Office 365 works great. We have tested it many times for production reasons. We have done some tests and have always managed to do the recovery as we wanted and without any issues.

For simpler environments, they have some templates for startups. Possibly for a smaller environment, they need to do more automatic configuration and selections of users who want to do backups. This is mainly for smaller environments. I would like them to have the same system fit for all environments: small and big environments. Currently, we have to do a lot of configuration of the layout, which takes time. This solution is appropriate for enterprise-level enterprise, but I would like it to be easier to use for SMB environments.

Less than half a year.

Up until now, it has been a hundred percent working great. So, it looks stable.

Our customer's environment is not that big, but it looks like it can easily handle a big environment.

We back up a little less than a thousand users, whom we are licensed for, and a lot of them are company employees. 

There are two sysadmins managing the solution. One of them mainly does the monitoring and getting the work on the system.

The technical support was good enough when we needed their help. They were available for assistance and gave us good support. They fixed the issues that we had in the system. 

When we looked specifically for a solution that would hold the backup on their cloud environment, Metallic Cloud was what we wanted. We didn't want to bring the solution into our environment, but we wanted the whole solution. Metallic was exactly what we were looking for. From my point of view, Metallic Cloud was the best solution that we could find.

Previously, the client didn't have backups for the 365 report. People who deleted their emails or files on SharePoint just lost them. So, this solution was quite important, because trying to do backups from an on-premise environment wasn't successful. It took a lot of time because of the low bandwidth over the Internet.

This solution mainly gives us backup functionality that the client wasn't able to do before. It is saving them a lot of bandwidth over the Internet and giving them functionality that they previously didn't have, such as, backups to their 365 tenant. They save 150 to 200 Mbps for nightly backup runs.

Most of the important things were straightforward. It was quite easy. It is a SaaS-based, web-based configuration. It is very simple and easy. You learn by some kind of runbook, step-by-step. That's it.

In a couple of hours, we finished 80% of it. Over the next couple of days, we did a couple of tunings.

We did a PoC at the beginning. We weren't sure that we were going to purchase it because we didn't have experience with this product before. So, it was a testing environment first. When the test environment went well, we just went into production. We went from PoC status into production status. 

After we decided to move to production, we decided what would be our guiding rules for system backups, e.g., what would be the policy that we would have to decide internally. We had a small discussion about what we wanted to back up, what was the policy, who should do the management, and who should get the report. It was some type of late policy implementation after the product was already working in backups because we just moved from PoC to production immediately, which was easy enough.

The first backup is always long and takes a lot of time. After that, the daily incremental backup speed is quite fast.

We had some small issues, but we received good assistance from their support to fix those issues. The issues were mainly report type issues and changing it from HTML to PDF. These were very limited, small issues. I think they were related to small bugs in the versions. The support was helpful. So, we just got support for the issues that we had encountered during our implementation. Otherwise, we did the implementation ourselves.

One and a half people were required for the deployment, one of the system engineers and myself (as CISO of the company). I did most of the configuration, then one of the system guys helped with the SAML configuration of the Azure tenant.

Metallic has reduced the amount of manual work required to manage our client's backup operations. It is reliable. We trust it and don't need to monitor it as much as another backup. This is quite labor-intensive, manual work, so it saves our technician time. It is saving us an hour or two a day.

It is not the cheapest solution. I think the pricing is fair for mid-side customers. It is between all the other options.

Costs are fairly predictable because you pay per user. It is quite easy to do the calculation.

If you have different use cases in the 365 tenant, I am not sure that the product gets the full agility of those licenses. If I want to do backups for just some of the users, I still need to do a backup for the full SharePoint and have a full license for all of the users who use SharePoint. If there could be a higher variety of license type for this that reduces the cost, that would be a nice functionality.

We were looking for a backup solution to do backups for all 365 data as well as SharePoint, Teams data, OneDrive, and mailboxes. We wanted all the data located on our 365 to be robust from one side, but easy enough to manage from the other side, not complicated, and reliable. After we did the PoC with Metallic and found it a suitable solution, we decided to keep working with it.

We mainly decided to use Metallic because Commvault has a good solution on-premises. We know Commvault as a company. They have a good product and we have a good relationship with them. Commvault is in Israel, so we decided to try the cloud product in the environment, and it was good.

We did PoCs with all the options that we evaluated. We mainly checked the supported functionalities and eliminated those that did not support our required functionality. In the end, we had two options and decided to go with Metallic.

I would give Metallic's overall ease of use as an eight out of 10. It is not too complicated. It is quite easy to use for people who are familiar with Commvault. They can understand the language pretty quickly. If you have Commvault on-premises, which we have for the same customer, you can understand the language of the solution pretty quickly.

Know what policies you need and what you want to back up beforehand. If you are planning to do backups of a few users, and not all your users, research the type of applications you need to do backups, e.g., if you need SharePoint, mailboxes, or OneDrive. Each of these applications behaves differently regarding license activities.

I would rate the solution as a nine out of ten. Nothing is perfect, but it is a really good product. There were only small issues/bugs that I found in the beginning, e.g., small report issues and it was a little bit complicated the first time configuring for SMB users, which is a bit more complicated with limited options. However, since we have experience with other products, it was fast. I don't know another SaaS product doing 365 backups better than Metallic. This solution is the best one that I'm aware of.

We used Commvault HyperScale X to increase the security of datasets, to be sure that all data and all backups that we have are secure, and that we have them in another place, such as disaster recovery. The idea is to always have a third copy somewhere else. The initial idea was to have a third copy of that backup sets to be in the state government data center. However, before they finish, I left Ministry, and they have not finished that job.

Generally, the idea is to have a possibility, for all backup data, after some time, to be saved in another place. For now, everything is still inside the Ministry. 

Commvault HyperScale X has increased the way our organization functions by adding more security to the backup sets. In case the primary location is disabled, or there is some problem with the primary location, the second one will continue to work. The idea is to always have a working backup.

The most valuable feature of Commvault HyperScale X is the automatic nature of its operation. We don't need to worry about sets of documents. It worked automatically, we don't need to think about it. When you set the solution up in a good way, you don't need to worry.

The price of Commvault HyperScale X could improve.

I have been using Commvault HyperScale X for approximately one year.

Commvault HyperScale X is highly stable.

The scalability of Commvault HyperScale X is good. It is simple to add more systems or server storage.

We have approximately 400 endpoint users and 40 terabytes of data being used. 

We had to use the support and they were responsive and quick. They fixed the problem, not immediately, but the timeframe was dependent on the ticket type. They were always there to help. They did regular call checks until everything was resolved. 

We used many different solutions previously. When we had some large issues in 2015, I decided to buy a professional corporate solution for all the systems. We did test some other solutions, but with Commvault HyperScale X, we received what we needed and much more. Additionally, Commvault HyperScale X was easy to maintain and use.

The solution was easy for us to implement because we have been working with Commvault for many years, and we know what to do. The initial setup alone will that approximately two weeks. The longer portion is buying the hardware and setting it up.

I rate the initial setup of Commvault HyperScale X a three out of five.

We did the implementation of Commvault HyperScale X with a local partner. They installed it and did the setup. For us, it was easy to add new features to the Commvault HyperScale X backup.

The company that has the solution is managing the solution.

We have seen a large return on investment by using Commvault HyperScale X.

The price of Commvault HyperScale X is a lot higher than competitors. As a government institution, we have annual costs. We made a budget for one year in advance. It was difficult to calculate the other solution's costs because each solution has another way of licensing. The solution is expensive but it is very good and we know the good quality we will be receiving.

There were not any additional costs. The new storage, software, and support were inside the price.

We did evaluate other solutions before choosing Commvault HyperScale X.

The solution has changed since I have used it but what I know is the solution offers companies the possibility to have their own backup storage.

I rate Commvault HyperScale X a ten out of ten.

It is used as an enterprise backup solution.

We have a very good disaster recovery solution with Commvault. We have a standby CommServe where logs are being deployed every five minutes. If something goes wrong, we are immediately able to recover and enable services on the standby server. We are achieving 99.9 percent SLA with respect to the backups.

It also helps to ensure broad coverage through the discovery of unprotected workloads. We can easily identify them in the Web Console where we can see which of our servers is not protected. And if there is no backup for more than one day, we can get a report, and we have also enabled alerts. Those features are really helpful to us in identifying and addressing issues.

Commvault minimizes the time we spend on backup tasks. I only have to check the health of the CommCells, and the rest of the time I can work on the other tasks.

It's a very good enterprise backup solution with multiple features. We are able to take a backup of multiple databases. We don't need to use scripts to schedule any kind of local backups. We have a direct plugin for Commvault so that we are able to take backups of any of our databases or application systems, like SharePoint. Commvault is also enabling backup for PaaS services that are deployed on the cloud.

Commvault provides encryption mechanisms with the latest standards that our customers are looking for.

The CommCell console is very good and user-friendly. I have experience with NetBackup, HPE DP, and Backup Exec, but I'm really comfortable with Commvault. The console makes it easy to identify exactly what we need to see. For example, there are multiple categories. If a backup needs to be performed on multiple systems, we just configure one client or one group and we can push the agent straightaway. That's a very good feature that helps us to complete tasks on time.

We can integrate our multiple CommCells in the single Web Console as well and that helps us easily identify how many servers are getting backed up and how many servers are not being backed up. We can see the SLA and the success rate. And even though our customer is huge, we can give them access and they can easily see the SLA and the success rate of the backups. Commvault also recently launched the Command Center. It is very good, enabling us to deploy server plans. It is very good and user-friendly.

For disaster recovery, there is a feature called Live Sync, and we are also able to export disaster recovery backups to the cloud. If something goes wrong, we are immediately able to recover and continue with business.

In addition, if something goes wrong and a backup fails, we can trace the issue using the log. Each service has a different log that clearly gives us information about the exact reason for the issue and what needs to be done.

We have multiple workloads, including SQL, Oracle, SAP HANA, especially Sybase, as well as file systems, VMs, and Exchange mailboxes. Commvault provides very good support for them. We perform 70 to 80 restores on a monthly basis. Over the past year, I have faced challenges with one or two restores. All the rest were completed successfully. And if we get stuck, we can easily use the logs to identify the issue and to make some changes to the configuration. So we are approaching a 100 percent success rate with respect to restoration.

Commvault has very good procedures for performing backups and restores of SAP HANA databases. As far as I know, no other technology provides an option to perform a restore directly from the backup tool itself. We log in to HANA Studio when we have to perform a restore and Commvault enables this by default. We are able to do the restoration from the Commvault GUI itself.

Commvault also provides workflows. If you want to decommission a client's systems, there is a workflow where we just have to add the client to it and we can easily complete the task. This is useful when we are informed that a customer is moving out. It would be a huge task for the backup team to retain the backups for such-and-such a period of time and to release the license. Running this workflow makes our work very simple and reduces our efforts as well. The multiple workflows really help us in completing tasks quickly.

Overall it has great features that fulfill our customers' expectations.

I have been using Commvault for the past seven years.

The stability is very good. If you don't follow the metrics and best practices recommended by Commvault, or if you mess up the setup, you may face challenges. If you follow the best practices, it's a very good, stable solution.

We can easily expand our licenses and deploy Commvault for our customers, which keeps our business going. From a scalability point of view, I haven't seen many challenges.

We get very good support from Commvault if we run into any kind of production issue. They maintain a very good SLA for critical and high-priority tickets. We are really satisfied with their support.

For example, let's say that something in production is down or multiple customers are impacted. SAP won't join a call and help us in resolving the issue. But if we have a critical CommServe-level issue, and multiple backups may fail, Commvault can easily jump on a call and can help us in addressing this issue. In reality, if something is wrong with a SAP system or if an OS is not functioning, a customer may not be able to do their work. Whereas, without a backup, they can continue their business, but they cannot recover things if something goes wrong. Still, if we raise a high-severity ticket, based on the criticality, Commvault support will definitely jump in. They can help us in one hour, at the most.

Positive

In one of my older projects, deployment of Commvault was simple, but the current one is complex. It's a very big environment. It depends on the environment of the client and the requirements. If you have a shared mechanism and the customer has multiple firewalls at their end, it will be very difficult to integrate multiple customers into one CommCell. But if you have a single project and a dedicated customer in a single domain, it will be very easy.

Compared with other backup technologies, Commvault is a bit more costly, but we are satisfied with the support, the services, and the features that we get with Commvault.

We are using the capacity-based license and have a total of 10 CommCells. In the license file, we can clearly see what kinds of workloads can be backed up.

Veeam is very useful for Windows-related platforms but we chose Commvault because it does not have any kind of platform dependency when it comes to backups. It has multiple features enabling us to backup Oracle RAC, or Exchange DAG, and IBM Lotus Notes, and any type of PaaS services.

Commvault has a clear-cut, three-tier architecture, whereas others follow a two-tier architecture, other than NetBackup, I believe. With Commvault, every backup load will be taken care of by the MediaAgent, and administrative tasks will be taken care of by the CS. Evn the CommServe size also not be huge when compared with other solutions.

With respect to security, in particular regarding ransomware, Commvault has built-in features that we enabled to protect our environment. As for storage targets, every storage array has its own built-in mechanism for encrypting or securing the data. It is very difficult for a third party to enter and to make any kind of use of the storage arrays.

Storage cost completely depends on the retention the customer is looking for. If they have, say, a 1 TB system and they're looking for more than two months' retention, there will be a lot of storage utilization. But we do get a very good duplication ratio, close to 90 percent for file system backups, which helps us to minimize the cost.

Overall, if your infra is very good, once you configure Commvault there are no challenges. It will function well. If something is wrong with the network, obviously, any backup technology will end up with issues. But Commvault is very good.

We are using it for taking backup of our virtual servers and some physical servers.

We were searching for a tool to backup our virtual machines when we bought Commvault. I was already using Avamar to backup our desktops and laptops on a daily basis. We are using Commvault to take backup of servers. Both are good, but if I compare Avamar and Commvault, Avamar is better than Commvault. Avamar has hardware, but Commvault is a software-based solution.

Prior to implementation of Commvault, we were doing backups manually; shut down the virtual machines, do backups of entire machines, and then restart the machines. The administrative time has been drastically reduced now.

We used do manual backups of every virtual machine. A machine of 50GB would take around two hours to backup. This is the downtime. We had to shut down the machines and take the backup. But with Commvault, the major benefit is that we never shut down the machines. Every server is online and the backup is also online. So we reduce the downtime and administrative overhead.

The setup is complex. It's not simple to install the machine and start a backup. 

Commvault is software based, unlike hardware-type devices.

We have used Commvault the last three to four years.

It is stable. We don't have any problem regarding the core part of Commvault.

The solution is scalable. It's a software-based solution so we just need a license to expand it.

I have Avamar servers that we have recently updated storage-wise and capacity-wise. So we don't have any immediate requirement to increase the licenses of Commvault.

We have the technical support of Commvault, but in cases where little support is required, we call F1 to help us.

The initial setup was complex. The setup was implemented in one day, but the fine-tuning took longer to work through.

It has three to four parts. The server is one, storage is another, and the agent is another. It's not just a simple thing you have installed in a machine and start to do backups. It is a very new product for us, so we needed installation support from a partner. We are not the IT guys. We are a manufacturing industry, and we have a little knowledge of everything but are not really part of each type of hardware and software. It required an expert who had already implemented elsewhere to help us.

We hired a third party, F1 Technologies, a local support partner who implemented the total solution with us.

Commvault's license fee is per server-based for physical machines. For virtual machines, it's a 10 VM one-pack solution. Avamar is just a license for storage capacity-wise, around 8TB to 16TB. It's not based on how many servers you backup. In a price comparison, definitely Avamar is the winner.

I'd rate Commvault a seven out of ten.

If your organization does not have many hosts, I would recommend using Commvault. But if you have more than 50 to 100 hosts, Avamar is the better solution as it's more stable than Commvault. When you buy Commvault, you need to buy hardware separately; servers and storages are a different part. With Avamar, you have a complete solution with hardware and software, so it's better.

It's being used as our main backup and recovery product. We use it to back up virtual machine infrastructure, using VMware and/or Nutanix. We use it to back up our SQL, Exchange, and File Systems, where is a mixture of Linux, Windows and Solaris. We also use it to backup NFS and CIFs Shares under NetApp. We also use Commvault for Oracle Backup and/or RMAN Clones.

We migrated everything we had from other vendors to Commvault. About 95 percent of everything in our environment, is being backup by Commvault.

On-Prem, Cloud, Data Centers.

The disaster recovery features of Commvault have improved the way we operate. In the past, we had a very complicated process for testing disaster recovery. That kind of testing is one of the nice features of Commvault. You are completely sure that your data resides in multiple locations at the same time and you can be sure Disaster recovery Data it's there in case you need it. 

HyperScale X also helps our admins to minimize the time they spend on backup tasks so that they can spend time on other projects. We are a big company and we have at least 80 locations using Commvault. We have admins for it in four or five regions on different continents. Overall, I would estimate HyperScale X has improved our productivity by 30  to 35 percent. We are more productive using Commvault than with other backup software.

It has also helped to reduce storage costs. We chose the solution because it decreases the backup costs for our end-users. We have been able to reduce backup costs by at least 50 percent.

There are a number of features we like HyperScale X:

• The deduplication is pretty good. 
• We also like the ability to generate reports using the Command Center feature. 
• We like how the software upgrade process works. 
• From the start, the disaster recovery for the CommServe has been very robust and flexible and works pretty well. 
• It also provides us with protection from ransomware, by default for Windows, and it can be enabled for Linux as well.
• Replication and Auxiliary Copy features, like dynamic throttling, are helpful.
• There is also the flexibility to create self-service capabilities for end-users and to give them access to restore their managed servers for data.

In addition, HyperScale X provides a single platform to move, manage, and recover data across all locations in our environment. The CommServe is the brain of Commvault. It's the server where the index and the cache are stored for the backups that are happening in the environment. All the management is centralized from that CommServe server. You can manage all the clients and all the infrastructure using one interface and one server. For redundancy, you have a disaster recovery CommServe server in standby mode. You can configure a disaster recovery backup to happen every 15 minutes.

Using the Commvault interface, you can customize and generate multiple reports to easily see what is protected and what is not protected in the environment. There is also a third-party feature called Commvault Activate. It's a separate product and you need another license to use it. That product specializes in discovering the environment, and the data in it, that you are not backing up.

You can manage everything from two interfaces. There is a Java console (CommCell), but in the near future that will be fully replaced by the Command Center, the HTML5 interface. The Java interface is not great. The Command Center interface is far better and it looks nicer, but it doesn't have all the powerful features available in the Java console. The place to improve the product is on the management interface level because that's the point where it's not perfect.

Today, to manage the product, you just have to use both interfaces. The Java interface is basically for the admin because it has all the powerful features in it. The HTML5 interface is mainly used by end-users, and by admins when they just need to generate a report or see something graphically to help with the management of Commvault.

One other note. I would rate the ransomware feature at about eight out of 10. There are different processes for enabling ransomware protection on Windows versus Linux systems. In the current version, there is no ransomware for HyperScale X. That feature has been released in CV SP 24.

We have been using Commvault HyperScale 1.5 and HyperScale X for the last three and a half years.

It's pretty stable. We haven't had a major issue in the three-plus years we have had Commvault. 

There were some issues in the first year, until we managed to acquire the skill sets and learned how the product should be used, including the best practices. But overall the environment is pretty stable. 

We perform a disaster recovery test twice a year and the product is robust and resilient.

The solution is pretty scalable. You can grow the environment. We have been using the same CommServe server for the solution for the three years that we have had Commvault, and we have just scaled and scaled the solution. We started with about 3,000 clients and now the number of clients has doubled or tripled.

HyperScale X, which was released one year ago, is more scalable than version 1.5. You can put more nodes in one cluster and, because of that, you can increase your overall storage.

We don't have the Commvault Activate solution. We are thinking about acquiring it in the near future to improve our environment. Our migration from other vendors to Commvault took between one and two years because our environment is so large. Right now we are fine-tuning the product and the processes around it. Perhaps we will use Commvault Activate starting next year. It will be in our scope.

Support for the product is pretty responsive and pretty good compared to the other vendors. Commvault's support is far better than Dell EMC's support.

If you hit an issue or a bug, Commvault support is there. And it's pretty easy to solve something that support cannot handle, if it's a bug that needs to go to the Commvault developers. We have initiated sessions with their developers to solve an issue that was affecting the environment. Because support is responsive, you can solve almost everything.

And if you need a feature that is not available, Commvault developers are responsive there too. They usually integrate such requests within a few months, and after that it's available for use.

Positive

In the past, we used Dell EMC NetWorker and Dell EMC Avamar. The main reasons we switched to Commvault were the storage and backup costs. We wanted to find a cheaper solution. In addition, we wanted a solution that we could manage using a single interface, versus the multiple interfaces that we had with Dell EMC. Third, we wanted something that was simpler to manage and that could perform disaster recovery much better, including disaster recovery testing. We also wanted the ability to upgrade agents and software in a centralized fashion. We have seen an improvement on all of these points with Commvault, as a replacement for Dell EMC.

The initial setup process is pretty complex. I was involved with the product from phase one. There are multiple points where you need to configure the product to have it functioning well in your environment. It's a complex product. There is a lot of stuff to set up from scratch to have things working as expected.

The time for deployment depends on how much infrastructure there is and on how many media agents and VSAs you need to deploy in the environment. For the first deployment we did in our environment, it took us two or three days to finish all the settings. But we were new to Commvault and we needed some time to understand it and to familiarize ourselves with all the options. Today, if we need to deploy a remote, on-prem site, where there is one media agent and one VSA, where the requirement is to back up a small or a medium site, the whole process can be done in a few hours. We work with Commvault's professional services to automate some of the deployment steps using Commvault's workflows.

Initially, we had about six petabytes of data that had to be migrated from one environment to another. It was pretty complicated because we had to disable the backup in one place and enable and configure the backup in another place. The process was also complicated because we had to look at the remaining space, how many workloads we needed to migrate, and how much had been migrated. We had to create procedures and train operations.

Commvault was new to everybody in our environment. Everybody had to become familiar with it and with the new processes and procedures. We had been using another technology for five years. Today, everybody in our operations, in our engineering, and our managers, is familiar with the product. Now, because we know the processes, everything moves much faster than it did in the past.

We have decreased the cost of our backup infrastructure using Commvault, by 30 to 35 percent.

Also, using Commvault HyperScale X has taken us to new ground where we can offer self-service recoveries to our customers and give them access to whatever server they manage. The other plus is the automation that we can create with Commvault's workflows to decrease the time it takes for a site deployment. That also translates into money saved because instead of having one admin resource occupied for a day to deploy a site, we can deploy a site in five minutes.

The pricing is far better than we had in the past. The license for Dell EMC was not too expensive, but the storage, given that Dell EMC is based on data domains, was pretty expensive.

We evaluated Veeam, as well as Dell EMC NetWorker and Avamar. Before we bought, we ran some try-and-buy and some PoCs in our environment, to see how the products handle things. We were convinced that Commvault is better and fits better than the old product, and we acquired Commvault.

The pros of Commvault are that you can manage everything from one console and the disaster recovery scenario functions much better than with Dell EMC NetWorker. Also, Dell EMC Avamar was specialized to back up VMware environments and NetWorker was specialized to do them all. We wanted a solution that could do all the backups that are required in our environment. Veeam was not able to handle all our backup scenarios. Veeam is very good on VMware backups, but you cannot do Oracle backups, SQL backups, or file system backups. We were looking for a solution that could fit all the backup requirements, operating systems, and appliances that we have in our environment. There are very few products that can cover all of them, few of them are: Dell EMC NetWorker and Commvault.

Involve Commvault support from the start, at the implementation level, to be sure that you implement the infrastructure with best practices. What can happen is that, a year after you implement the infrastructure, you notice that your clusters have not been properly set up and it's too late to change anything. Use their support during the implementation. Have some sessions with them to understand the whole infrastructure and the whole process of deploying HyperScale X.

We made a mistake in our first implementation, three years ago (Hyperscale 1.5). The recommended number of nodes per cluster was six, but for some reason we added nine. Because of that, we had some issues. Don't make the same mistake. However, HyperScale X, released in the last year, is a little bit more scalable and more flexible. Clusters can exceed nine nodes and can be extended further (current limitations per cluster are around 5 PB).

If someone is buying Commvault today, they should try to buy HyperScale X. It's the next generation and has some advantages. It can help avoid issues with clusters, moving forward.

Overall, we have been impressed by the features of the solution and by the responsiveness of Commvault's support. We like the product and we feel we made a good decision in acquiring Commvault and working with them. We are pretty happy.

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.