Commvault Cloud Reviews

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 really needed a product where we could extend the Microsoft Office 365 backups and archival process, as well as back up our Office 365 SharePoints and our users' OneDrives. That way we could have a seven-year retention plan and if we need to go back and grab someone's email that they accidentally deleted two years ago, we could. 

We also needed a solution that we didn't have to have onsite storage for, because we had a storage restriction onsite. This product gave me the ability to have everything stored, as a SaaS model. Everything is right there.

We recently had an issue where someone couldn't find an email that they had just recently written. When I went looking inside the backups, I was able to find and restore that email and they were able to continue working. It was very critical for a customer sale, but that email was recovered and it was perfect. Because it was just a single email, it was relatively quick. If I had had to do it another way, it probably would have taken me an hour-and-a-half to two hours longer with our old way of doing it. Before we went with Office 365, we were Exchange on-premises and it would have required me to have pulled out a SAN snapshot to recover the data that way, or go to the tape. Because this is all hosted in the cloud and works in the cloud, I was able to do it in five minutes.

Metallic has helped minimize the time spent on backup tasks, absolutely. It has reduced the time, daily, that I deal with whether the backup is up, and performing backups, by about 50 percent. I have more time to do other things.

I have been able to save on hardware costs at my site due to the low price of the application. I am looking at a reduction in infrastructure costs of at least 25 percent.

The most valuable part of the solution is that it is fire-and-forget. Everything we've programmed into this Metallic SaaS offering is what they claim it to be. It's been just a treat to use it. From starting the trial, to the 15 minutes it took to run my first backup, to the 30-minutes for my first restore of the users' email, it has just been fantastic. It works as advertised.

Since it's built off the regular Commvault product, and I use that Commvault product, the user interface has been very easy for me to get into. It's easy to use and navigate through. I've had no questions on how to find the relevant information, and their documentation has been on-point for helping me find all the hidden features inside their menus.

The Command Center, as far as providing a complete view of data goes, is 100 percent accurate. I found stuff that I didn't know about. I was able to find out that a couple of things are flowing in an odd way and I was able to get those remedied and treated in a way that ended up improving my boss' daily life.

It also provides me with a single platform to move, manage, and recover data across on-premises, hybrid, and cloud locations. It's a single window to see everything I needed to see regarding this level of backup. I really dislike like it when the company purchases multiple products that do similar things and I have to go to different windows to get full insight. This solution gives me the full insight without having to use other products, metrics, or reporting tools.

Since it plugs into my Office 365 tenant, it was literally three clicks. So it supports cloud well. And it's all documented well. They even provided training and onboarding help for that 15-minute process. It was just fantastic.

I would like to see some of the code execute a little bit better when I add new licenses and assign licenses to users. I'd like to see that information update a little quicker. It would also be helpful to be able to run a report on licensing so that I have better visibility into how much licensing I'm using.

I really have no other complaints beyond that. And they were able to get me that information relatively quickly when I submitted a ticket.

I've been using Metallic since day-one of its release in October, 2019.

I would give the stability "five nines." I've not seen it down. I can't say it hasn't been down once, but it's been up the entire time I've used it. There have been no issues. It's snappy and responsive. I'm impressed with the stability of it.

Scaling is amazingly easy. The way they recommend the setup, it is easy to drop a user into one of my security groups and, within 15 minutes, they are in the backup schedule rotation and are being backed up.

I have 75 users enrolled. We may have plans to expand in the future to start taking advantage of their endpoint product through Metallic. We would expand from 75 seats to 200 seats in the Office 365 backup, and would add on another set of 200 seats for their endpoint backup.

Commvault's technical support for the solution is knowledgeable. I haven't been able to stump them. They've been able to answer every single question and help me with any issues I've had. They've just been, bar none, fantastic.

We were using Backup Exec for a lot of stuff and ShadowProtect SPX, a StorageCraft solution. Now that we have this online, it's fantastic. Every product that we use from Commvault, in general, has been fantastic.

We switched to Metallic from our other solutions because they didn't provide the Office 365 backup component we wanted.

We needed a backup solution and I purchased their standard Commvault for our on-premises stuff. When I attended Commvault Go, their customer conference, they debuted Metallic and I said, "That's exactly the product I was looking for, for my 365 backup, and I'm buying it from Commvault." I already knew how their software works and Metallic is same. They're just doing it in a SaaS model for 365, endpoint, and even server backup if you want. I really needed that 365.

The initial setup is straightforward. It's 100 percent accurate on their website. From start to finish: 15 minutes and you're running your first backup.

My implementation strategy for this was for the 365, the OneDrive and the SharePoint components. When we brought it online, my goal was to target the 75 most used, customer-facing mailboxes. Within 15 minutes I was able to make sure the product was working and, by the end of that day, I had everyone applied. Compared to other products, that would have taken days.

If you have technical experience it will be straightforward. We walked through their installation script just to confirm I had everything done, because, given how new the product is, they wanted to test their help script. And it was spot-on. They had it perfect. I am fully confident that, even if a person doesn't have great technical knowledge, they would be able to help that person through it.

When I purchased Commvault Metallic, they did have an onboarding process that helped me if I had any questions. It was literally a 15-minute process. I did everything before we even had that phone call, so I got to spend the call asking a few questions. It was really easy. 

I would say we have seen a return on investment, but it's a hard metric to come up with due to DR. We haven't had a DR scenario where it has paid for itself. But I view it like buying car insurance. It's better to have it and not need it, than something happening and needing it and not having it.

We are paying on a yearly basis and it comes out to about $3.80 a user per month.

There are no other costs for the specific features that I have. If I was to use server backups with them, there would be an additional cost per terabyte of storage, based on my storage targets, or an infrastructure cost if I was using it to target on-ground storage stuff. But because I'm using the platform that includes storage for the Office 365 backup exclusively, there is no additional cost.

The other products I was looking at wanted to charge me anywhere between $10 to $15 per person and I would have to do storage on top of that. That means I would be paying by the terabyte if I was putting the storage in the cloud or having to purchase hardware on-premises to do so. With the Office 365 offering from Metallic, at the price point we got it at, it was perfect. They knew exactly what the market needed and they hit their marks.

We really didn't evaluate other vendors because none of them gave me the options that I was looking for and that Metallic was offering: a low price per user, and storage included for the 365 backup. With other products I would have had to purchase cloud storage and pay for additional storage, or the cost per seat was just not something I was willing to pay.

The biggest lesson I've learned is to remind people that they still need to back up Office 365 emails. Just because it's not on their premises, they should still back it up.

Commvault gives you a fantastic 45-day trial. It's worth trying it. They have a really good, long trial period. They will answer any questions you have during that process. I know a lot of people say, "Just try the product." With this one, try the product and you'll see the ease of use.

For deployment and maintenance of the solution, for our size of company, it's just one person, a system administrator who does overall operations support.

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.

Commvault is our primary solution for all backup and recovery; for index, for analytics, for everything.

When it comes to the storage that we use for backup and data aging, we were limited, at first, by the amount of storage that we could provide for onsite storage and archiving. Commvault's compression and deduplication within the application is allowing us to almost triple the amount of storage. For example, at one of our primary sites we're only able to store about 60 terabytes of capacity, but we actually back up 1.5 petabytes. We're able to squeeze that into the 66-terabyte license capacity. That is huge and saves us quite a bit of money in storage, and even more money on license capacity.

The solution also helps our admins to minimize the time they spend on backup tasks and to spend time on other projects. Throughout the corporation, we only have a handful of people who deal with the backup and recovery portion of our operations. With the number of requests that come in from time to time, it's nice to know that the single pane of glass, and the application as a whole, allow my engineers to quickly find an issue or resolve an issue that our users are having.

All its features are useful and beneficial, but if I had to pick two it would be the reporting and the support that they offer.

I'm a big fan of the reporting. You can build your own reports; it's very customizable. You can have individual reports going to groups of people or individuals. You can have them go out multiple times a day. It's basically a free-for-all as far as reporting goes. If anybody wants a specific job report every day, you can build it, schedule it, and have it go out and never touched it again. It's pretty nice.

Commvault also provides us with a single platform to move, manage, and recover our data across on-premise locations. I've done it multiple times. I've restored files, virtual machines, databases; everything from one location to another location within the United States. I've moved virtual machines, databases, and files between the two. An easier solution than the normal way of moving a server or application is to run a restore to another location. It runs faster and it's encrypted. It provides us with ease of use, instead of using a third-party tool. And I know that everything, all the permissions, all the user access, remains the same no matter where I restore to.

Their single pane of glass solution is daunting at first. It's not the easiest interface but, as with anything that you use, eventually you'll get better and better at it. I've worked closely with their user experience team to improve their web-based command tool. 

We try not to use the CommCell tool that is provided, because it's a little old and a little too powerful to give everyone access to it. So we've started using their Command Center tool. At first, it was hard to find things with that, but you end up finding them. Command Center definitely gives us a complete view of our data. But finding some of the granular, very small items that we sometimes have to find, such as auxiliary copies for tapes, I still find that it's easier to navigate and, sometimes, only possible to find them using the CommCell tool. Maybe that's just an area that hasn't been added to the Command Center yet.

Since I only use the backup and recovery, I'm not using Activate or Orchestrate. And I am strictly on-prem so I'm not using any of the Metallic or Hedvig solutions. I can only speak for backup and recovery. I would like to see a little bit more access into the CommCell areas via the Command Center. That would be my only small request.

In 2019 there was a flaw with their Active Directory plan which didn't actually allow you to recover the full Active Directory properly. I brought that to their attention and they made the change and fixed it. That was the only area that needed to be fixed.

I have been using Commvault for five years.

It's very stable. To be completely frank, I beat the heck out of it, 24/7 and 365. We're a healthcare laboratory company that never closes. We're an around-the-clock operation in all of our locations. The backup jobs are running, and the reports are running, around the clock. Everything runs constantly but we have had zero downtime.

It scales out pretty easily. There's not much on the Commvault side that scales out; it's more the storage repository that's required. There's not much it can't do. 

One thing that I have been requesting is a Linux-based virtual server agent. You have to stick with Windows for the actual CommServe. We'd like to move to a Linux-based OS to release some licensing. I'm sure, eventually, that will come. We have a few Macs in our environment with Commvault on them. We don't often use the Edge client that they provide because the laptops and desktops we have use what is called DFS or file redirection. The files that they have saved are saved on the server instead of their laptop. Since we deal with PI and PHI, we can't have any of that stuff on a laptop. We have 10 Edge backup licenses and we have it on four or five of them, and one of them is a Mac.

Everybody in our company is affected by Commvault. We have about 7,500 employees and everybody uses a product or an application or a database or a server that is involved with Commvault.

For deployment and maintenance of Commvault we have just five people. That includes me as a data center manager and the other four are server engineers.

Commvault's support is a 10 out of 10. I've learned so much from the support. They're very fast and they're very flexible. If they can't figure out a solution right away, they offer a work-around pretty quickly and they always want you involved with the solution. They even offer custom solutions for things that their applications don't do. If you run into a service pack limitation or a limitation with the product itself, they'll actually add the solution they come up with as a feature in their application.

We needed to pick a global solution. I had been reading about Simpana, which is Commvault now, for a while and I had the opportunity to jump right into it and learn about it while deploying it. I had never used it. Everything, on paper, was exactly what we needed as far as it enabling a very granular setup goes, without it being a one-size-fits-all-application. That's what I liked about it: being able to customize and mold each location to use Commvault.

I had other requirements but they were requirements that I didn't know that I had until after I had found that I could do them in Commvault.

The setup is extremely easy. The first time I did it I was a little worried that I didn't do it properly because it was so easy. The overall configuration is a little bit more difficult, but that's roadmap-based configuration, so you have to think very far down the road when putting this together. You can't be thinking, "Oh, I only need this for a couple of months." It's a 10-year plan.

The setup itself took a couple of hours.

Since I had never used Commvault before, we had implementation support from Commvault. They walked me through it. They asked questions and I gave them answers and then they showed me what they were doing. What they showed me made sense. From there, the configuration started, which was mostly on my part. A lot of it was pretty straightforward. There are things that are difficult in a domain environment, things that take a little bit of configuration, such as setting up additional users and passwords for service accounts. But overall, it's a very streamlined process.

I think Commvault's model is now cost-efficient. When we first started with Commvault, I thought it was overpriced. I thought, "That's a lot of money for a piece of software." But as I used it, and developed a trust in and knowledge of the application, I definitely was made aware, very quickly, of how it was worth every penny. Over the years, it has actually become cheaper, due to the fact that I've become smarter about how to use it better. With that knowledge, you learn how to save money with the application.

I've used other solutions in the past, such as vRanger, Symantec Endpoint Protection, Metalogix for Exchange, as well as Data Domain. For data recovery, the others are definitely not as streamlined. I've had quite a few situations where I've had to recover large amounts of data but I don't have a comparison of the recovery times of Commvault versus the others because, in the last five years, all I've used is Commvault. All my large or business-critical restorations have been with Commvault. But judging by what I've done in the past, Commvault is far easier and far more consistent than any other application I've used.

In terms of advice, the biggest thing I would like to say is don't look at it as a dinosaur. A lot of people associate Commvault with being old and antiquated, and not having all the bells and whistles. If you look past that, you'll see that it's more far more capable than anything else that's on the market. You have to get through the complexity of the application and from there you have to trust that it will do what you want it to do.

The biggest lesson I have learned from using Commvault is don't be afraid to call support.

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.