The scalability is excellent. We've regularly increased the capacity of Rubrik as we onboard new customers.

Between 30 and 40 people in the company probably use Rubrik, but that's obviously not every day because we have different staff on different rosters, and, being an MSP, we support multiple customers. From our side, we probably have a higher touchpoint of Rubrik given that we are supporting customers that are using it.

Like many other modern solutions, Rubrik is architected as a web-scale solution. This means that if you are running out of space, just stack another brick on top of the existing ones. You can stack bricks until a couple of racks are full. It is very easy. 

Scalability-wise, when we expand the cluster, it is non-destructive and non-disruptive. So, we can stack, and while it is stacking, we can still have backups running. Nobody notices that you are actually expanding.

We have active administrators of the Rubrik platform at this time.

They have everything available by API, which is a good thing because this is the way that things are going forward with an API-first infrastructure. In terms of their physical nodes you can also scale them, but there's a requirement of always increasing in sets of three more nodes. We have one Brik and four nodes currently, and to increase our storage we would have to buy three more nodes, which is kind of a limitation. It would have been nice if we could just buy one node and increase that way, gradually, instead of buying three large nodes. But I can't complain about it. That's probably their infrastructure.

We are using it for everything except our media storage. Our classroom recordings are directly archived to glacier and everything else goes through Rubrik. The reason for that is that we don't want on-premises storage of the media. These are large video recordings and it would be very expensive to store them locally. Rubrik keeps a local copy for three days, for regular backups. We are actually testing a new feature where you can connect to NAS storage and there will be no local data, only metadata, stored locally. Everything else is archived. We have tested this feature with their support. They showed it to us but we haven't acquired the license to start using it yet.

Only sys admins have access to Rubrik in our organization. Currently, 10 of our sys admins have access to the system. 

This is a well-designed product, so adding more space is as easy as adding another chassis. It is great functionality because adding more storage is like adding more bandwidth and more connectivity. That's a great design.

We are a fairly small organization, so probably five to six people have access, and there are probably three or four who use it. We centralize Rubrik to our IT systems and IT help desk, so it's all managed internally. There is enough flexibility to extend it to developers and give certain people rights to certain restores. It's just that the workload is so light that it doesn't make sense for us to constantly keep training users on how to operate it. By the time they need to perform a restore, they'll forget it all and have to come back to the help desk anyway.

If in the next version of Rubrik they announce new ways to back up Azure or Office 365, I would jump on the offer. The main driver for us to purchase additional Rubrik units would be if we were constrained on storage. As of right now, we have sized it correctly so we have plenty of storage to satisfy the SLAs for the data that they need to store in-house.

If our data consumption or data storage requirements increase, and we suddenly need more storage for data protection, we will look into adding units. At this point, we are properly sized for the performance.

We haven't had to do too much on the scalability front. However, the on-prem scalability makes sense. We are happy with it. We have currently an eight-node cluster on-prem, and if we needed to add more storage, we would essentially add another node or two to our cluster. So, we are happy with our options. We could scale from small to very large easily and with minimal configuration changes.

While I haven't personally added more nodes yet, based on documentation and feedback from others, the scalability seems virtually unlimited. Adding more storage is seamless and non-destructive.

This solution is highly scalable. You can add nodes as needed and expand the environment. There are no limitations to it in terms of hardware or Rubrik's support.

In order to expand, you would have to purchase licensing. Depending on the company's budget, that could be a limiting factor. As long as you can afford the licensing, if you grow then Rubrik can grow with you.

There are three of us in the company who use the product from a management standpoint. I am the system administrator, the CIO has access, and then the support tech has access to the system. I am responsible for maintaining it.

It is integrated 100% within our organization. We have no plans to do anything more with it because it's being used in every aspect of the business for backup and protection. We're fully invested and committed to it.

The scalability is wonderful. That is one of our biggest advantages with this. We can scale out as big or as small as we need to. We went with 20 nodes or so at the start and we've got over 40 now. We continue to expand as needed. We're still not all the way done with rolling this out to replace everything, but every year we're getting more and more nodes in there and replacing more and more.

We've covered about 85 percent of our environment. With the other 15 percent, it wasn't that Rubrik couldn't handle it, it's that the budget only allows for so many nodes to be purchased at a time. On top of that, we need to make sure that we do it in a way that's non-disruptive for work, and there are some teams that would be affected by disruption. We need to go a little bit at a time, which is what we've done. 

For the future, I do see us using it more. We have been doing a soft launch on Oracle, because we needed the tool that Rubrik has that allows for integration. That was still in something of an early stage of development, and we weren't comfortable putting it into production until it was in a more developed state. So we have used Rubrik to back up Oracle, but we've gone about using less of the automation pieces that Rubrik offers, and we're using it more as just a landing spot until that is fully developed. That's about the only piece that we're going to use more in the future.

So far, we've not had any issues at all. We have 16 nodes on one site, and we also have several virtual Rubriks where it's just a single instance. So, we have a range of different configurations, and all of them scale pretty decently.

We have about 10 users who use it directly. Its usage depends on the day. At times, it's heavily used, and at other times, it's not. It's a come and go thing.

We have not had to scale too far. We have six nodes at the moment and are capable of going to 32 nodes, if we need to. We don't really make use of that scalability, but I know other customers who do. I would be quite happy to scale it, if we need to.

There are six people who know how to use Rubrik at Cranfield. This is my systems team: cloud engineers and systems admins. 

Rubrik is a scalable solution. We have to do the sizing properly during the initial purchase so that there is no immediate requirement for expansion. We are using the solution in our data center. Only the admin has access to the solution, whereas all our enterprise server backups are on Rubrik. We have around 200 servers.

Based on strategies, we decide on future growth and monitor the dashboard to know if we are supposed to have additional nodes or expansions.

They sell hardware processing and discs, so if you want more disc space, you have to buy more processing. But I understand the model, so we're fine with it.

We have plans to increase usage because our company is growing.

We have not seen any limitation in the amount of data that we are backing up. Between two locations, we are backing up approximately 40 terabytes.

Since we're using Rubrik for backups, we don't have users logged into it. The solution is used by our IT support team, which has six to seven users.

I rate the solution an eight or nine out of ten for scalability.

It is definitely scalable. It is used to the extent of any other application in our production environment. We will definitely increase its usage.

Because this is a backup and restore application, only system administrators are the ones who schedule all the backups and do all the restores. There is also an option where you could give a user permission to do certain things. For example, we have DBAs who have access to restore databases. They cannot overwrite anything, but they can mount, and they can copy.

Scalability is very good. As your need for backup capacity increases, you just add more to the same cluster. So it's all managed from one interface. You don't need to manage each process separately. It's easy to scale up. And you can replicate to the outside. 

Our environment is about 150 terabytes.

Rubrik is a very scalable solution. The DBA and the server admin team, comprising approximately 15 employees, use the solution in our organization.

I rate Rubrik a nine out of ten for scalability.

My clients are mostly medium and enterprise-sized businesses.

Scalability-wise, I rate the solution an eight out of ten.

Because it's hyper-converged, we can just add additional Briks and nodes to give extra capability. We introduced an edge appliance to our setup. We installed it, added it to the cluster, and it picked up some of the workloads. It was so simple, a bit like Nutanix. The fact that it is all hyper-converged means the whole scaling piece is so much simpler compared to 3D architecture. It's just plug and go.

It's only within our IT department that there is access to the product. There are about a dozen people who can use it. But the services that we support help support the whole organization, whether it's HR, finance, or research data, or user file stores. It does touch everyone.

Scalability is pretty simple. We had initially started off with our two bricks in a replication pair, and then we needed to bring that replicated pair into the main system. I worked with support, decomm'ed the replication target, got that brick reset, and then brought it into the cluster. That took just a couple hours, but that included the fact that I had to physically move the box. But it was extremely simple and, once it was in, it operated just as you would have expected. All of the certificates copied over and I was able to contact all of the nodes exactly how I would've expected. It was pretty seamless.

Performance-wise, we might be using five or ten percent of the performance that's available through the system. After that initial ingest, you're only really copying changes, and most of our changes are relatively small in comparison to what the system can actually handle. 

In terms of features, we're only using five or ten percent of the features that are in the system. I was working on using some other features and then the need went away. It was taking a snapshot of a database and from one server and restoring it onto another server, but the need went away so I stopped working on that.

As new things come out, they move us forward. They just released a feature for the archives and cleaning them up. I must've missed it in one of the release notes, so when I ran across it I said to myself, "Oh, I better go in and enable this." Low and behold, it did exactly what we needed it to do and it saved us double digits of terabytes on our archive locations, which was great because we were running out of space. When they added the ability to link VM's between virtual centers, I enabled that one. As new features are released I'll implement them. There are quite a number of features, such as all of the integration with NetApp and Pure Storage, which I can't use because I don't have that storage. I can only use the features that make sense for us.

So far, so good.

Scalability has been a great process, as we have gone through a few at this point. Rubrik handles everything. They will come onsite, upgrade the units, ensure all is working properly and it typically only takes a couple of hours. That being said, we have deployments in multiple locations and they do not currently have a management hub that allows you to manage multiple clusters from a single place. You have to go cluster to cluster to make changes.

The solution is scalable, and it's straightforward to scale. We have around ten users, including database and server administrators, plus security staff. Most users have read-only access, and a few have write access too.

Scalability is not an issue. 

The ability to just attach additional bricks to scale-out capacity is great!

It is scalable, but you're just locked in because you have to buy a Rubrik device unless you go with the cloud.

There's another team that does maintenance. There are other products, so the team isn't just dedicated to Rubrik. We have about five individuals using Rubrik.

We are planning to increase usage. There are between a few hundred workloads to a thousand in IT. We're basically looking at cloud technology, so we're not actually using Rubrik.

It is highly scalable. We can easily add more VMs to our configurations or Rubrik account. It also can easily take snapshots.

In-house users are around 25 to 30 people who are mostly from the DevOps profile: software engineers, the infrastructure team and release managers. Developers are also involved.

Rubrik is scalable. We can manage multiple Rubrik appliances from a single console.

All of our IT infrastructure team are using Rubrik. We are using it in at our data centers in  India, and we have another  in the middle east. We have recently increased our usage of the solution.

It's very scalable. You're able to add additional controllers and also add storage on the file. It's also expanding their Polaris, which is their online software manageability portion. That, in their future release, will allow us to manage all of our Rubrik clients at all of our data centers which is excellent for scalability.

We have around 20 users. The majority of those are our database administrators. They are allowed access to database servers, so they can do their backups, manage backups, and recover backups. A handful of people in the U.S. and Canada are the backup administrators. The overall maintenance works on the machines to backup schedules and recovery.

For the maintenance, you can do it with as little as one person per site. We have five to 10 people for both Canada and U.S., which is five data centers.

My role is to design and implement this technology. Our systems administrators who manage the VMware environment would be the ones that would handle the day to day with the Rubrik backups and recovery.

We're in the process of replacing all the old backup technology with this. We're looking at roughly 300 virtual machines per data center. So we're looking at an environment that is probably 3000 virtual machines. The database count for all of those is probably in the hundreds. It's pretty significant. We have around a 65% adoption rate. 

I consider Rubrik scalable because all you need to do is add another Brik and it's seamless.

At this point we have adopted it 100 percent, so we do not have plans to increase its usage.

We have a lot of Rubrik, a lot of "bricks". If we needed more, we'd just buy more. The horizontal scaling is really great. I don't think we need anything immediately. But I could definitely imagine a moment in the past — not that I know that this happened — where we had ten nodes instead of the 50-something nodes we now have at each site, and we needed more and we put in more. I could totally see it all just working. It would just all of a sudden get better.

If we were ever pressed and at a point where we need something better, we needed more, I would imagine Rubrik would have a solution for us and it would work 100 percent. Whether that would be to PoC some new hardware and verify that it would actually improve our situation, or tweak a setting, or do a site survey to figure out what we're using and how to help, they would either get what we are using right now to work better, or they would figure out what we need to make it better moving forward.

That's scalability in a lot of ways. That's technical scalability in being consistent and stable and being able to improve and evolve. And that's stability and scalability and not having to plan your business processes around what should be a no-brainer issue. It's something that shouldn't drive your business. It should allow your business to be driven in whatever direction it needs to go. It should be something that just works, and so far I've seen it just works.

We have over 2,000 employees, and every one of those employees has some form of a computer and some have multiple: a laptop, or a laptop and a virtual machine, or just a virtual machine, or a laptop and two virtual machines. It's a big environment. We have hundreds of Windows Servers and about 100 Linux servers, if not more. We have pretty extensive Microsoft SQL environments which are either always-on clusters or a combination of always-on clusters and available clusters, and then we have some Oracle Databases as well.

I don't remember the exact number of what we're currently supporting in Rubrik, but I know it is a lot. We've integrated it in such a way — and this is a fairly normal process, but it's great — that whenever we put a machine online, part of the workflow is to get it to back up into Rubrik. Whenever we decommission things, it's to remove those backups 90 days after we remove the physical or virtual server. We keep backups X number of months after we remove the machine, just in case, depending on what our data retention policy is.

It's ingrained. We're invested. We made the jump.

No scalability issues.

The solution is scalable. 

It is scalable. We can add a node and scale it. 

In terms of its usage, it is used every day. Currently, we have only five users because we also have other solutions. We also have Dell EMC Avamar and Networker. 

No

The only issue we have run into is the sizing of the Virtual Edge devices. In retrospect, we sized incorrectly and ran into the limits of the virtual device. If we had setup a physical cluster, we would not have had any issues at all.

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

Rubrik is easy to scale.

We had a team of about seven users when we were working with Rubrik.

We have recently scaled the solution and it went well.

We have an administrator and people who do the restorations that use the solution.

Nope

It is a scalable platform. I rate its scalability a ten out of ten.

You can scale it. It is expensive, and it normally requires their support team's help because it is a physical brick. So, you usually connect another brick to it, and it scales out to that brick. So, it is easy to scale out. Scalability is not a problem. 

The scalability is also fantastic.

There have not been any scalability issues. This is one of the pluses and a driver for buying Rubrik. If you need backups to run faster, or if you need more storage, you just add another node or Brik.

I would rate the scalability of Rubrik as a nine out of ten.

Rubrik is highly scalable and is easy to do.

The process of increasing or scaling the solution is to add a new server, power on the server, tell the customer they have a new server and then everything gets rebalance on the new server. Increasing and decreasing is very fast and easy.

Rubrik is highly scalable, and the process is straightforward. Adding nodes is easy, even during network changes, with no downtime required.

I would rate the scalability as a three out of five because additional hardware is a must if in terms of infrastructure loads. In terms of archival functionality, the scalability is good because you can achieve that through cloud storage.

We have four Rubrik clusters with 41 DB in them. I would assume that we are backing up around 100 terabytes of data from the company.

We have three system administrators who handle the infrastructure side of the company.

No issues.

No scalability issues.

No, our biggest Rubrik cluster is 10 briks/20 nodes and we're still growing that pool.

We have not encountered any scalability issues. This is the best scalable backup device that we found in the market.

No. Add a brik and scale indefinitely. Scale-out to the cloud provides no fork lift upgrades and unlimited data retention.

Not at all.

No, if you need more space you can simply add a node.

The tool is scalable. We have more than 500 employees. We have only two administrators.

It is scalable.

Not at all, it's built to be scalable.

No issues with scalability. We have added two Briks to our environment with success.

I believe the solution can scale pretty well. I haven't actually tried it out at our organization, therefore, it's hard to say for sure.

There only a couple of admin personnel on the solution at our company.

Rubrik is scalable, and it can work for enterprises of any size. 

This is a scalable solution. We currently have a hundred servers using Rubrik.

We don't require any technical people for maintenance. When Rubrik was first establishing itself, we hired help for the first one or two times but the rest is so easy. The very first one, somebody has to do it, but for the second or third one, you can do it by yourself. It could be very good or very bad, depending on what you think. If you are trying to sell professional services, with Rubrik you are dead.

This solution is scalable.

The solution is very simple and easy to scale. It is extremely scalable.

The solution is highly scalable and reliable. We have a lot of users in the company, most are storage and backup admins. Not everyone has access to the backup system. 

The solution is scalable to multiple petabytes. Since we do not have that much data, the one which we are using is enough.

No. Rubrik is easily scalable when it comes to both capacity and performance.

It's able to be very scalable, either scaling up or scaling out.