Commvault is highly scalable. We've successfully extended its reach by replicating the on-premises environment in the cloud and leveraging additional capacity across other utilized environments. This flexibility aligns well with the subscription licensing model.

We have not encountered a scalability issue yet, and I do not foresee one in the near future. With proper infrastructure planning, I am unsure of the maximum scalability of Commvault Cloud, but we have scaled it to a significant size without any scalability issues. I believe the biggest limitation is that we are running Commvault on Windows, and Linux support is currently available. We will eventually migrate to Linux, but we are waiting for that side of the product to mature. Once we are on Linux, I believe scalability will no longer be a concern.

We are still running with a single server, and it's a per server per instance-based license model. If we need to add our first storage-based model or another division, we cannot support both. It's a licensing model issue. 

It's scalable, absolutely. I imagine we are small in the world of Commvault. I can't imagine any point that we would get to that Commvault couldn't handle and manage well. But even for significantly larger companies than us, Commvault is going to be one of the best partners to grow with you.

It is very flexible. We did not find any issues with regard to scalability. We are backing up eight petabytes of data. 

In terms of users, we are a team of six people providing 24/7 support. We are a part of the Global Data Protection team in our organization. In our team, we have Data Protection Engineer 1, Data Protection Engineer 2, and Data Protection Engineer 3. Apart from that, we have Architect 1 and Architect 2. These are the standard roles in any team across the organization.

We have very well-versed and capable engineers in our team. Our team is capable of planning, designing architecture, and managing operations. We have distributed these roles across the team. There is no dedicated person. Recently, we implemented Metallic in our environment, and as a senior member of the team, my role in that project involved planning, designing, and coordinating with the vendor. I also had to coordinate with different internal teams. We have something called Architecture Review Board. We plan and come up with a solution, and then we propose it to the management and get all the approvals. I have been a part of that. In addition to this, I do the regular normal BAU activities. I spend around 40 hours a week working with Commvault because I am from the core backup and the core data protection team. 

Commvault is the only enterprise application that we have for this purpose. It is being used in our organization for protecting data, and we plan to continue with Commvault. We don't have any plans to switch.

I am impressed with Commvault Backup & Recovery's scalability and my ability to use different storage options.

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.

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.

We haven't been involved in any scalability. We just have a simple backup for our four products, and that's it. I am sure it is scalable since I can see in their dashboard that they use Dynamics 365, Salesforce, and do endpoints. However, we do not use any of those products.

The project has been handed over to a BAU (business as usual), which is a team of two server engineers who work with it. One of the engineer's jobs is to check the backups daily. That involves checking the Metallic backups. We set up an daily email, which they receive and can confirm the backup has run. Rather than log into a dashboard, look at figures. or go around looking for information, it is on their fingertips in the morning. It takes one minute and their job is done.

It's appropriate for an enterprise-level environment. It's scaled with us from 900 mailboxes to 12,000 mailboxes, plus our scale of the Office 365 platform.

Before the COVID pandemic, we had six users using this solution. They're system administrators, they manage infrastructure and systems.

It has a 100% adoption rate. The product is being used every day. The backups are automated four times a day and we restore them on a need basis. We use the product every day.

The tool is perfect. I rate the scalability an eight and a half out of ten. It is scalable according to our needs. We have more than 100 users in our organization. We use the solution 24/7. We use it to its maximum potential.

It is very scalable. You can scale out as much as you want to the data platform as well as expand to other network platforms. We have seen some resellers or other vendors who are using Commvault as part of their service provider to back up their clients. In terms of scaling, they can use it to back up private data, public data, etc.

I would rate scalability a nine out of ten. It is very scalable.

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

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

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

The scalability is good and we plan to increase our usage of Commvault in the future.

It can probably improve on scalability. We have the typical Windows Server deployment. There can be easier automation when deploying new clients and agents.

The product is scalable. To scale, we need to buy more agents. We’re using HP hardware for HyperScale. We’ve three backup administrators working with the solution.

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

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.

It is very scalable. We started with hundreds, and now, we have got thousands of decoys. The only thing that you have to be careful about is the more decoys, the more alerts. Can you handle them, tune them, and get them cleaned up so that you are effectively looking at real alerts when they come in?

Once you have an appliance deployed somewhere, it's very scalable. It's pretty easy to deploy more traps. We have 14 different locations. So, we needed 14 different appliances that had to be configured, shipped out, and installed on the network. Generally, the product is pretty scalable, considering it has a physical deployment component.

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

The scalability is very good.

It seems very scalable. We have plans to increase our usage of the solution.

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.

We have hundreds of database backups, and Commvault has handled that well. If anything fails, they will send an email notification to notify you of what has failed.

We have customers with multiple petabytes of data. There is no issue with the scalability at all.

Commvault is the thought-leader in numerous trade organization reviews. They get top awards all the time based on the completeness of the solution and the ability to execute. For our customers, having that weight behind them and knowing that this isn't a company who was just thought up overnight or solving a single issue. They are looking at large enterprise-level issues with the ability to scale to the largest of enterprises as well as the smallest company. We have customers with one or two computers that they need to protect, and we're protecting them with Commvault. We're bringing that entire Commvault platform with the entire weight of Commvault behind it. Being able to offer that to a customer with one or two computers allows us to really use the entire suite of Commvault to help protect all our customers. That is one of the biggest benefits for us, having the entire weight of Commvault behind us as a service offering.

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.

It is a scalable solution. Currently, one of my customers has an almost one-petabyte backup solution. So, it was increased from gigabytes to petabytes. It can be increased if you have a big setup in place. With HyperScale Appliance, it is easy to expand the server. It will just expand your capability and the storage capacity, and a few other capacities in the solution. Scalability-wise, I rate the solution an eight out of ten. I have around fifteen big customers. There are a lot of customers of the solution who use it, with other vendors supporting it. The solution has quite a big market for the solution.

The solution is scalable so scalability is rated an eight out of ten. 

Scalability is very good.

There are no limitations for us. We are interested in indefinite backup for deleted files. Even if I delete the file, it'll be there permanently. I don't foresee any issue with that.

Our customer's environment is not that big, but it looks like it can easily handle a big environment.

We back up a little less than a thousand users, whom we are licensed for, and a lot of them are company employees. 

There are two sysadmins managing the solution. One of them mainly does the monitoring and getting the work on the system.

The 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 can easily expand our licenses and deploy Commvault for our customers, which keeps our business going. From a scalability point of view, I haven't seen many challenges.

The solution is scalable. It's a software-based solution so we just need a license to expand it.

I have Avamar servers that we have recently updated storage-wise and capacity-wise. So we don't have any immediate requirement to increase the licenses of Commvault.

The solution is pretty scalable. You can grow the environment. We have been using the same CommServe server for the solution for the three years that we have had Commvault, and we have just scaled and scaled the solution. We started with about 3,000 clients and now the number of clients has doubled or tripled.

HyperScale X, which was released one year ago, is more scalable than version 1.5. You can put more nodes in one cluster and, because of that, you can increase your overall storage.

We don't have the Commvault Activate solution. We are thinking about acquiring it in the near future to improve our environment. Our migration from other vendors to Commvault took between one and two years because our environment is so large. Right now we are fine-tuning the product and the processes around it. Perhaps we will use Commvault Activate starting next year. It will be in our scope.

At this point, there are no plans for increasing usage right now. We are reducing our footprint on-prem and we've moved everything to Azure. Unfortunately, we leveraged some of the native protocols from Azure side. Commvault has gotten reduced. Due to that change,  the pricing or licensing that supports the functionality of it may be impacted a little bit.

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.

The tool’s scalability is very high. It can be scaled in any environment. I rate the scalability a ten out of ten. In a single organization, we have 4000 to 6000 users. Our clients are enterprise businesses.

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

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

Metallic is a scalable solution. Its primary benefit is unlimited backup for endpoint users. However, not all clients purchase that. 

I rate Metallic 10 out of 10 for scalability. 

The solution is very scalable. I'd rate it ten out of ten in terms of the ability to extend.

Everyone uses the solution. We have 20 to 30 people using the product. That includes consultants. 

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

It is easily scalable. We have about 300 users of Commvault Complete Data Protection in our company.

This solution is scalable. In our company, we have two users of the product.

It is scalable. We have approximately 30 users, but we are also backing up the servers that everyone uses.

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.

HyperScale X's scalability is okay.

It is a good solution that can grow horizontally to a large number of nodes.

The scalability is great. It's very scalable.

Currently, I only have 10 endpoints that I'm protecting and I'm trying to roll it out to more. There are a lot of employees in our company. Right now, we're using Metallic for just critical systems, critical endpoints. I'm hoping to create more awareness throughout Parsons so that others learn about it and see it and, maybe, start using it. But for now, it's going slowly trying to get Metallic in through the door.

The Hyperscale scalability is very good. CV LiveSync is a great tool for protecting Commvault’s database.

There are two full-time engineers doing day-to-day administration of this solution. 

The product is currently in Phase I: VMware. We have plans to increase usage in Phase II: Exchange/Physical/Isilon.

Scalability is really good. We can scale out as much as we want.

Scalability was also not an issue. Every time we needed to scale the system for a customer, we could do it easily. On average, our clients are working with around 500 terabytes, and they're doing thousands of backup jobs on a daily basis.

We are increasing the capacity because we have an increase, on average, of about 20 percent a year. It's really scalable. With Commvault, you have a lot of possibilities. You can use your hardware or you can use dedicated hardware from Commvault. There are a lot of options for how you back up your environment. It's really good in this area.

The solution is scalable. 

Also, it is used by 380 users.

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

The scalability capabilities depends on which version you get. If you go to hyper-scale, it's infinitely scalable. If you go to an IBM object storage, it's scalable only up until a certain point.

We have approximately 50 people that have access to do restores. Ten of those having the additional responsibility of initiating backups for databases. And we have one engineer and two administrators.

We're considering going to the hyperscale version and then expanding it to have it distributed through three sites.

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

Scalability is very good. It can go very far with the number of media agents and its database. 

You have hyperscale possibilities, which is not something that I work with a lot. However, if necessary, you can also use the appliances to scale. 

For normal environments with servers and media agents, it is rather easy to scale. We sometimes start with small media agents using a physical server. We always have the possibility to extend it with more disks. It is easy for Commvault to scale the disk capacity.

We are looking into scalability because we're not yet using Commvault for the whole organization. The main limitation is the cost of implementing it at a lot of sites. Every year, we put it on our agenda to adopt it across Europe. We've selected some spots, but sometimes we've had to scrap a few because of the cost. However, soon we'll have the data we need for broader implementation. 

We have around 15 affiliates, including five big ones. Currently, it's running at two of those. Every national affiliate is responsible for its own budget, and it's up to them to decide if they want to spend the money on it. They have the built-in Snapshot technology from NetApp that they can use, with all its limitations, or they have the full-blown Commvault option, which needs investment first. Every year, we evaluate if we replace the NetApp Snapshot technology with Commvault. Quite often, there are other priorities.

But that hasn't stopped us because sometimes we use Turkey's Commvault to take backups from all those countries. So the scalability is excellent. It's easy because you just add the server, and it's up and running.

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

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

The solution is scalable. We have three to five customers using the tool.

It seems to be scalable. I'm not really involved in that side, being a user and not an administrator of it, but I know that they've had to add on and do upgrades to it. It seems to be working well. I haven't seen any disruption from that.

It seems like it has good scalability, which is another thing that I'm interested in because hopefully I won't be a small business for long. I've never run enterprise-level software, but I'm very happy with Metallic, as the owner of a small business.

As the business grows, as I add users, the ability to add backup features is there. It's something I've discussed with their customer support and tech support. I'm comfortable that as I add users and begin to use more features in my Office suite and elsewhere, Metallic will be able to provide backup. That's really the primary reason I have it: data backup and security.

I use it every day for the business. It's in OneDrive now but at some point I'm going to have employees and it will have to migrate over to SharePoint. I will then need it backed up in SharePoint as well for use by my team.

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.

We have grown our initial, on-premise VM-only backup solution to cover all three of our on-premise datacentres as well as our Azure IaaS and O365 environments. This was easy to do and the central management tool set easily coped with our rapid scaling up to our entire estate.

It is scalable. It is able to expand as needed. I'd rate the ability to scale at an eight or nine out of ten. 

In our company, we have about 100 people using the solution. 

The environment can scale nicely. It's got the ability to scale for multi-node clusters, but you need to ensure that you keep it updated.  

As it gets larger, it gets a lot more complex in terms of the configuration. Generally, the larger it gets, the harder it is to manage. We probably have about 1,000 servers right now that it is backing up.

Scaling can be done easily.

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

Commvault Complete Data Protection is scalable. My company was able to scale it when it had a media server problem, particularly storage issues.

The company quickly added disk libraries to the server, particularly disk expansion units. You can add additional media servers. It can be physical or virtual, or you can add a virtual machine from the cloud as a media server. Commvault Complete Data Protection is easy to scale.

The scalability of Commvault HyperScale X is very good.

The solution is scalable, and the entire organization is currently using this solution.

Commvault has tremendous scalability.

We do not have plans to increase the usage of the solution.

This product is scalable enough, although it will be complicated to do, depending on your environment. Veeam, for example, is not as complicated to scale. The same is true with Veritas NetBackup.

I think the reason for this is that Commvault is installed only in Windows environments. Veritas NetBackup, for example, can be installed on Unix or Linux, and those operating systems are easier when it comes to scaling. Most software depends on the features that are available in the host operating system.

The product can scale if a company needs it to. It does have the potential to expand as needed.

In our company, we have about 1,300 people using it.

The scalability of this solution is fine. It is much more scalable and flexible than everything else in the market. It is the one thing that they are good at. There is no doubt that they have simplified the licensing and purchasing model.

One of our enterprise-level customers for this solution is a very large telecom. They have lots of users. There are different databases and applications including Oracle, their ERP solution, Financial Suite, Greenplum, their CRM, filesharing services, and others. They also have a heterogeneous environment that includes Linux, Unix, Solaris, and Windows. There is also virtualization using VMware and Oracle virtual machines. Commvault is the only software that they have for performing backups, so they are one hundred percent reliant on it.

It is scalable. We are providing services for 30 to 45 customers in our organization.

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.

The solution is scalable, because you can add app features. It's very possible to scale.

We have four or five customers, so that's probably around 20 users. We are in a small country.

As we have used and scaled out the product SQL integration with the companies automated scripts proved to be a challenge. The Work Flow feature is your only solution and therefor you end up with a mix of scripts then relying on the products work flow to run and return expected results allowing your scripts to then continue. Not a very clean solution yet.

It is easily scalable. You may need to add a gateway, proxy, or media server to the environment before adding more data to the environment. 

Something that is not commonly used is that you can use Appian as a backup storage solution in one integrated package. 

We can scale the solution as we need to. The hardware supports any kind of storage. 

Everyone is using Commvault. It takes a backup of their endpoint devices, and mostly it's used by the admins to restore, schedule backups, and other things.

We have maybe 700 people on the solution right now. 

In terms of scalability, it is a skill level solution. You can scale up at any time by adding additional nodes.

The scalability is good, although we don't have plans to increase our usage of it.

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

The 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 four solution users in our organization. I rate its scalability a nine.

Commvault is scalable. We have about seven or eight engineers 

Scalability is great. In the new license model, I can scale it on the virtual environment. We are going to increase our Commvault center in our data center. The maintenance will increase. 

It is scalable. Commvault has recently changed the licensing. The licensing methodology makes things much easier and easy to scale up and scale out. Usually, the rate of technology they are accomplishing with other partnerships with vendors like Fujitsu is using the scale appliances which are massively scalable. 

We have more than 11 customers over here, and in total, there are around 400 users. Some of them are in the financial sector and the government sector.

The amount of people we require for maintenance depends on the project. If it's a medium project, then it's around five. 

Commvault is a scalable solution. At present, medium businesses work with the solution. I rate the scalability a nine out of ten. 

The tool is scalable. 

It's scalable. That's why it's HyperScale.

We have four administrators in our company who are managing the infrastructure. 

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

The issue of scalability isn't applicable to us because we're not trying to just grow, grow, grow. It's not that we're going to have 200 percent growth next year. Our environment is more or less stable. We have 800 servers. Next year we might have 850, but it's not doubling.

Pretty much everything we back up is done via Commvault, except for desktops or laptops.

The scalability is different between software and an appliance. If we use an appliance it is simple to scale because we just add more nodes to expand the storage, the compute, or the backup performance. If we use software, we may need to do some manual setup. Adding more media agents can be complex, involving more configuration. Also, you don't have high availability with a software environment. You only get that with an appliance.

Commvault's scalability is unmatched. Very few competitors have the scalability that Commvault offers. IBM and Veritas might come close, but there are no other solutions that can grow to accommodate enormous environments. So we have to rethink or mix up different backup solutions and technologies. With Commvault, you can do it for either large environments or medium-sized environments as well.

It's extremely scalable. It's used across the coalition control team and the cloud team, so there are a couple of dozen administrators. We are running a great deal more than that in the backend systems.

The new HyperScale solution from Commvault is a scale-out solution. We are not using it yet. One month ago, we did a book with the scale-out solution, so we do not have much experience with it. I expect a lot from it.

I have found the scalability of Metallic to be good.

I found the solution best suited for small businesses.

The solution seems compatible with almost every platform, including VM Hyper-V, and most databases, including SQL, MongoDB, and Postgres.

It's scalable. 

Commvault Complete Data Protection is scalable. We are using a socket-based license.

It is also scalable.

We have scaled out since our initial configuration. Our initial configuration was around 300 TB and now it's around 1.5 PB, if we measure it by backup size. If we measure it by servers, initially it was around 10 servers and now it's around 50. We have around 60 tenants. Some of them are smaller and some of them bigger.

Commvault is very scalable in terms of the data that Commvault can maintain.

The product can scale. If a company needs to expand it, it can do so. There shouldn't be any issues.

We might have about 150 users on the solution currently.

The scalability is good. 

No.

We are using VMware for virtualization every day. The issue with scalability that Commvault has is that any modifications in virtualization that we make have a direct impact on it.

We do not have a problem with scalability, but I think if we had to restore a large scale of information, it would be a problem because of the time we would have to spend restoring all of our virtual machines. However, we could backup as many as a 1,000 virtual machines very easily. 

It is easy to scale.

The solution is scalable.

I know that we can add nodes to the system, although I don't have much experience with scaling Commvault.

In my experience, the solution has been highly scalable.

We currently have approximately 30 customers that use Commvault Complete Data Protection. 

This solution is scalable, and we have more than 5,000 users that are using SAN services.

This is a scalable product.

We have been using it more frequently in the past three months, and we have ten companies as clients who are using it for their backups. I do not know how many users they have. We are planning to increase usage.

No.

We are happy with the scalability. We have 30 to 40 physical servers with 100 VMs. With this product, it is not about users, but about the amount of nodes utilized.

We will probably increase by two or three nodes in six months, depending on the requirements of our project.

Commvault scales great in a scale-up and scale-out manner. E.g., if your backup server (MediaAgent) isn't enough anymore, you can simply add another. Same goes for disk space and other resources.

In general, no. But some features like context indexing and searching have some limitations, which should be considered from the very beginning.

It is scalable, and it can grow up the environment.

No.