Commvault Cloud Reviews

Overall, Metallic has helped us out tremendously from a backup and restore situation. We just had a pretty major restore that we had to do from Metallic two weeks ago for a file that was basically deleted five days ago, and they needed a copy from seven days prior to that. My whole team walked through the restore in about two to three minutes. We basically figured out which buttons to push, then the restore was done 30 seconds later. That was an eye-opener at that point, because we understand what a great decision we made by going with Metallic.

If you ask me today whether Metallic was appropriate for an enterprise-level environment, then I would say, "Yes." If you asked me a year and a half ago, I would have said, "No." Normally, you would think that a cloud-only backup type solution probably wouldn't work for an enterprise environment. Then, here comes NDOT and we're about as enterprise as it gets when it comes to the state of Nevada. Right now, we are doing all kinds of neat stuff with this solution where normally you would need an on-premises solution. They have me convinced now. We are backing up stuff that I couldn't get MABS or Rapid Recovery to backup, and those are on-prem and cloud, e.g., hybrid solutions. If we wanted to, we could go to hybrid with Metallic, but their cloud solution is so stable right now.

I ran the solution through my CISO. When it comes to server guys, I am probably the security-conscious systems guy on our team. I went to the same training that our CISO did. Between him and me, we love Metallic. We think their security is definitely acceptable at a high level.

The ease of use is the most valuable feature, which keeps the training down. Pretty much anybody in my group right now can do a whole bunch with Metallic compared to what we could do with our previous solution, on-prem Commvault. The ease of use is probably my number one priority. With the amount of systems that our systems team deals with, the ease of use is the most important thing. We were bouncing around all of the time from this system to that system to this system, trying to remember how things work. Whereas, Metallic keeps it simple.

It is just about as flexible as you can get; simple. You can put it anywhere you want. You can put it on-prem or in your cloud. I could see where a team that's looking for more of a follow the bouncy ball type of solution might get a little confused. "Oh, no. What do you mean I might have to do it this way or I can't do it that way?" Sometimes, people just want to be told what to do. For an enterprise environment, like we are at NDOT, everything we do is not standard. It is not industry standard; it is not normal. We have all kinds of one-offs. We do need flexibility in the solutions that we get. I will say that Metallic has been extremely flexible in that sense, where we are able to follow the bouncy ball if we wanted to. Obviously, we didn't. We did it our way and Metallic, as a whole solution, provided that to us with no issues.

Permissions can be tricky. There is granularity when trying to get people to write permissions to be able to view, backup, and restore. It is just hard to understand that granularity. I can't even 100% say that it is Commvault. I can say it is not super cut-and-dry right out of the gate. However, I would also say it is great because it is granular.

Getting my guys the right access has a learning curve. Sometimes, it is, "Oh, okay. I think I got it for you." Then, they say, "Oh, nope. I logged in but I can't see this." Then, it is, "Okay, hold on. Give me a second. Let me change that. Okay, it's this one." That learning curve has probably taken a little bit longer than some simpler things. So, Metallic has some granularity, and as a systems administrator, I appreciate that. At the same time, I also realize that I have to learn it.

Seven to eight months ago, the documentation needed improvement, but they have caught up on it now.

I have been using it for a year. My team has been using it for about seven to eight months.

It is a very stable platform.

Right now, we have seven guys on my team and two of us are setting up the backups. The other five of us are strictly doing restores mainly until we get all our backups entirely into the cloud and clean up the groups. I really just need two guys doing that, a junior admin and me. The junior admin has been setting this all up because he will be around for another 15 years. I might as well have him learn it now and be our guru.

For the most part, it does the updates for us. There is a piece that we own down on our network and there is a piece that they own on their network. For the most part, the piece that they own is definitely the bigger of the two. With that being said, our version that we are running on-premises needs an update, which basically means that it is waiting on a server restart. Our servers restart once a month, so I imagine it is scheduled to restart on Sunday. Then, we will get that up-to-date. Metallic pushes it out, then our server installs it. Metallic is mostly on the hook for updates and keeping things up-to-date.

It is 100% scalable.

We were on a hybrid system, which was on-prem and in the cloud as well as local. We had probably 10% of our servers that were backing up locally to themselves. We had about 40% of our big, large servers backing up on-premises. Then, the other percentage was backing up to the cloud.

Once we moved to Commvault, instead of about 80% of my servers backing up to the cloud, we will shortly have them all going to the cloud. Now, I'm not hybrid, but in a simple solution, which is a cloud backup solution. Adding to that is as simple as going to Azure, and saying, "Hey, I need this storage count to be a little bit bigger," as long as I have pre-planned the amount that I would buy from Metallic. In other words, Metallic gives us a price on 100 servers. I know that I have 50, and I am good to scale for another 50. All I have to do at that point is go into my Azure tenant, have it give me some more storage, and at that point now I am scaling.

Now, if I need to, I get a hold of Larry over there in Metallic, and I say, "Hey, buddy. I need to add another 50 servers." Then, he gives me a price quote, and we pay them again. The solution is simple, easy, and scalable. I don't need to buy hardware. I don't have a bunch of engineers down here reassessing our environment. I just got to add some more storage to the cloud, then I start sending more data out to the cloud. I would say, "Scalability is wow." They have done a great job there.

I had a conversation yesterday, between me and my manager, about when we will use Metallic's Office 365 Backup & Recovery. First, we need to get our backups. Between the Metallic solution, the file storage optimization, and now the 365, which are the three things that we have gotten from Commvault over the last year. File storage optimization is next, then 365 is after that. I am going to say sometime in October.

So far, I would give Commvault tech support 10 out of 10. We have dealt with some good and some bad tech supports. Between Microsoft, Dell, and Commvault, those three solutions are at the top of my list when it comes to support.

Anything that we find is usually something that we can fix ourselves. We can get ahold of support, then support takes care of it.

We were using Microsoft Azure Backup Server (MABS), but there were many problems with it. We turned around, started using Metallic about a year ago. I tested it out. We now have 80% of our servers being backed up to Metallic. We will probably have the rest in the next six to eight weeks. At that point, for the first time in two years, we will have all our servers completely backed up.

When we used to have the on-prem version of Commvault, it was nothing like Metallic. Metallic is a different solution, but it is Commvault. Back in those days, when we had Commvault, it was pretty complex. It was very granular. It had many features, but it was complex. You really only could have one or two guys working on it.

We left Commvault five years ago because the grass is always greener on the other side and cheaper: bigger, better, and stronger. Of course, we came to find out: none of the above. Nothing was true. Basically, we were talked into it by Dell EMC. My old manager, the person whose position I now have, was talked into using Quest Rapid Recovery product by Dell EMC, saying, "Hey, you don't need Commvault. They are one of the biggest backup solutions in the world, and we are an up-and-coming, starting company. We're going to make it cheaper for you. We are just as good. We will show you some cool demos." Those demos looked great. Of course, we went with it. To make a long story short, in the four and a half years that we had Quest Rapid Recovery, we were never compliant on our backups, not once. We were duped.

We are finally back with Commvault, and we now have a 100% compliance backup solution. 

We switched to Metallic because of money. Right now, we are paying less for Metallic than we ever were for Rapid Recovery. I have reclaimed man-hours back for my team. I had one guy for five to six hours a day managing those two other systems, Microsoft Azure Backup and Quest. I lost four to six hours a day for one of my top-level guys by having him troubleshooting that all day long. By going to Metallic, we have freed up man-hours, infrastructure costs, and the time to manage.

I did the first initial setup all by myself. I had it set up in about an hour and a half, then I was backing up a server in about an hour and 45 minutes. It was pretty easy. That was our proof of concept testing. I did that for about three or four months, then I blew it up, broke it, and reimplemented it. 

When we started using this solution, it was seven months into its infancy. By the time we bought it, they had just hit their first year. It has definitely changed around making things a little easier, instead of having to go: here, here, here, here, and there. They have simplified things. They have created nice new little shortcuts. 

The interface now is super easy. You can fumble around in there, then after awhile, you are like, "Okay. That is how this works."

The process of switching to Metallic was really easy. We actually ran Metallic backups during the MABS backup. In other words, we were actually backing up with those solutions as we migrated to Metallic. Of course, we had to age-off. The fact that we did not have to turn off the other backups so Metallic could do its backups made the implementation extremely easy. The cut over was easy. 

We were able to run it in parallel with the other system. It didn't cause any issues. It tells me right there that it's not the same design. Because if it was the same design, then we would've had to turn off the other one which means that we would not get backups for two or three weeks while Metallic catches up. That is not always a good thing to do when you are talking about important systems. Because of Metallic's different way that it backs up, we were able to run it in parallel. The implementation was very simple. It wasn't like we had to go and pull the tablecloth out from underneath the glasses while they were still sitting on the table. It was extremely seamless because of the fact that their backups are done differently than the not-so-good solution we were going with.

I had a couple phone calls with engineers and broke it really good a few times, to the point where it even broke up their stuff there. Once we decided we were going to buy the product and implement it into our environment, they set up a couple of calls with their top level engineers and had us set it up even better than I did in my test environments. They were really good about helping us. So, their assistance and the ease of setup were great.

After it was approved through our infrastructure technical committee, I needed to get a call set up with their engineers for an initial setup of the plans. The first plan to get going the way they recommend. Because when I was testing, I tested from every angle. I broke the heck out of it to know its limitations. We created an initial phone call with their engineers, who helped us set up the first 20 VMs to get backed up under their idea of how they set the system up to work. This was good because I didn't understand this when I was doing my testing. I just did the things I thought that were supposed to be done.

We had a second follow-up call with them. That second follow-up call was for any questions that we had for the month in-between what we were doing with our backups, e.g., checking things out and playing around. They answered a whole bunch of questions for us and helped us set up single sign-on. It was a smooth process. They were willing to help us out, which helped us out tremendously. We basically used their support to help us implement the solution.

Once you set up a bunch of these backups, you will get notified in an email if they are wrong. If you're not adding anything the next day or another server, there is no reason for you to even be in there, unless there is a restore. 

At the moment, we are trying to add 400-plus servers. Therefore, we are going to have a guy in there for half an hour to an hour a day adding a few more servers. When adding a few more servers, you need to be careful. You don't want to rock the boat too much, then all of a sudden you have a big problem. So, it is just a little bit at a time. Right now, we are talking about an hour once or twice a week. Once our servers are sitting up there and this stuff is going, there should be no maintenance. 

I have made this very clear to my team. I don't need a guy in there, like we did with Rapid Recovery, chasing down errors. There are no errors. It is backing up. It will tell you when it is not. Then, when it's not backing up, we will tackle that. 

I just don't see a lot of maintenance on this solution. Management of it really has nothing to do with anything unless you are fixing or reimplementing something. For the most part, once you set it, then it is a set-and-forget SaaS solution.

We have a seven-man team. I am the supervisor with six guys underneath me, who are all veteran IT professionals. One of those gentlemen, a $100,000 a year guy, was on Rapid Recovery for four to six hours a day, every day for the four years that we had it. He was just maintaining it, fixing problems and backup errors. When we went to MABS, it was the same problem. He was now managing both of these things, because we were dual-headed at that point. Once we got into Metallic, I had one of our junior-level admins, at that point, take this project on. He moved 80% of our servers into the cloud and basically checks an email once or twice a week, looking at the backups for about 20 minutes a day.

The labor has gone down exponentially. It is insane. We are talking about a $100,000 solution that we paid for Rapid Recovery a year, plus the $100,000 a year salary for having one of my guys managing it every day. Whereas, we are paying Metallic an X amount of dollars right now and spend about five or 10 minutes every other day just to verify that the backups are good. We don't have to fix anything.

We are basically getting rid of hardware that we were paying for Rapid Recovery. We are actually leveraging some of Rapid Recovery's hardware for MABS, so we cut down on MABS and Rapid Recovery. Now, the hardware that we would need to renew warranties and get support for is no longer necessary.

I used the free trial to test it. That was our proof of concept. I had the servers up and running by the middle of the day. I think I started it some time around breakfast. It took a couple of hours. It was really simple.

Hands down, Metallic provides us with more predictable costs for our backup requirements. You are getting what you pay for. If they are charging you X amount of dollars at that point, that is what you are going to pay. So far, I have not seen any hidden costs or any kind of gotchas. It is pretty cut-and-dry. They will let you know, "Hey, you are going to use our storage and it will cost you this much. You are going to use your storage, then we are going to charge you this much to backup." What they told us they were going to charge us is exactly what they are charging us now for the next two and a half years.

We also evaluated NEC, which is another big solution out there, like Nike or Converse. NEC has their own data centers. The government uses them. They are big and their solution is robust. We tested it, and it worked well too. However, the bottom line was a huge sticker price shock. We went with Metallic because of cost. 

Since I have been in this NDOT environment for eight years, we have used Commvault, Rapid Recovery, MABS, and now we are back to Commvault Metallic. Of those four products, with Commvault being the first and now the last, those have been the two more stable products. The first one that we used was Commvault on-premises, with MediaAgent and physical servers on-prem, which was extremely stable. Then, we went to Rapid Recovery and that wasn't stable. Neither was MABS. Now, we are back to Metallic and it is stable again. Most solutions I have used from Metallic, from the on-prem now to the cloud, have been extremely stable when it comes to backup.

Definitely take advantage of the support team in your initial rollout because Commvault is not a follow the bouncy ball type of solution. It is definitely granular, configurable, and scalable. With the initial deployment, it is important to get that right because everything is going to start working off of that initial deployment. It is a good idea to take advantage of their support tier in that initial deployment and not try to set it up 100% on your own. I did, and It worked. However, once we got a hold of the engineers for the production rollout, they started answering some of my questions. If I would have known the answers that they gave me back when I rolled it out, the rollout would have been much easier and not as hard as it was. It could have been even better. 

Get a little knowledge from these guys. Have them help you roll it out. It takes half an hour. That is all it took us. We had the engineer on the phone for half an hour. He had us setup and backups going, with the vision that Metallic was built for, not the vision that I had thought it was for. My biggest recommendation is to take advantage of their support during the initial deployment. From there, you can be as creative as you want. It is always good to get that help in the beginning.

There have been discussions about doing the solution’s Endpoint Backup & Recovery. It really just comes down to the fact that we would need more push from the business. Right now, the business understands that most of their data is stored in the cloud as-is. So, backing up into a computer is not necessary, as the data that they are putting on that computer is in the cloud. I don't see us using it any time soon.

Right now, Metallic is used a lot. For the most part, it is now the entire backup of our 400-plus servers. It will be used even more with the 365 implementation, Active Directory backup implementation, and disaster recovery. One of the good things about going to Metallic in this cloud solution, where all of my servers now live in the cloud, is I have a DR solution now, as opposed to having to move it down to another place or building in Las Vegas. Now that we are central with our backups to the cloud, we can focus on a DR solution. It definitely is very important to our infrastructure. As a server team, backups are number one. Metallic has now become one of our fallbacks on solutions for all kinds of stuff.

Spend it if you got it. The biggest lesson that I learned from using Metallic is sometimes going with cheaper isn't always better. That is why we left Commvault. While Metallic might be a little more expensive than Quest or MABS, with that extra dollar you are paying, you are going to get your money's worth.

I would rate them as 10 out of 10. I can't really complain. Right now, they look like a knight in shining armor. What do you normally do with a knight in shining armor? You put a medal on him.

I've been here for 37 years and I've seen all the data challenges there are. The Centers for Disease Control consists of multiple centers that are all under one umbrella of CDC, but each center has its own budget, its own IT, and its own data collection. They were all disparate and they could not be put under one system where we could protect all of them. Everybody had their own protection. Everybody had their own little silos.

Around the time we brought in Commvault, our challenge was to bring those silos together where one larger team could diversify into specific areas. For example, disaster recovery was a whole team of people. That's all they did and they specialized in it. We could develop SMEs in each area of IT, such as disaster recovery, database, and hardware configuration. We had to attempt to bring all these silos together. There's resistance to that to this day, because everybody thinks that they're special and the other people don't matter. Our challenge was centralization at that point. Each area had its own way of backing up and several of them had Commvault already, but it was at that point that we settled on Commvault as our backup solution.

Before Commvault, virus infection was our big problem. If a virus got fished into a system, recovery was disastrous.

Currently, our use case is disaster recovery, pure and simple, including everything from a file restore to a complete system restore.

It is on-premises and also hosted in the cloud. 

We've had problems in the past where a storage person made an error and actually deleted a large chunk of storage, and we recovered it with Commvault. If we had lost that storage, it would have been a catastrophic loss of scientific data. The value of that is incalculable.

In addition, when we're applying for authority to operate, compliance requires that certain things just have to be backed up. That's a requirement of any system that we allow on our network. It has to be recovery-protected in some way, in the event of an error or a tragedy or an attack.

What is most valuable to me are the search features, where you can search through large backup data sets and find what you're looking for. Our data sets are so big that we're over the petabyte mark. To find a specific file for a specific user out of 10,000 users is a challenge. Sometimes the user doesn't know the file path. If we can glean from them a general description of where it might be, the search feature comes in very handy to actually locate it and restore it for them.

If you compare Commvault's user interface for managing on-prem, cloud, or multi-cloud environments in one place with some of the newer stuff that's coming out, it may seem to be a little too complex. But it's so powerful that I don't think the newer stuff competes with it that well.

And Command Center is helpful for reporting to upper management because they want to know the total figures, like how much we are protecting. They want to know the value of what we're doing compared to the cost of it. With Command Center we can tell them, "Look, we're doing this much and we've had this many restores." I have to do monthly reports to upper management on how successful we are at protection.

The solution also supports a broad coverage of workloads, absolutely. We use the VSA backups which means we don't have to have a client on each server. That, in itself, reduces a lot of the complexity. The broad coverage also means that we don't need as many personnel to administer things. It also helps with productivity. We're able to meet our SLAs for restores much better than we would otherwise.

The main area for improvement is that we sometimes experience negative effects from their updates. If they had a larger test area for their updates, that would help. I'm sure that they test, but our environment is probably 1,000 times bigger than their test environment. There are way more complexities in our environment, things that their updates overlook, and that causes a ripple effect of errors.

I've been using Commvault for about 15 years.

As long as everything functions in our environment, Commvault is very stable, but that's not the case. There are always ripples in the environment and sometimes those ripples can cause dramatic effects in Commvault, such as corrupting DDBs.

It's plenty scalable. That's one of the main reasons that we use Commvault. It gives us scalability and versatility across multiple storage platforms.

Their technical support is excellent. Any issues that we've had have been resolved.

At the time we chose Commvault, it was the best, according to our evaluation. There were three main options: NetApp, Commvault, and one other. There wasn't a lot of competition in that area for enterprise-level organizations.

The initial setup was a long time ago and I don't even know if I was involved in it. My lead engineer was involved in it. I was just an overseer at that point and just moving into that position. 

But I do know there have been a lot of complexities in upgrades from one version to the next. Sometimes we skip a version and go from nine to 11, for example, and there is complexity in that, or there has been in the past.

We had direct support from Commvault.

When it comes to ROI, Commvault is like the return on investment with insurance. When you need it, you see it. But if things are going smoothly you don't see it. However, it has to be there. My favorite saying is, "People really don't care about backups. They only care about restores."

One of the most interesting aspects is that the licensing model can be modified. We're paying for our licensing by the client, as opposed to the size of the footprint of the backup, which decreased our cost by about 20 percent.

There are multiple costs involved. We have the hardware, the tape drives, and the storage that our backup targets use. We use non-recommended storage, which is not as robust as what Commvault recommends, but we're able to make it work. That saves a lot of money on storage and its maintenance.

I've looked at other solutions but to scale them requires multiple devices, dedicated appliances. In our environment, everything has to be security-scanned and remediated on a monthly basis. The more devices we have, the more complex it gets to do that.

If you're a smaller-sized entity, Commvault may be a little bit more than what you need. You get what you pay for. Commvault's scalability and granularity are excellent for a large enterprise, but for a smaller one, some of the alternatives are probably more cost-effective. In this context, a large enterprise is one with storage in the petabyte range. That's where Commvault shines.

Our Commvault partner is KELYN Technologies. They're a very professional support service, as an intermediary between us and Commvault, so that we get really professional and timely support. We even bring them in on our proofs of concept. As new technologies develop, we have to prove that we can back them up or support and protect them. Having their engineers available to help us work through those issues is very valuable. Anything that they can't solve, they escalate directly to Commvault for us. That way, we don't have to be in that exchange with Commvault. If we're doing a proof of concept and get to an area where we just don't know how to deal with it, they go off, find out, and come back and say, "Okay, now we know how to deal with it."

And while my staff was mostly pre-trained on Commvault, as new developments and new enhancements come out, KELYN is right on top of them.

The value, for us, of KELYN comes from the following:

1. We have a reduced licensing cost.
2. We have more granular access to engineers to assist with new technology, new concepts. 
3. And sometimes we'll change our methods due to a new enhancement and they're invaluable in getting those things set up and working correctly.

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

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

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

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

The price of Commvault HyperScale X could improve.

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

Commvault HyperScale X is highly stable.

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

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

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

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

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

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

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

The company that has the solution is managing the solution.

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

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

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

We did evaluate other solutions before choosing Commvault HyperScale X.

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

I rate Commvault HyperScale X a ten out of ten.

We use the Commvault HyperScale X to manage complex infrastructure, so deployments are fast.

Commvault HyperScale X is also a good choice for regulations that require the backup system to be isolated from the rest of the infrastructure. If there is an issue with the software, we open a support ticket with the software vendor. We then escalate the case to the hardware support team.

Commvault HyperScale X is more expensive for hybrid environments than traditional solutions.

I have been using Commvault HyperScale X as a reseller for five years.

I rate the product’s stability an eight out of ten.

The scalability is very good, but there is a limitation on expanding the cluster to scale to a higher level. We have smaller and enterprise-level clients. I rate its scalability a nine out of ten.

We have a team of four to manage support. We have many paid credits for networking and application support.

Positive

The initial setup is moderately easy. I rate the process a seven on a scale of ten. The deployment time depends on the environment. It takes around four to eight hours to complete.

I rate the product’s pricing a seven out of ten.

If the customer needs to protect five terabytes of data, they will need five licenses if they need to upgrade to make devices flexible or create this model. Many small customers can start with a 10TB appliance, and enterprises can scale up to 50 TB. The appliance is compatible with various hardware platforms, including LG, Lenovo, IBM, Dell, etc.

I recommend the Commvault HyperScale X for its enhanced quality, performance focus, and data isolation. I recommend looking for support for various solutions from a single vendor. Overall, I rate it a seven out of ten.

We use the Commvault for data optimization because it maintains enough data. We have implemented it to run two incremental backups per day and a full backup at the end of the week. We also perform the restoration of the database and DR servers, using it.

Commvault is a software-based solution that can manage backups to any storage and VMs. It integrates redundant storage and preserves jams in a storage area, providing up to 70% compression rate. Backups of large volumes do not take much time to complete. It also facilitates restoring Oracle data, which can be opened directly to a database after restoration without any user intervention.

There are still a lot of ways to improve the recruitment process. Commvault deployment is executed remotely, but managing their support on time is difficult. They reply to the support portal weekly, but there are some delays.

I have been using Commvault Backup & Recovery as a customer for around two years.

The stability is good. I rate the product’s stability an eight out of ten.

There is some gap in technical support, but it is good. Restoration happens only when there is a disaster. In that case, customers always expect the solution providers to be present. They regularly go through the update process and release updates frequently.

Neutral

The initial setup is easy. Integrating the database and server for clients might be difficult. The deployment does not take much time. However, changing advanced features or integration may take some time. Once the software and backups are ready, it will take seven to ten days to complete. You may need more people involved in the deployment if you have many servers. A team of two to three people is usually sufficient, including a deployment engineer from Commvault and two to three executives on the client side. I rate the process a six or seven out of ten.

The product generates a good return on investment.

I rate the product’s pricing a five out of ten.

They should decide to go for Commvault Backup & Recovery or another solution depending on the infrastructure requirement. 

I rate it a seven out of ten.

We use the solution for file system backup, Linux OS system backup, and Domino backup. Our data center team uses the solution for testing servers and database-level backups. In my company, we are not using the end-point features.

Earlier, it would take us a long time to create a backup. After implementing Commvault, the time needed for creating a backup has been reduced.

IntelliSnap and file system backups are valuable features. There are multiple functions, but we are currently using these two functions.

Data center backup must be improved. We also want the product to provide us with a cloud-based backup. If we use Microsoft Exchange Online for email services, we want to know how to get a backup in Commvault.

I have been using the solution for the last three years.

I rate the tool’s stability an eight out of ten.

The solution is really good in terms of scalability. I rate the scalability an eight out of ten. We have deployed the product in three factories. We are centrally managing the solution from the head office. Three people in our organization currently use the solution 24/7 to its maximum potential.

We have faced a little bit of delay in support. The support team is not available during the night. The product must improve support.

Neutral

Previously, we were using EMC NetWorker. It had some limitations. We compared it with Commvault to determine which solution would fulfill our requirements. We switched to Commvault because it had certain features that were not available in EMC NetWorker.

The initial setup was easy. I would rate the ease of setup an eight out of ten. Currently, we are using the solution on-premises. We are also checking whether we can take backups on the cloud. It took us almost three to four months to deploy the product.

Commvault Professional Services helped us with the deployment. We required two or three professional team engineers for the deployment. We have two to three engineers to manage the solution in the data center.

The tool is affordable. I rate the pricing a six out of ten. Implementation requires additional costs because we need Commvault Professional Services.

We evaluated other options, like EMC Networker and Veeam.

People considering using the solution must consider their budget and requirements. They must also consider the quality of support. Overall, I rate the solution an eight out of ten.

The solution is used as a backup for Office 365 workloads.

Pricing and functionality can be improved. The way to configure is not as simple as the configuration itself, nor is adding users within the backup scope.

I have been using Metallic for more than three years. I am an end user. I am using the solution's latest version of the solution in my organization.

The solution's stability is excellent.

The solution is scalable. 

Also, it is used by 380 users.

I rate the solution's scalability a nine out of ten.

The customer support is not good. There should be fast responsiveness and more proficiency when solving the issues or when helping solve any issues. I rate customer support a six out of ten.

Neutral

Some configurations could have been simpler, and the recommendations could have been more precise in allowing only certain users to be included in the backup scope. We could use group membership. Based on the user's group membership, they would be included in the backup scope. It's pretty simple, so if a user belongs to Group A, they will be included in the backup scope, and if not, then they won't be.

The deployment took two days, and one engineer was required for it. If you refer to maintenance as the procedures to test the restore and the options or directions, there's something else.

The solution is expensive. The subscription is based on a monthly basis. There are additional costs that vary depending on the size of the backup.

What we had before was that each user needs to be licensed. We purchase the required number of licenses and are priced accordingly per license. This pricing is independent of the backup data. Now, Metallic has changed, and the pricing is either per user or per license, in addition to the amount of backed-up data.

It supports SharePoint Online, OneDrive, and other services.

Overall, I rate the solution a seven out of ten.

We use the solution for mail archiving and sync application features. We can back up the virtual environment with its help.

They should provide more integration with OpenShift for the solution. Also, its support could be better.

We have been using the solution for five years.

I rate the solution's stability as an eight.

We have four solution users in our organization. I rate its scalability a nine.

The solution's technical support team resolves the queries efficiently. However, it takes time to respond.

Positive

I have used IBM Spectrum Protect before. I have attended training sessions and implemented them as well.

The solution's initial setup process is complicated. One needs to know the product in-depth for easy deployment. It takes a couple of hours but depends on the type of environment. Also, one executive with good knowledge can conduct its maintenance process efficiently.

The solution's cost is reasonable. I rate its pricing a nine.

I recommend the solution to others and rate it as an eight.

We use the solution for backup and recovery.

The solution's most valuable features are compression and duplication ratio.

The solution's pricing could be better.

I have been using the solution since 2020.

It is a stable solution. I rate its stability as an eight.

It is a scalable solution, and I rate its scalability as an eight. Currently, we have three solution users in our organization.

The solution's initial setup was complex. Our team contacted the vendor for assistance. They logged in remotely with us and solved the issue.

We implemented the solution with the help of our in-house team.

The solution is highly-priced.

I recommend the solution to others and rate it as a nine.

The solution is primarily used to protect against ransomware. It helps protect data and allows for data recovery and backup.

The data protection itself is very good compared to other products. 

The backup agents are helpful.

Its pricing is pretty competitive. 

The technical support is responsive. 

It is easy to set up.

I haven't had any challenges with the solution. 

The pricing could be more flexible in terms of licensing. It would help attract more customers. 

I've used the solution for three to four years. 

We have around customers using the product with 5,000 or more users.

The response in terms of support has been fine. Whenever they need help, the team can respond to the ticket. They do provide solutions to issues. That said, I don't really use customer care directly.

The vendor will offer support contracts. The customers can decide if they might need support or not. 

The initial setup is straightforward. There are basic steps to follow for the installation. That said, I do not handle the setup directly. From my team, I have not heard of any kinds of challenges. I'm not sure how long it takes to deploy the product.

We handle the implementation for clients. 

The solution's pricing is competitive. It depends on the number of users required and if any discounts are leveraged. Bigger volumes will lead to bigger discounts. 

We're provided the solution to clients. We are implementors. We are using the latest version of the solution. 

I'd recommend the solution to others. I would rate the solution eight out of ten.