The primary use case is as a backup and recovery solution. We have two data centers and we have a Commvault server for replication in both. We back up all our infrastructure with this solution, from Active Directory to SQL, web servers, file servers, databases, et cetera.

Commvault helps to ensure broad coverage with the discovery of unprotected workloads. The Discovery feature lists all the resources that we have, all the virtual servers and all the physical servers. You can also automatically deploy agents or set up schedules. At first, we did some manual tuning to customize it before deployment. Now, the virtual infrastructure administrator just has to add the VM tag on the virtual machine and that machine will automatically be backed up in the next schedule. It's a good automation feature.

It also helps by minimizing the time our admins spend on backup tasks so that they can spend time on other projects. Before Commvault, we had two backup administrators who were using a backup and restore application to restore every test that we had to do. It was a full-time job just monitoring the backups and doing the restores. With our new solution from Commvault, we have successfully implemented web-based backup and restore management for our different teams, including our file server, database, and Exchange teams. We split operations among those teams and each one has access to the backup Web Console. This console from Commvault is very useful for segmenting the restore options. That way, the database backup administrator only has access to the database servers and can only do backups and restores of databases and does not have access to Active Directory or file servers. The web-based backup and restore is a really great option.

Whereas before, we had one full-time engineer doing backups and restores, now that engineer is only working on it for two to four hours per week. Across our four teams, it's saving us about 10 to 12 hours a week.

The solution has helped to reduce storage costs as well. Commvault has an option to move data from primary storage. When you do a backup, it scans all the files from the file server and you can set a policy to remove all files that are more than, say, three years old from the primary storage. And on the primary storage, there is only a link that connects to the backup source. When a user needs a file on secondary storage, there is no problem because it only reads the file. When the user opens that old file, it's automatically restored and the user can access it. For our IT team, it has saved us between 5 and 10 percent of storage. It depends on how widely you implement the solution and the policies you set. You could save 50 percent if you have a broader policy.

We have also saved on infrastructure costs because Commvault takes less time to do the backup jobs, due to the deduplication. Also, the background tasks that are used to copy the backup jobs to tape are deduplicated. The full backup of our infrastructure can now be done in a couple of hours during the night. Before, some backup tasks would take more than a day, on the weekend. There has been a reduction of 80 or 90 percent in the backup window.

Commvault's most valuable features are its

• deduplication
• encryption
• support for many OSs
• support for different infrastructures.

We have VMware, Hyper-V, Oracle, and Microsoft SQL. We have a lot of different systems, and all of them are supported under one licensing agreement. That's one of the benefits.

We use two user interfaces on a regular basis. One is the Web Console, which is simple and has all the necessary functionality. You can add servers, back up servers, and restore. We also have a replication solution implemented and we use the Web Console for that as well. But for the initial configuration and for some deeper configurations, we also use the Commvault application. It's big and has all the fine-tuning options.

The solution's Command Center is very straightforward. It has an intuitive user interface with graphs, tables, alerts, as well as many options for alerting and messaging. Of course, you have to get used to the environment, but it's easy to use.

It is also important that Commvault provides a single platform to move, manage, and recover data across on-premises locations. That's because we have different storage and virtualization platforms. We have no problem if the file resides, say, on NetApp storage and we have to restore data to a workstation or some kind of Windows Server. Also, when we did some migrations from our old Hyper-V cluster to the new VMware cluster, those integrations between different infrastructures were successfully accomplished with the Commvault solution. We have no issues with different types of resources we need to back up.

In addition, the recovery options are pretty straightforward. For example, if you choose a virtual machine, you can restore the full virtual machine, you can restore the virtual machine on a different platform, you can restore just a virtual disk, or you can restore just a file within the virtual machine. You have all the options. In the web-based user interface, you can also restore using download options. You can browse through the files or virtual machines and download the file from the backup. They have a great range of restore options.

We had some small issues with the reporting, but that was just a matter of fine-tuning the kinds of messages we receive by email. It was a little overwhelming in the initial configuration. So we reviewed our configuration with our partner and customized the reports so that we only get the important reports. I haven't seen any big issues or things that the solution is missing.

We implemented Commvault at the start of 2021, so we have been using it for almost a year now.

We had one issue. The Commvault server is an Active-Passive cluster and the Active node had some hiccups. It wasn't something serious, but the Commvault server was unable to connect to one of the agents. I believe our partner discovered it because they also receive messages from our Commvault solution. They just informed us that the Commvault server had to be restarted. We did so during working hours because backups are done at night, and there were no issues. It was a standard procedure and we have had no other big issues.

At the start of the Commvault project, we put together a list of all the resources that we have. They counted our resources and gave us the exact number of clients we needed to buy to cover all of our infrastructure and we had no issue there. Of course, we also have some plans for the growth of our infrastructure. If we have any big upgrades, we will also upgrade the Commvault infrastructure.

We have a lot of Commvault's features implemented. We're also in the process of testing the backup of endpoints, such as laptops and devices from end-users. There are just a few features from Commvault that we don't use.

We use technical support through our partner because our partner has a lot of inside knowledge. For the majority of issues our partner gives us the solution, but they have had to report some small issues to Commvault support. They spoke directly with Commvault support and the solution was available in a few days. It was a very good troubleshooting experience.

We used NetWorker and Veeam. The NetWorker solution was the older solution and, in some very old clusters, we also used TSM (Tivoli Storage Manager) from IBM. The TSM solution was no longer supported and the Dell EMC NetWorker solution, which we used for our physical servers, was difficult to maintain. Veeam was a good solution for our VMware infrastructure, but we needed a solution with support for a wider variety of infrastructure types. One of our major goals was to eliminate our multiple backup solutions by going with Commvault.

If we had to do the initial setup ourselves, it would be complex, of course, because we have a big infrastructure with different types of targets. But our partners helped and they managed to cover all the tests that we implemented at the start of the project. So, overall, the setup went really well. It took just a few days, maybe a week, to add our agents. After the initial configuration, it was really easy to roll out the solution to our entire infrastructure.

Our partners, called Our Space Appliances, are system integrators in backup and storage solutions. They know our infrastructure.

We had a process for choosing a vendor. We called a number of vendors and had proposals from the Veeam, NetWorker, Cohesity, and Commvault.

The big pro for Commvault was that it was a single solution for our entire infrastructure. The licensing model was also an advantage and the experience of the partner was also a big plus. Some of the other solutions we evaluated did not make it to the second round because they did not support all the infrastructure we have in our environment. In the last round, the battle came down to pricing, as well as some small features, and Commvault was the best in all the criteria.

Commvault is a pretty comprehensive but, maybe, complex solution when you first start with it. But that's why it is a perfect match for complex infrastructure, as it supports all types of infrastructure. Commvault is not appropriate for small businesses with just one type of virtual environment. There are different vendors that may be better for that use case. But when looking at enterprise backup and recovery options, Commvault is the easiest to use, and it has the widest range of features.

We are currently moving to Exchange Online. We have between 1,500 and 2,000 users. We have already deployed Teams on the cloud, and now we are migrating user mailboxes to cloud. Our next step, in the following month, will be a backup of Microsoft cloud solutions through Commvault.

In terms of the coverage of Commvault, we have a big Oracle Database and the Oracle administrators are a separate team. They do their own backups using RMAN. They then move the backup to the separate Sun ZFS storage. We also tried that backup with Commvault, using the Commvault agent to run RMAN. The test went well, the backup was good, but the database team was used to their old solution. So we agreed to implement a backup of the ZFS file server.

Ours is an all-on-prem solution so we don't have any other networks being backed up. We do have a DMZ with different VLANs and so there were some problems. We had to install an agent on the DMZ zone, an agent that has access to resources in the demilitarized network. But it's a no-brainer. We just have to open a specific port so that the backup agent can communicate with the CommCell server, and the resources are backed up successfully.

In addition, to protect against ransomware we use Commvault's alert options because Commvault can predict big changes in the network with its AI solution. This is the first line of defense. The second line of defense is that we are now in the process of implementing secondary, offline storage to ensure an air gap between the primary backup, the replicated backup, and the offline backup storage. In case of a ransomware attack we will have off-site backup storage.