Commvault Cloud Reviews

How we implement this solution in a government institution is a little tricky; it's more closed. One of our most important use cases is how we protect and back up documents and files from users outside of our building because we must follow security standards. We use only HTTPS protocols, a special proxy server, etc.

The solution helps our admins minimize the time they spend on backup tasks and to spend that time on other projects. It's not easy to calculate in minutes, but we have found that it's approximately 80 percent faster to do a backup and restore if we need to.

Using Commvault, we have saved on infrastructure costs. Before, we had a few other solutions for backup. Each of them asked for a data store for storage space. Now, with one solution, we have reduced the amount of hard disk storage in our platform. And with Commvault, the file compression is much more efficient than with other solutions. We currently have 50 to 60 TB in our data set, for the entire ministry with 350 users. Before Commvault, we used much more. I would estimate we are saving 60 to 70 percent of the storage we used to need.

I have also cut more than 50 percent of my daily tasks as a result of Commvault. I don't need to worry too much about backups because I know the system will do everything by itself. Every morning I get reports from Commvault and, if there is a problem, I will get a notification in my email. So it allows me to work on other things.

For now, we are very lucky that we have only needed the solution to restore some clients' data. Only once in the three full years that we have been using it did we need to restore our main mail server. There was a problem with the Windows update where the machine would not patch the Windows update and everything crashed. With two clicks we were able to restore the machine live, so we did not have to reinstall the machine. And a few times, Commvault has enabled us to restore a user's data set.

The most valuable feature is sharing data sets like they're in a private cloud. We call it our "private cloud" because we can share anything that is inside our backup set with our colleagues or with other people, and yet, everything is still in Belgrade, in Serbia. It's not somewhere else on cloud servers. Everything is in our environment. For example, our inspectors exchange data between themselves, so they put everything in one folder and anyone with rights can see it. That is a feature that we use very often.

Another important feature is the protection against ransomware. If an employee gets a virus on their computer we will not worry about it, or if their computer is hit by ransomware, their data will be protected in the backup. That feature is very nice.

In addition, there is a new feature for GDPR regulations and protecting personal data. We don't use it fully because it's new and we are still experimenting and trying to make things easier for all of us. But we could say, "Okay, this database has some personal data in it so please do extra tracking, ask for more credentials, etc., to be sure that nobody can reach that info unless they're supposed to. That is a very nice feature.

The Commvault Command Center is good. Even when I'm not in the office, I can track and see that everything is okay with my system. The Commvault team uses it for protecting our make system and to make it better. They see the health of the system, what features we use often, or not, to help with right-sizing the software.

Overall, we like the fact that it's a single platform for everything. We have one console that has everything that we need. We can add or remove users, retire a user, add a new server, or even start a backup by itself. We don't need to go to the client's site to fix something. We can do everything from the console, wherever we are. If we need to restore a client's computer, we don't need to go there. It can be done from a local PC. We have 22 locations in Serbia, so it's not possible to visit all of them in one day. We can do everything from our console. The only requirement is that that computer is on, and we can do everything from one place. And with one click we can start a backup procedure for any server we want.

As a government office, we think about protecting personal data. Serbia is part of an open government partnership, which is a global project. Commvault should think about protecting open data, especially if there is personal data involved. Perhaps they could divide the data and say, "In this database is personal data and you cannot use it in an open data format."

And they can always improve the interface design to make it easier. Sometimes, you need to click two or three times to do something. They should look at what tabs are used most and make them more accessible, to cut the time it takes to get to that information.

I have been using Commvault since 2015.

We started by testing the solution with a local company, one of Commvault's local partners, here in Serbia. We first wanted to test how it would really work in our environment. After that, we procured it at the beginning of 2016. So in the summer 2016, we officially used it with our license. Before that it was just testing, tendering, procurement, etc.

Every type of software, even Microsoft, has some problems. It's not possible to make something without some patches or little bugs. But until now, over the years we have been using it, we haven't had any big problem where we said, "Oh, this is not working." We have had some problems and opened tickets and support has helped us very fast. 

We can say we are generally happy with Commvault. It's not possible to expect to buy something and never have a problem with it. That's especially true when you add something new; it depends on your hardware environment. It also depends on your network and your users' backup behavior. It's not possible that something will be perfect.

For our use, it scales well. They have many solutions, both on-premise and now, with this Metallic software as a service, you can use it on the cloud. So it's scalable. You can choose what you need and deploy it. 

As a government institution, we are not allowed to use public clouds. Everything must be in our data center. We can mix in a hybrid solution of private clouds and on-premise, but for now, we only use on-premise.

If we need something, if we have any problems, we can open a ticket and their support will help us, and they do very well. We must send an email to our local partner describing our problem and that we need Commvault support. They send it on our behalf to Commvault. Then Commvault opens a ticket. It's not possible for us to open a ticket directly. We need to go through our local partner. That path works for us.

We're happy with the support we receive from our partner. If it's something smaller, they try to fix it by themselves. But we usually open a ticket, in case something has happened or just to have the possibility of tracking all changes.

Commvault also has a very good portal where users, before opening a ticket, can try to find solutions. If others have had a similar problem, we may learn how to solve it.

Before Commvault we had other brands. We use Acronis Backup among others. We wanted to have just one solution for all our needs: for servers, for SQL Server, for laptops, etc. Our partner suggested we try Commvault and we saw that it was a good solution. It really helped us in dealing with backups, so we chose to buy it. Especially when you have public procurement, you cannot say I want to buy this particular solution. So it is tricky to do public procurement and get what you really need.

Our requirements included having one console for all systems. Before, we had Acronis for servers and we had Backup Exec for clients and we had Windows Backup for Windows servers, etc. So the main requirement was to have one place, one console, from which to manage everything: laptops, PCs, servers, databases, and everything. That was the main reason we wanted Commvault.

The second requirement was because we have employees who are outside of Belgrade; they are not sitting in our building. We needed the possibility of backing up their computers, computers that are not in our primary network. With Commvault we managed that very easily.

We now back up more than 70 PCs from our inspectors all around Serbia. With one solution we back up all of them. That was most important because people lose their computers and some computers crash. It was very necessary to have the possibility of protecting their data with a backup solution.

There were other factors as well, like having a partner in Serbia. Also, if we wanted to add new functionality we didn't want to have to buy other software or to experiment. We wanted to be able to just buy a license for the additional things that we needed.

For me, the initial setup was not so complicated, because I'm an IT guy. I understand what is needed. But if I look at it from the point of view of someone else, it's still not too complicated. The documentation is very well written and tells you what you need to do next. Of course, you need to know some rules about backups, but the installation is usually done by guys and girls who are in that field. A regular user will likely never install Commvault by him or herself. And even though I am not a technician and I am not a backup engineer, the setup was okay for me. I was able to understand what the system was asking and what I needed to do.

In terms of how long the deployment took, we tested it just to see if we could back up a part of our database. We have two networks. One is the primary, official, and public network, and the other has secret information. So we tested backing up both of them. Including testing, the deployment took around two months from zero to putting everything on. That also included deploying it on our system, connecting it with our storage, our databases, and installing it on some clients to see how the clients work.

Our implementation strategy for Commvault was very simple: Do it fast and secure all the information we need. We needed to back up everything we had. We just wanted to do it correctly, by the book, and to protect everything.

We used a local Commvault partner, Fractal Dimension, to deploy everything. They also provided some courses on administrating it in our institution. They did everything from the beginning to the end.

I have known Fractal Dimension for a very long time. We have worked with them on other projects here in the ministry. When we were looking for a backup solution they said, "Let's try Commvault."

I hope we have seen a return on our investment but it's not easy to measure in money, because we haven't had any big problems or lost any very important data. But generally, the ROI comes from not having to worry about these things. That may be the best return on our investment. I know that if there is a problem, I'll be able to restore without problems.

It's not cheap but it's not too expensive. We have a yearly contract for support from Commvault. Of course, even for that, we need to go through a public procurement process, because there are a few Commvault partners in our country. Our yearly cost is around €20,000.

There are no additional costs to the standard licensing fees. If we want to add a new feature or to buy new licenses for new clients, of course we have to pay more. The cost is based on the number of users and the amount of data. They sell it per terabyte.

We have a contract with Commvault through our local partner so that every year we enter into a new contract for the coming year for updating, upgrading, and support. That enables us to download and deploy every new version, service pack, and hotfix. The latest one is service pack 18 so that is what we are using. That was part of our requirements for a solution: to have the possibility of continuing with it, rather than buy it once and then stop updating. Our goal was to always have the newest version and to have support for tickets.

Whether the licensing model is cost-efficient depends. Government has needs that are different from the private sector. Banks and financial institutions, for example, have other needs. It depends on how they work with backups. Do they need a backup restored in five minutes or in five hours? For my system, if a computer doesn't work one day, it's not a big deal. But in a bank, if you cannot get your money in five minutes you get mad. But overall, the pricing is okay. For what you get, it's a good price compared to the market.

We only tested Commvault because our partner explained to us that it would probably do everything we needed. We spoke with them, had three or four meetings to explain what we really need and what our system looks like. After some weeks they came to us and said, "Okay, we think we have a solution for you." We only tested that solution because we didn't have much time to test others. It was almost the end of 2015 and we needed to budget for the next year.

The biggest lesson I have learned from using Commvault is that if I set everything right, everything by book, I can solve any kind of problem that I may potentially get. I know some people using other backup solutions didn't set everything up very well or by the book. But that is why companies make documentation and say that if follow the book you will not have problems. If you try to escape that and to take some shortcuts, if problems come up, nobody will be able to help you. A good lesson is to just follow the rules, according to the vendor.

We not only use this solution to restore data, but when clients get a new computer we don't need to spend time transferring their data from the old computer to the new computer, because that data is already part of the backup set. First, we decide what we will back up.  We separate their private data from official work documents and we back up only what they need for work. So when they get a new computer, we don't transfer data. If they want to transfer their private data, they do that themselves. We just install the Commvault agent on the new computer and say, "Okay, this is that person's new computer. Copy their backup set to their computer. In a few minutes, depending on how much data they have, their data set will be in their computer. That is another good way for using the backup set in our system. Doing it this way, we save almost a whole day it would take to transfer the old data.

The time it takes to restore data, comparing Commvault and other solutions, is approximately the same. What does make it faster, in general, is that we don't need to install another application. We just install the agent and each user can log in to their account and can choose what they want to restore. If they don't want to restore everything, they can just select what folders they want to have on that computer. In that way, it's faster. Because the solution is user-friendly and we have created a user manual for our users with print-screen illustrations, even people who are not so familiar with IT can follow the manual. It's easy. We don't need to go there physically or explain on the phone to the person how to do it. They have the manual and they just click this and that and everything they want is restored as it was.

In our organization there are only two IT guys, me and another colleague, who work with Commvault daily, to see if that it's okay. Other people, once in a while, need to restore a file, if they deleted it by mistake. 

Clients only need to check things if they get an email notification that their computer didn't back up in a given period of time. We put that in place in case there is some problem. After 10 days they will get email notification that in the last 10 days their computer didn't back up and to check if their computer is turned on. When people go on vacation for more than 10 days, they will get that notification but they know it's because they are away that their computer is off. But if they are at work and get that notification, they call us so that we can track what's happened. But in general, nobody else uses it daily.

In terms of maintenance of the solution, I learned on my own what I need to know, for now. If I have a question, I call our local partner, or I will read through the Commvault forum to see if anybody has said something about the issue, to know in which direction I should look.

We use it on-premise because we are a government institution. In Serbia, by law, we cannot use public cloud for government institutions. We have servers and storage in our data center. For this year, we plan to expand it to create a disaster recovery location in another public institution. We will make a disaster location on their site and they will make their disaster location in our data center. We will buy Commvault HyperScale and, with our local partner, we will set it up so that in case our data center is offline, we will have another location where our data is available.

There is no reason for me to rate them other than a 10 out of 10. When you have support online, you really see what they do. They are fast. If you open a support ticket, they will call you within 24 hours to check and to organize a session. You share your screen and work together to solve the problem. They have good partners and they have good marketing. So Commvault is a 10, without any doubt.

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.

Positive

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.

We provide backup services to our customers and we implement Commvault for most of our backups. This includes cloud with VMware, cloud with IBM, cloud with Azure, SAP applications like HANA or traditional SAP, for databases including Oracle and DB2, and across several operating systems including AIX, Solaris, Windows, and Linux.

We have a separate, private backup network. It has its own appliances from different vendors and the information on it is not visible to our main network. This is to help protect against ransomware and other threats.

Commvault provides us with a single platform to move, manage, and recover data across our on-premises and cloud locations, which is something that is very important for us. We have data centers in Mexico, Panama, Guatemala, and the Dominican Republic, and we need to administer all of the environments from a single location in Mexico.

The administrators connect to all of the environments on-premises. We have two flavors; the multitenant environment and the dedicated environment. We manage all of these from Mexico.

Commvault is very good in terms of coverage for applications and databases. This is important because we don't only administrate backups. We have managed services that include the database, application, operating system, and storage. We talk with the administrators for the database and operating system to create a policy that ensures all of the data that we need to recover the environment is complete.

The recovery process is consistent across platforms and this is important to us because clients give us the information, and we need to back it up and to ensure that we can recover it if they have a problem.

The recovery options are good because we offer our clients a complete recovery of their information, as well as an option for partial recovery, based on their needs. For example, we can offer the recovery of a single table in a database, depending on what the scenario is.

The most valuable feature is the compatibility with our entire environment.

The embedded deduplication engine is really good because we use a Near Line SAS disk as a repository for our backups, and we don't need to pay for another appliance such as a Data Domain or Quantum so that we can have hardware-based deduplication.

One of the benefits of using Commvault over the years has been that all of our administrators have the ability to perform admin functions. They haven't had any complaints about the interface.

Commvault has support for multiple storage platforms, which is helpful for us. We use block storage for some backups, and we use appliances that have duplication capabilities for other backups. The method in which Commvault fits in depends on how much money the client spends. For example, if they have a higher budget then we use PCI-compliant appliances, or snapshots in the backups to ensure that we don't have ransomware. Other clients pay only for the amount of storage that they use. In some cases, we use replication at the host level, whereas in other cases, it is at the hardware level. The console that we have with Commvault can manage all of the environments and hardware that we have.

I would like to have a manager-level dashboard to review the backups. This is not from an administrative perspective where you can see the details of the execution. Rather, it would only show the percentage of completeness for each one.

I have been working with Commvault for more than eight years.

We have not had any problems with stability. 

We have more than 10 implementations in all of our data centers.

Using Commvault helps to minimize the amount of time that we spend on backups. I am not exactly sure how long it would take otherwise, but we back up approximately four petabytes of information each day.

Scaling is not a problem for us. If we need to, we can install more servers and install a new console.

We use Commvault support on a daily basis. People from the database teams need help restoring data, so they contact Commault for assistance.

I would rate their support a nine out of ten.

Prior to Commvault, we used Veritas NetBackup for five years.

A lot of our environment is currently backed up using Commvault but we are planning to use Veeam and Commvault together. Veeam is priced better than Commvault and right now, we use Veeam to back up our virtual machines. As we split more of the information between the two different applications, we may use Veeam for cloud environments, and for traditional environments, Commvault.

There are some applications like SAP HANA that are not compatible with the Veeam software. In cases like this, we use Commvault.

This product is very easy to set up. The reason is that we do everything. We implement, we operate, and we migrate. One of the reasons that we continue with Commvault is that we have spent a lot of time training people. This means that the people in the company can do everything without the need for third-party persons.

It takes between two and three hours to install a new console.

Over the years that we have had this same software, people on the admin team have become certified by Commvault. This ensures that they are doing things properly and doing them well.

We charge our customers on a per-gigabyte basis.

Using Commvault has helped us to reduce storage costs because, in some cases, we changed to block storage. Using block storage and software-based deduplication is cheaper than the appliances that have deduplication embedded in them. In some cases, we have reduced our hardware cost by 50%, whereas in other cases, it has been reduced by more than 75%. It depends on the technology that we compare. For example, the Data Domain appliance is perhaps four times the cost of the Near Line SAS disk in traditional block storage.

Reducing the hardware that we have in the data center, also reduces our costs in terms of energy and space. I do not have an estimate as to how much we save.

Commvault is more expensive than Veeam, which is the reason that we are changing to Veeam for cloud environments.

We had been running Veritas NetBackup and did an RFP to change the backup software. We tested Veritas, Commvault, TSM from IBM, and Dell NetWorker. The finalists were Veritas and Commvault. We found that there were more advantages to using Commvault. For example, it has deduplication embedded into the software and if we wanted this with Veritas, we needed to pay an additional fee. This is why we changed and we have maintained it for several years.

In comparing solutions, I think that generally, today, all software solutions are the same. We have the same compatibility using Veritas, TSM, NetWorker, and Commvault. The main reason for us to maintain Commvault is the expertise that we have with the tool. All of them have deduplication capabilities and can use different repositories, so I don't have a problem with the other brands.

Commvault has the capability to discover unprotected workloads, although we don't use this because we only work with policies. Our clients tell us the policy that they want to apply to their environment, and we don't analyze their environment beyond the scope that they specify.

I would rate this solution a nine out of ten.

We use it to back up everything in Office 365: our Exchange mailboxes, SharePoint, OneDrive for Business, and Microsoft Teams. And we use it for Azure Active Directory. The thing we use it the most for is recovering email messages or mailboxes.

We moved our email to Office 365 and, when we did that, we were using an on-premises Commvault solution but that was not an efficient way to back up the O365 mailboxes. Metallic has definitely improved our ability to back up and restore email, as well as the other online systems.

Also, we spend very little time with the Metallic solution because it just runs, so it has reduced the amount of manual work required to manage our backup operations. With our former solution, I was spending two hours a week on that, so it's saving me that much time. The other benefit is that I now have three or four other people on my team who can do the backups and the restores, as necessary. With the on-premises solution it was very complicated and I was the only one who could do it. Not only have we reduced the time from two hours a week to almost zero, but we now have multiple people with the ability to use the tool.

And when it comes to infrastructure costs, it's saving us about $25,000 a year.

It is very easy to use and that's been good for my team because I can have multiple people use the solution. It's very intuitive.

In addition, the granularity of the Office 365 Backup & Recovery feature is very good. We've used all of it, recovering data from each of the four systems that we back up with it, and it works very well.

It has also been very reliable.

The speed of the Office 365 Backup & Recovery feature is adequate. Microsoft controls the amount of bandwidth that people have when they're using Azure and the O365 environment. It's not really a Metallic issue, it's more of a Microsoft limitation. If they could work out something with Microsoft to improve the speed, that would help. But, generally speaking, it's been fine. I don't know of anything else that I'd want to see improved.

I've been using Commvault for about 18 months.

We're very satisfied with the stability.

The scalability is excellent. Any plans to increase our usage of it in the future will come naturally with time.

I've contacted their technical support a couple of times and they were very good.

We switched to Metallic from Commvault's enterprise backup because that solution is not in the cloud. Given that it was on-premises, trying to back up the resources in the cloud was inefficient. Metallic is in the cloud and it can talk directly to those other cloud resources. It was designed better for what we need to do.

We used Commvault Metallic's implementation services. There was an engineer on the phone with us and he walked us through the steps and everything worked as it should. It was very simple. The configuration is all done through a web browser; just point and click. The deployment took about an hour. All I had to do was get it up and running and show my team how to use it.

Our experience with the Commvault engineer was excellent.

There are four of us who use the solution, including me. The others are all system administrators. We haven't had to designate anyone for maintenance.

It's hard to measure the ROI of a backup solution. It's like car insurance. You have to have it but it only pays for itself if you have a catastrophe.

The solution is licensed based on the number of objects that we're going to back up, and that's a known quantity. As a result, we get predictable costs for our backup requirements. The actual storage on the back end of the system is included and that means we don't have to plan for any storage growth or changes there. We just have to plan for the number of employees that we have. That makes it very predictable.

We researched Veeam Backup & Replication. The main factor in deciding to go with Metallic, at the time, was to stay with one backup vendor so that we did not have two different solutions in place.

The evaluation was to compare what Metallic was capable of doing with what Veeam was capable of doing for what we needed. We thought that Metallic was adequate so we stayed with that.

Use their professional services for the implementation. That was very helpful because whenever you're configuring anything that works in Azure, or AWS for that matter, there are complexities. The professional services walk you right through that so you don't stumble. After that, it's very simple to use.

The solution is definitely appropriate for an enterprise-level environment. The performance for both backup and recovery, in an enterprise, is very good.

When we signed up for it, it was a Microsoft Azure-based storage solution and Commvault has its relationship with Microsoft. We're just leveraging what Commvault offers, so there's not really any flexibility, but that's okay with us. We just subscribe to the service and it does what we need it to do. We didn't need storage flexibility or anything like that. We just needed what the solution had to offer.

What I've learned from using Metallic is "keep it simple." We use a very simple approach to back up everything and it works just fine.

We use Commvault to back up all our enterprise solutions, like MS SQL, Exchange, file servers, and MongoDB, but we don't use Commvault for multi-environment management. There is a primary site and a disaster recovery site that we control offsite with one console.

I know Commvault has another interface for the multi-site, but I've never used it before, so I don't have any experience with that. However, we have a passive primary server at the disaster recovery site, and if we have trouble at the main site, we can use the disaster recovery server. 

Commvault makes it easier to back up new additions to our environment. For example, when we added MongoDB, we found it in Commvault and could start backing it up. 

Right now, we are trying to integrate Kubernetes platforms into our environment, and I'm sure that Commvault can back up those. Commvault keeps up with new technologies, and if you upgrade to the latest stable version, you can find everything you need.

Backing up with Commvault doesn't require much effort. Commvault's reporting features are also excellent and user-friendly. It's easy to find anything we want. The workflow feature is handy, too. For example, we schedule an automated monthly backup and restoration test that we used to do manually. That has been integrated with Commvault's workflows and running automatically every month for four years. 

It runs all the tests and emails us the reports. We take daily, weekly, and monthly snapshots, and I integrate the storage snapshot scripts with the Commvault workflow. The Commvault workflow runs all the scripts and sends us the reports. It also features cloud-side reports and workflows. Commvault has many tools for backing up, restoring, and archiving, but we use another service for our archives. 

Commvault can show us unprotected workloads, servers, and SQL databases. It's a good feature, and I periodically get reports on this. However, it's a low priority because we are waiting for our inside customers to tell us whether they want something backed up or not. They must follow that, but we are using terabyte-based backups. We don't separate the agent— MS SQL or others—and we are only looking at the terabyte trends, so it's predictable for us. 

Our main pain point is that some of our hardware is old. For example, the SSD disks for our application database are slow. It's hard to avoid a slowdown in our environment because the size of our backups is growing every year. If you're growing and don't upgrade the environment, you will see slower backups and restores. You must enhance the environment if you are growing.

I've used Commvault for about 10 years, and we used it at my last company for around six years. 

Commvault's stability is good.

We have no problems scaling Commvault. I don't remember the numbers, but we have a terabyte license size. It's about 400 terabytes, but the backend is in the petabyte range. 

Troubleshooting is easy because Commvault support responds and finds the root cause quickly. When I've contacted support for other solutions, some of them ask you to recreate the scenario. They ask you to increase the debugging level and reproduce the scenario to get the error again. As a result, we waste a lot of time troubleshooting those solutions. With Commvault, we don't need to devote much time to the operational and troubleshooting aspects. 

I've used NetBackup before, and I think it's a good solution. It required more effort than Commvault, but I prefer it over EMC NetWorker. NetWorker was labor-intensive, buggy, and hard to use. We spent a lot of time dealing with EMC support. They have a large, competent support team, but we spent too much time with them. 

NetBackup is better than NetWorker, but it has fewer features than Commvault. NetBackup also has an old-fashioned interface that is harder to use than Commvault's. It's not user-friendly. Commvault is the best of the three.

Setting up Commvault was straightforward. You set up the primary server first, then the media agents, disks, and agents for clients. Each of those steps is easy. It's like a "next, next, finish" Windows installer. You can deploy it in half a day in a smaller environment, and it's maybe one or two days for a large one. 

Of course, it depends on the size of the agents and how many you need for your physical environment. If you have a rigid environment, it's effortless because you only define the vCenters or the Hyper-V management console, and that's it. You can take backups. 

On the other hand, you must install all the agents if you have too many physical environments. Still, Commvault makes it easy because you can install everything from the user interface on the primary server. In total, we have five people, including me, managing Commvault and all our other storage solutions. 

I rate Commvault 10 out of 10. If you're planning on implementing Commvault, I suggest doing a PoC first to try out all the features and to compare them to other products. We did a PoC for backup solutions to test some new features for our enterprise solutions, and some of the products didn't make the cut, so I would recommend a PoC.

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 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 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.