Commvault Cloud Reviews

We are a partner and a service provider for Commvault in the Middle East. We use it for both backup and recovery, and sometimes for replication. 

It has on-prem solutions and we are also going with Azure.

Commvault is the first software company to release software for Nutanix AHV backup. We have an implementation here, with a government company, where we are taking a backup of the Nutanix virtual machine and their database, and replicating this backup to the DR. That way, if the main site is down or something has become corrupt or something is wrong with the backup, they are able to restore from the DR backup. It is the largest implementation in the Middle East.

The solution provides us with a single platform to move, manage, and recover data across on-premises, hybrid, and cloud locations, making it very effective. We can replicate the data even when building a new data center for DR. That makes it easier for us because from there we are able to restore using Commvault.

It provides us with a single console where we can back up our software, our databases, and even our desktops and laptops, even if they are connected remotely, at any time and from any place. Whenever the bandwidth is available and whenever the process is available, it will take a backup.

Commvault also supports most of the cloud vendors. We can back up cloud-based applications like Office 365 to on-prem, and we back up our on-prem data to the cloud as well. It can be anywhere, either local or in the cloud.

It helps to minimize the time admins spend on backup tasks. Once it is configured perfectly you can forget about it, in terms of administration. It saves our admins along the lines of 20 weeks per year.

And with Commvault, you don't need multiple applications to back up different kinds of platforms. It can be OpenStack, VMware, Hyper-V, a physical machine, or Oracle. It's a single point for backups.

When it comes to saving on storage we are saving 20 percent. In terms of storage optimization, it is seven times more efficient. You can store 700 TB in about 100 TB of space.

We have helped many clients to recover from ransomware using Commvault. For one of our clients, we were able to get them back into production in one week. That was an environment with 200 servers and 1,400 user backups. Without Commvault it would have taken some months.

One of the most valuable features is the encryption which helps save you from ransomware. Because the data is already encrypted, it cannot be encrypted again.

The restore performance is better than with any other product. That's why Commvault is number-one in industry reviews.

With Command Center, you can view the backup schedules, the running backups, and the data availability.

It takes a lot of technical expertise to implement. Commvault could increase the training it provides to customers and partners.

Also, with technology changing, it could use more features. Maybe they could include artificial intelligence.

We have been using Commvault since 2015.

The stability is really good. Once you implement it properly you can forget. It's an automated solution. You don't need to troubleshoot anything.

As software, it's scalable. You can add any number of licenses as often as you want. Commvault has options to scale using appliances and software.

Commvault's technical support is really good. I would rate it at nine out of 10.

We have used Veeam. Commvault is more of an enterprise product. In terms of the scope of integration across multi-cloud/hybrid environments, Veeam is a five out of 10, while Commvault is an eight.

The setup is not straightforward. It is a little complex. It really needs expertise, unlike other software.

The deployment time depends on the size of the environment, the number of servers and the storage size. It has taken us anywhere from one week to three months.

As a result of our experience in setting it up, we have created our own plan for doing so. We do a complete environment study of the client by using a solution survey sheet. That gives us complete visibility into the databases they have, the number of servers, the virtualization platform, and the physical machines. According to that, we suggest a plan for the size, if it is on-prem. We have a project management professional to make the process smoother. We have four engineers who implement Commvault and they are also responsible for maintenance.

ROI with Commvault will take about five years. It's cost-efficient when it is used at the enterprise level.

Some years ago, Commvault had a huge price. Now, it is cheaper than Veeam.

It's also available per VM license or per socket or per storage capacity and you can mix licenses. You can have some VM licenses and some socket licenses, for example.

We evaluated NetBackup. Commvault has better encryption technology and restore performance.

Keep on training and select a proper implementation company. That is the most important thing.

Most of our clients are only using Commvault. If they go with Commvault they won't use any other product. It can back up everything: servers, databases, storage snapshots — everything. They don't need other software.

We have full functionality as a complete data warehouse, and I've been tasked to leverage the multiple features and licenses that Commvault has, as they apply to our business. We're using every feature and what we are not using, we plan to be using.

We back up multiple platforms in our environment: Windows, Red Hat, Linux, Oracle. We have hypervisors, a large VMware environment. So it's a pretty enterprise-class environment. 

We use it for custom reporting to better manage our backup environment and there is a lot of discovery in that area too. The better question might be how we're not using it right now. We try to leverage every feature that's out there, as a complete data warehouse.

It's a hybrid. It's an on-prem, but we're in Azure now, too.

We're saving storage space. The built-in deduplication features are really good. It's second to none in my experience with it. You really have a better handle on your deduplication database and block changes. Saving storage space is the biggest thing. We see up to 75 percent compression rates, and even higher, so we're saving on data.

Also, with archiving, we've been able to identify data that we were backing up multiple times and archive it instead and save money there. So overall, we've had a lot of space savings with data that's being compressed through the deduplication features of Commvault.

It has also helped us save on costs. There is money available to further use for fees in Commvault, which means the business is happy with what's going on. Those cost savings are from the fact that we don't have to keep increasing our storage the way we were before we were using Commvault. For me, as an engineer, that means I have training opportunities and I can also identify a service for server refresh because there's money available for infrastructure.

We expect that Commvault will also help our admins to minimize the time they spend on backup tasks so they can spend time on other projects. We have identified how it can. Now we're trying to figure out how to implement that. It will involve using workflows and automated processes for scheduling, alerting, and reporting, and even using support resolution through automatic tickets that can be generated.

We haven't yet used Commvault to recover from a disaster, attack, or to recover data for another reason. We just had a report that said we haven't had disaster recovery backup in the past year. Commvault sent us an alert and, within one day, they assembled a team to discuss what we could do to mitigate that risk. Once the team was assembled and we all got together on the phone, I noticed that the report had been inaccurate for a year. It was great that we didn't have a disaster, but I like the fact that Commvault was willing to address that need, at my immediate request, based on their alerting system. They were ready to assist me in a disaster at a moment's notice.

You have total control of your data. It's scary, but it's good once you understand it. There are a lot of unknowns that happen with your data, things that Commvault is doing, and you really need to be aware of them to maximize its overall performance. I like that you have complete hooks into and total control of your data.

The biggest lesson I've learned is that it doesn't break easily. You can get by with some mistakes. It's pretty intuitive. You're not intimidated that you may do something incorrectly and cause some damage. 

The data is well-protected. It doesn't age off until it's copied. That's a big feature right there. When you reach the end of your retention, it does not expire until the secondary copy is completed. That allows you to hold onto data that otherwise would have aged off by retention. I like that feature. It's hard to just delete or lose data using the Commvault platform.

It's tough to understand if you're really maximizing the features of such a large platform without engaging other services that Commvault offers to help you understand and leverage the data warehouse.

It's a little challenging because of the way Commvault communicates and works with third-party solutions. Right now, we're using Commvault to back up Office 365 mailboxes, so we have to work with Microsoft and Azure. There's a lot of handshaking in the background that the customer can be impacted by. For instance, Commvault can say, "Hey, we can back up a thousand mailboxes in two days, providing Microsoft lets us." "Microsoft letting you" means that Microsoft will throttle you at certain times, and there are also certain restrictions Microsoft has with how fast you're doing something, or how many you're doing. We, as a customer, are impacted from that perspective. Although Microsoft welcomes Commvault, there's always the strain of how these two platforms work together. So it's a little challenging when it crosses different platforms into other environments that Commvault doesn't have total control of.

Also, Commvault likes to be ahead of the game when it comes to merging with other platforms, but sometimes it's before they have the solution truly baked in. Office 365 is an example. I feel that my company might be a litmus test for their solution, because we have such a large environment. Some of the promised solutions that we received from Commvault were more like testing solutions. They weren't really validated, meaning they were possibilities. There have been a lot of hot fixes for the solution that we're using right now, more than we expected. It wasn't a simple, turnkey solution when we decided to use them. They could do a little bit more due diligence before they jump into a space to get some of that market share.

One particular issue we found was when we were trying to open up ports for communication. They had listed a couple of ports that we needed and we found out there were a lot more communication ports that they had already assumed we were aware of or already had in place. As we were doing our deployment, we had a lot of network communication issues when we were trying to communicate between resources on-prem and off-prem, due to different ports that were identified as being blocked.

They have to be willing to admit that, "Hey, we don't have this quite worked out yet, but we're working on it." I got to learn Commvault by implementing this Office 365 solution. That's my go-to for examples. There have been a lot of "gotchas" in performance. Commvault says, "Go to this SP, go to that SP," but you're talking about changing your whole service pack level in your environment, and you just can't do that overnight. You can't move as fast as they want you to move, business-wise, to take advantage of new releases and new features. They have to be more realistic that the customer can't keep up with their pace.

In addition, there are two of us who do all the maintenance, but we definitely make use of Commvault resources. They kind of make you dependent on utilizing their resources, which is not such a bad thing. But sometimes you may want to learn to manage your own environment completely, without engaging the vendor as much. Commvault finds a way to keep themselves engaged with what you're doing. You almost have to reach out to them to say, "How does this work? What's the best way to use this? I don't see any information on how to leverage this feature."

The documentation is lacking. You'll find some general stuff, but it's hard to find actual use cases. You also want to know who has tried a solution out, who is it working for, who can you talk to to get some pros and cons? They could do a little bit better with their documentation and not just have basic guidelines that you have to customize to follow.

I've been using Commvault for a year and a half.

We haven't seen any issues with scalability at all. They tend to have a suggestion for us when we come to them with a problem. Right now we're leveraging the IntelliSnap feature. It's been identified as a better way to back up, given some problems we've been having with some particular data that has been hard to capture within a certain time window. 

It's scalable. We haven't had any complaints at all. It rates pretty highly in scalability.

One of the features I'm working on putting in place is access control: How to grant different levels of authorization. We currently have 51 users and six are primary users. Most of those 51 users log in to run reports. Those users have operational roles, administrative roles, and some are in engineering. We also have a couple of database admins who have read-only access to view metrics.

Support is pretty extensive. There are five different levels of support. We're at the top level and we have also experienced two levels below that. They have a great support system. 

They could use additional subject matter experts, but when you do get the right subject matter expert you have a person who is pretty knowledgeable. We haven't needed many escalations, but they do have a good escalation system. 

They've never been stumped. There's always somebody that has the knowledge and expertise to resolve the issue. And that's generally within a matter of days at the most — and sometimes it's only hours. I've never had an outstanding problem for longer than a week without having the right resources in place to resolve the issue.

We have the highest enterprise-level support contract, so we have a team that engages us on chronic issues. We have a team that engages us on new initiatives and we have a team that we work with on the overall Commvault experience. We also have a dedicated technical account manager and we can bounce anything off of him at a moment's notice.

We went from Veritas NetBackup to Commvault. We switched due to upfront licensing and costs. We have more visibility into what we're actually purchasing. It seemed like, overall, the cost of Commvault was cheaper.

The licensing is more visible. It's more "per-diem." They're not forcing you into certain purchases. You can buy in bulk, per se. You can try things out. Commvault offers a lot of good, temporary licenses where you try something out before you commit to buying it. Once you express interest in purchasing, they'll supply a lot more information for you to make a better decision. I like that, versus the way Veritas works.

Commvault is a cost-efficient solution. Just beware that there's a lot you're going to have to understand before you can get to the point where you're utilizing that cost-efficiency.

To convert over to Commvault from NetBackup took us three days, and part of that was standing up the environment. With Commvault, it's easy to bring new data and new platforms in. It's simply a matter of clicking on the agent, installing it, and then going from there. The fact that it's agent-based made it a little bit easier to adapt to and back up multiple platforms and storage devices.

Generally, it takes about five hours to two days to drop an architected solution and start the implementation process. You need time for whatever issues may arise, so it could take three to five days to get Commvault up and running. 

But to get started, it's just a matter of a few minutes. The fact that you can push out and do all your installs from Command Center is a good feature from Commvault. It's easy to get rolling and get started. To really get it fully leveraged takes some time.

Our company is in its fourth year with Commvault and we're just now getting to the tip of the iceberg with leveraging a lot of its features and the licensing that Commvault offers as a data warehouse.

Training-wise, there's a lot of information out there, a lot of free training. There are tutorials and a lot of YouTube videos and virtual classrooms. They encourage you to learn and leverage their data suite without paying for a lot of training.

Prior to using Commvault's Office 365 feature, we were backing up mailboxes at the database level. Commvault allows us to just point, click, and drag-and-drop for backup and restore. That's a really big ROI. Restores are easier to handle at the message and item level. Things are a lot easier to restore. We can restore in multiple ways, including as a PST file. Commvault has a way of looking at our mailbox data and picking out anything that is PST and backing that up in different ways. There are a lot of built-in APIs to make things a little bit easier.

So we do have a good ROI with our overall mailbox protection and restorability.

It's been a while since we used NetBackup, but I think Commvault is easier. It's really point-and-click. There isn't a lot of background stuff going on or command-line stuff. It's all Windows-based, easy drag-and-drop. With NetBackup there was a lot of stuff going on in the back-end, command-line wise, that you couldn't get a good visual of as you were doing it. 

Working with Windows is a little more explanatory, versus working with command-line, when it comes to installations. With command-line, you have this sense that if you do something incorrectly you might really do something bad. That's a big difference that I like with Commvault versus Veritas NetBackup.

Take advantage of any free training and look at other business cases and how they use Commvault, because it's so customizable. There's no right and wrong way. You have to look at your unique business needs to really maximize the platform.

If you're just going to back up and protect your data, I would recommend something outside of Commvault. If you really want to understand your data, audit your data, really manipulate your data, and save money through your data, then Commvault is the place to go.

I like the interface. It requires some assistance with navigation. It's very intimidating when you first jump in as a newbie. You don't know where to start or what's important. The best approach is to learn each one, one at a time. The problem is that you usually end up favoring one particular feature because that's where the fires are at. It's user-friendly, but it takes some time to get used to.

I'm still learning the Command Center. I think a lot of people are hesitant to transfer over to it because it is a little different than the Java console. I just had a tutorial and demonstration on it last week. I like it. It's easier. It's just that the layout is a lot different. It's not as busy as the Java console, and because it's not as busy you don't know what you're not using, or what you have quick access to. I think that may be what intimidates people with the Command Center, that the layout is really a lot different. But kind of like a desktop, once you get it the way you want it, it's a lot easier to work with. I think those initial challenges deter some people, which is why it's been a slow rollout, and Commvault hasn't just said, "We're going to turn this one off and this one on."

I'm in favor of the Command Center. I'm starting to use it a little bit more. It's a good tool, a good upgrade, but it's going to take a little bit of learning.

The fact that a Commvault is a single platform will enable our organization to accelerate growth and drive innovation. This is my second year with this company, and we're now leveraging the experts within Commvault to show us how to use Commvault, so I think it will. But getting to that stage where you have to align those resources can take a company some time. There are some challenges there. But once you embrace it and leverage it the way they want you to use it, instead of using it how you want to use it, it will make the transition a little easier.

This process is helping in identifying lost data and identifying backup performance. You can really drill into backup performance, throughput, network connections, firewalls, and ports. You can really see where a problem is. Fixing their problems is one thing, but you tend to have to upgrade to fix it. Commvault is really good at listening to what the customer says, to their challenges, and then taking those challenges and making solutions down the line. The problem is you have to upgrade your environment to take advantage of those new bug fixes.

What we're looking to do with Commvault in the next six months is to leverage its ability to protect and backup our stuff within the cloud, within Azure. We also want to leverage it more for identifying data analytics. Because we're in the compliance field and the medical field, we really want to understand our data. Is it deduping right? Is it being backed up correctly? How can we archive it? We're confident that it's protected. We're confident we can restore it. Now we want to understand it.

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.

We are a systems integrator and we sell Commvault to our customers.

One of our customers has Oracle Cloud and we needed to create a backup for that. Only two solutions can do that, Commvault and Veritas. Our customer compared Commvault and Veritas by doing a PoC of each. We displayed the features of each one and the customer chose Commvault. 

We have another customer with a different environment. They have virtualization and they have a physical infrastructure and many operating systems and environments. They compared different backup solutions like Commvault, Veeam, and Veritas, and Commvault was the only solution that could cover all the operating systems and the whole virtual and physical environment.

Another customer is in the petroleum sector. They have different sites and they need replication between the sites and they also need to back up their main sites and their remote sites. Commvault is one of the best solutions for this scenario.

The number of errors or problems with Commvault, when dealing with backups, is very minimal compared to other backup solutions. It saves a lot of time for system administrators. An administrator using another backup solution will take one, two, or three hours per day just to check if the backup jobs have run. With Commvault, it takes about 10 to 30 minutes, maximum.

The solution saves on infrastructure and protects data. Compared to other solutions, using Commvault saves our customers around 15 to 20 percent. In addition, it reduces storage space because of the deduplication and compression during backup.

• One of the big features is the 10-mega backup for endpoints. Not many backup solutions support that. 
• Commvault has support for backing up operating systems and servers.
• The solution covers Oracle Cloud, on-prem, virtual, and physical.
• The support for cloud is good.

There is room for improvement in terms of data security.

We use Commvault's technical support at times. I would rate it at 10 out of 10. Their support is perfect.

For some customers we do the implementation on-premise, and others use the cloud version. It's very easy and straightforward. The design, implementation, and documentation is very straightforward, especially the Commvault hybrid product.

The deployment time depends on the customer and it depends on the environment. It takes a minimum of two to three days, and the maximum is 10 days. It depends on the size of the environment.

We have straightforward procedures for the implementation. We have a manual. We have procedures for the automation of installation for HA environments, whether it's for a virtual or physical, and for different operating systems.

Commvault's licensing is very flexible.

Right now we are using on-premise and cloud backups. We run 300 to 400 jobs per day.

Compared to other products out there, we have found that Commvault is best suited for our needs. We can easily restore and deploy the data.

Previously, before the introduction of Commvault, we used other software including Rubrik. But with Commvault we can deploy multiple clients at a time and we can back up multiple clients without any issues. Right now, we are using about 1,000 VMs. Before Commvault we used to back up about 200 servers and 100 VMs. Previously, backups took nine hours. With Commvault it takes minutes.

The solution definitely helps our admins to minimize the time they spend on backup tasks and to spend time on other projects. If we need to run backups for dozens of servers, it can be done in one minute because it can be done in a click. We can select the backups by selecting the client computer groups. We can categorize those groups and, based on that categorization, we can run the backups and we can restore the VMs as well. It can be done in minutes. Running backups twice a week, it saves us about 5 to 6 hours each time.

It is also saving us on infrastructure costs and has helped optimize infrastructure usage, like storage space. By using Commvault we have saved about 3 TBs of space.

We have used it to recover data when there was a problem with our database. It took about four hours to bring the data back. But recently, we introduced HA and it has saved us more time. With HA the data can be brought up in one hour. With other solutions it would take 10 to 24 hours.

We do monitor all the backups using the user interface. It is user-friendly, easy to navigate, and easy to create solutions with it. It is very comfortable. We can do multiple operations at a time.

We use Commvault Command Center for backups and restores and for the creation of new clients. We use it for other functionalities as well. In terms of VMware, I can go directly to the Command Center, enter VMware, and I can search it directly. Command Center is very useful and it can be used for more advanced techniques.

The cloud support is good. The on-premises cloud is working for us as is traditional cloud. All the clouds we're using are working with Commvault. We have Office365 and Azure.

I need documentation for Azure backups. One expectation that I have is regarding PDF documentation. When I was trying to browse the documentation, I could not locate that. The documentation should be in PDF format where it can be downloaded easily.

I have been using Commvault for the past five years.

The stability has been good. We haven't had any issues.

Scaling can be done easily.

I am now looking into an orchestrator. High-availability is another future use case for us.

We do not have any issues with support. Everything is fine. Commvault helps in fixing any issues and they help us to deploy the data whenever we need help. And they provide the security as well.

In the first year we raised many issues, but now it is easier for us to manage. We refer to the documentation.

We used to use Rubrik but we found Commvault to be a better solution. It provided time savings, handled more complexity, and provided more security.

With guidance from their team, and based on the documentation, it was easy to install. The deployment took one-and-a-half hours.

There are updates every quarter and they are getting easier to deploy.

We have about seven staff members on my team, IT analysts, who handle the solution, to account for different shifts and meal breaks, etc. Within the company there are 10 clients using it, mostly within IT.

We are very satisfied. It is a very useful product, daily. 

Commvault is constantly developing new use cases based on customers' requirements. They are developing new features on a regular basis. In version 11, 19 new features were added. For example, in previous versions we did not have the Command Center and whenever backups failed we could not restore the data. Now, there are options for restoring the data. These kinds of advanced techniques are introduced from day to day.

We are mainly using it for backing up our VMware environment, some file servers, and some SQL databases. We also use it for some replication.

Before Commvault we had one product for backup, one for replication, and a few consoles. That was hard to manage for the administrator. With Commvault it's just one product, just one license. It does not require a special, separate license for deduplication or other stuff. It's easy to manage everything now.

Commvault provides us with a single platform to move, manage, and recover our data across on-premises locations. We usually have daily, incremental backups and a full backup weekly. That leads to reduced storage space for our Commvault storage. It's saving us about 30 percent.

The fact that the solution is a single platform has enabled our company to accelerate growth. We have a database and there are some major changes that happen to it at the end of month, or sometimes the developers have done something to change it in a whole different way. Before they apply those changes, we take a backup with Commvault so if something has gone wrong with the update, we can always revert it back.

Also, because it has alerts enabled, the solution helps our admins to minimize the time they spend on backup tasks so they can spend time on other projects. We don't monitor the backup system all the time. We only look at it when we get email alerts. If something has failed, then we'll look at what the error is and what's happening. There are daily backup reports configured so that at 10:00 am, every day, I get a backup report. It says what has been backed up and what has not.

In addition, we have had a few crashes of our VM environment and we have had to restore some VMs, as well as some files that have been deleted by users off our file server. We had another solution before, but that was before I started with the company. People say it was pretty crappy and that sometimes, when they were doing recovery, it took about eight to 10 hours for a VM. But with Commvault, the last time I did a recovery of a 500 GB hard disk with a VM, it took about one-and-a-half hours. That is good.

Finally, Commvault has helped by telling me there are outdated tools in the VM environment.

The most important feature is that everything can be controlled using a single console. That is the best feature of Commvault.

The user interface is a bit tough, to be honest, but once you get the hang of it, it's okay. In the beginning it was tough, but now I know what I'm doing. We had free training but after that, just to learn the interface took me four to six months. There are still things to learn because with every service pack there are changes. Service Pack 18 was recently released and there are some features that I haven't even seen yet.

I would like them not to push Command Center. It is good, but I would like them to enable all the features for the Java console. Some things are not in the Java console, like Office 365 agents. In fact, they are there, but one of the engineers had to show me how to configure it. It's not done the same as in the Command Center.

I have been using Commvault since 2018.

It's stable. 

Sometimes the Java console might not respond. It might happen one out of 20 times that the Java console might crash. And then we have to use Task Manager to end it and reopen it. Other than that, the server has never crashed nor has the database ever crashed.

We have actually moved into 365 recently. We had to buy some licenses but they agreed to give us some trial licenses for testing, but it is based on the user base. Commvault is supporting everything that we are doing.

The technical support in the India region is a bit disappointing, but after 6:00 pm it is switched to the U.S and European teams, and they are much better in supporting and understanding the issues and fixing them. Sometimes the Indian team is also good, but we don't usually raise a ticket until after 6:00 pm. If it's a small issue that doesn't cause any harm to the production environment, we will go to the Indian team and some of them are good enough to help us.

Our company switched to Commvault because it had some issues with recovering data and the recovery time was high. Also, the local support team for our old product was not available when we needed them. That's why they were looking for something new and they found Commvault.

The setup was straightforward. We didn't have many complications. When we had to install the agents on the servers, there were some issues with authentication with the SQL database, but that was from the database side. That was sorted and there was nothing much more than the usual administrative stuff.

The initial deployment took about three weeks because we had some complications with database servers. Some of them had to study the user account permissions. After that was sorted out, it was fine.

Our strategy was to install it on critical servers. After the vendor installed the physical servers for Commvault, we had to download about nine to 10 GB of their setup files. After that, they installed and there were some prerequisites to complete such as .NET. After that, it was pretty easy. Once we installed we had some local support. We also had to plan and provide retention periods.

We had support from the local distributor. They were very friendly and they were cooperative and concerned with our requirements. They addressed them properly. Overall it was a good experience. 

And they provided us with the training after the deployment. We played with our environment for two to three months after the deployment, and then they gave us the training. That approach was better because we had an idea about what we were learning. We had questions when we went to the training so it was very good.

Commvault licensing is a perpetual license so only the support is being renewed yearly.

I don't like the solution's Command Center. I don't know why they have pushed it. The old Java console is much better. Maybe it's because I was used to it. One good thing about the Command Center is that it has reduced the steps we have to take. If we had to do 10 steps on the Java console, it's been reduced to four or five steps in Command Center. But I'm confused about whether I'm doing things right because there are some steps missing. For a newcomer, Command Center would be good. But for me, I still prefer the Java console.

Currently, there is only me, as a system administrator, and another guy on the database team who use Commvault. That's all. We don't have many administrators.

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.

We use it in the most traditional way: for backup and restore. We don't use it for all the other things that are also possible with it because we are quite a big company. We have all the specific tools we need for specific purposes.

We tested Commvault in the past for archiving, but in those days it was not really stable yet. So we selected other solutions for that.

We use Commvault on everything. We are using it in our own data centers but also in the cloud. We use Azure for most things, but we also are working on testing some things on AWS.

The benefits to our company are the performance and scalability and the willingness of Commvault to connect to talk with us about any requests we have for changing the product, and to do understand what we're looking for. If possible they also implement these things in quite a short amount of time. If a new feature is needed, or it should be doing A instead of B, they're always willing to listen to requests and build them. That's great.

The fact that the solution is a single platform has enabled our company to accelerate growth and drive innovation. We're using it in a traditional way but our resources and services are moving to the cloud. It helps that the way the product works, what we are used to doing in the traditional way on-prem, can be done the same way in the cloud. That makes it easier overall and makes the transition easier.

There are ways the solution helps our admins to minimize the time they spend on backup tasks, but in some ways, the solution doesn't. But that's more related to our way of working and not related to Commvault. Using it saves us about 40 hours in a month, thanks to its automation features.

In terms of saving on infrastructure costs, in our environment that's not measurable because we have a dedicated platform and dedicated infrastructure for it. But we see the benefits of the deduplication. It's saving petabytes in our environment.

The backup and restore activities are valuable and being able to use it in a hybrid space. You can easily back up on-prem and restore to the cloud and vice-versa. The scalability is also good.

The solution's interface is easy to use. For manageability, it doesn't matter where the resource is coming from or going to. That's the great power of the Control Panel: It's easy to use and does not matter if you manage on-prem or cloud resources.

Commvault works quite well as it is. But we are an MSP, so for us it's fairly hard to customize it for branding it.

There is also room for improvement in the multi-tenancy and security. That's been a hard thing for us and for Commvault as a vendor. Sometimes it's hard to implement new features in multi-tenancy environments. The new features are great, and it's good that they are there, but they are not always usable in an MSP environment.

The solution's breadth and depth of cloud support are good but could be better. Some cloud features that are common-sense, especially on AWS, are not completely integrated yet in the product. They are a work-in-progress. Overall, cloud is moving and innovating also very fast. That also makes it very hard for Commvault to comply with all the new features. Sometimes a cloud provider like Microsoft changes something and a feature is broken in Commvault.

We have been working with Commvault as a backup product for about 12 years now. As an MSP, it's very hard to switch from vendor to vendor. But the solution also works great. We have no real reason to switch to another product at this moment. We are always looking at the competitors, but not all the competitors can comply with all the things that we need.

It is very stable. We have some little issues with it, but when we have issues they're always related to the application we want to back up, not to the product itself. We ask a lot of the product; we use it in a fairly hard way on several things. Sometimes we hit the boundaries of the product and we encounter issues. But in day-to-day business, we don't see any real issues related to the infrastructure or the load we can give it.

It scales very well. If we need more capacity or more power for performance, then we add additional nodes without needing to do a complete redesign of the product or the environment. We can easily add extra power.

We have about 10,000 clients running with approximately 2 petabytes of data being backed up. That will double in the upcoming year to two years. We also have about 1,000 end-users of the product and most of them are doing restore activities.

Their technical support is very good.

But a hard thing for them is understanding how to work with an MSP. They assume, sometimes, that as an MSP, we have access to everything. But that's not the truth and it's not possible. That makes troubleshooting hard for us and for them as well. But they are quite fast in responding and try to help as quickly as possible. Still, most of the cases that we have with customer support need to be escalated directly to development.

We previously used an IBM solution. The main reasons we switched to Commvault were cost and complexity.

The setup of Commvault was complex but that's related to our environment. As an MSP we have very high security guidelines, so that made it hard. But that's not related to Commvault, it's related to our security environment.

Our deployment took almost a year. We had to make sure our design was good before we did anything. Most time of the implementation time was in the design phase. The actual building-up of the solution was quite fast. We were done in a month, starting from scratch.

For deployment and maintenance we need four to five people who are backup system admins.

We did it by ourselves.

We have seen ROI in several respects, but not as fast as we want.

We look at everything on the market. Every year to two years we do a new evaluation of the new techniques and products. We are always comparing it with Veeam, for example. We have Veeam running in several places. We test the two solutions and compare the results with each other.

Out-of-the-box, the manageability is one of the big differences. For end-users, sometimes Commvault is too complex and, while it's getting better and better with the latest versions, it is still not there. The most important thing is what my end-users say to me about using Veeam. It's very straightforward, easy-to-use, and does what it needs to do. Veeam and other competitors are point solutions. They are very good in specific situations and specific environments.

On the other hand, Commvault is a product that can manage a lot of things, and most competitors don't have the scalability and the large support-matrix for as many products, versions, and applications. Commvault allows us to use one product for almost everything. It's better than the competitors. We want to have everything in a single console, if possible, and that's what Commvault does for us.

The biggest lesson I have learned from using Commvault is to take your time. Especially in complex environments, the design stage takes a lot of time, but you need to do it well. Otherwise, you will have trouble in your implementation. We learned that the hard way. We wanted it built fast but, when the design was ready, we needed to rebuild several times.