We just raised a $30M Series A: Read our story

Rubrik OverviewUNIXBusinessApplication

Rubrik is #4 ranked solution in best Backup and Recovery Software. IT Central Station users give Rubrik an average rating of 10 out of 10. Rubrik is most commonly compared to Veeam Backup & Replication:Rubrik vs Veeam Backup & Replication. Rubrik is popular among the large enterprise segment, accounting for 75% of users researching this solution on IT Central Station. The top industry researching this solution are professionals from a computer software company, accounting for 29% of all views.
What is Rubrik?

Rubrik provides the industry's first Converged Data Management platform with the Rubrik r300 Series Hybrid Cloud Appliance, fusing enterprise-class data management with web-scale IT. Organizations use Rubrik to deliver live data access to recover from failures and accelerate application development. Our team has helped build products such as Google File System, Google Search, YouTube, Facebook Data Infrastructure, VMware Virtualization, Data Domain File System, and Amazon Infrastructure.

Rubrik Buyer's Guide

Download the Rubrik Buyer's Guide including reviews and more. Updated: November 2021

Rubrik Customers

Driscoll's, Red Hawk Casino, Davies Ward Phillips & Vineberg LLP, Wabash National, Chateau Ste. Michelle Wine Estates, Galliker Transport & Logistics

Rubrik Video

Pricing Advice

What users are saying about Rubrik pricing:
  • "You pay a premium for Rubrik, but you're getting a premium service that comes with immutable backups, instant recovery, and world-class support."
  • "The pricing and licensing of Rubrik is better than products that we've had in the past. It was quite a bit cheaper than Commvault and NetBackup."
  • "Rubrik was probably the most expensive solution but in the long run, it's justified by the value of the data that it protects."
  • "You need to understand what you're getting for the price. You are getting a backup solution, which is state of the art and works absolutely flawlessly. You are getting the storage needed to store your backups. You have all the sexy features that a modern backup solution can provide you, like deduplication, erasure coding, compression, fast execution time, secured data, and top-notch customer support. So, it might be expensive on paper. It's not free, but when you analyze what you are getting and the time you can spend on other stuff, then Rubrik is very cost-efficient."
  • "The pricing has been quite good from our perspective, in terms of being able to negotiate with the Rubrik team to get the product that we want and be able to sell that out to our end customers."

Rubrik Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
CB
System Administrator at a manufacturing company with 51-200 employees
Real User
Top 20
Easy to use with an intuitive web interface, helpful support, good performance, and saves us time

Pros and Cons

  • "The most valuable feature is the Instant Recovery, where we can restore a VM or SQL database or any server or application, and have it up and running on their appliance within a few seconds."
  • "They support Hyper-V and it works with our CloudOut, the cloud DR, but they seem to add features for VMware first and Hyper-V gets added second or sometimes several releases after the VMware feature comes out."

What is our primary use case?

Our primary use case is on-premises backup and cloud DR. We're using the Rubrik appliance with their CDM technology for our on-premises solution. We are also using their CloudOut technology to leverage their cloud DR as part of their offering.

We're backing up Windows infrastructure and on-premises applications such as SQL and Exchange file servers, and we're storing that locally on their appliance. Then, we replicate our environment to the cloud so that in the event of a true disaster, where we lost our physical infrastructure, we'd be able to spin up in the cloud, using their CloudOut technology. This would allow us to be up and running in the cloud until we were able to get infrastructure back online.

The environments that we are backing up are physical and virtual. We don't have any cloud-native environments, so we're not doing any cloud backups right now. We use the cloud, although it is a DR target. Our main task is VM backup, which is between 75% and 80%. We have a few physical boxes that we're backing up, as well. For example, I have the actual hypervisors to back up, and then a few miscellaneous other servers that haven't been virtualized.

The applications and servers that we protect include Microsoft Hyper-V for our virtualized infrastructure, Microsoft SQL server for the SQL side, and all of the other infrastructure, in terms of applications, that is Windows-based. We are very invested in the Microsoft platform and using Rubrik to back all aspects of that up. We do have a couple of Linux-based services running, but I would say that we're 95% Windows-based, whether that's Hyper-V VMs or Microsoft SQL, or Microsoft file servers or IAS app servers. 

How has it helped my organization?

One of the ways that Rubrik has improved the way our organization functions is time savings. Coming off of the backup solution we had before, we were spending several hours a week, every day sometimes, dealing with backups that fail. Other issues include trying to make space or deal with an archive target that was offline. We were just spending a lot of time on it.

Being a smaller team, when we spend time just dealing with the backups, that takes away from us being able to work on other projects that support the business growth and support other functions within the organization. With Rubrik, there'll be weeks sometimes that I never log into it. Maybe two, three weeks at a time, I never log into Rubrik because we get email alerts and they have great error handling. If there's an error or something happens, we get an email.

A lot of times, the appliance will take care of itself and then deal with that missed backup, or whatever happened. But that's very rare. It'll go for several months without having an error. A lot of times, the errors are not a Rubrik issue. It's always that Windows did something that caused the backup to fail and Rubrik reruns it, then it works.

Not having to spend any time in the console because we can rely on the alerting and automated reporting has allowed us to focus on other areas of the business and not deal with backups. Essentially, it gives us peace of mind that Rubrik works. It was definitely a change to get used to, not logging in to it. We buy this really cool piece of technology and turns out that we're not in it a whole lot, but that just goes to show Rubrik has a robust solution that we can depend on.

This product has definitely increased productivity because we're not dealing with backups. They work on their own and it does its thing. We made the investment into Rubrik to not have to deal with backups and it delivers on that. This leaves us time to focus on other things because we're not dealing with a backup that failed.

It is difficult to put an exact number on the amount of time that we're saving by using Rubrik, although, with our previous solution, there were weeks where we had to spend several hours dealing with failed backups. On a bad week, it may have been between six and eight hours. On average, by not dealing with backups at all, we are saving several hours a week.

Using the SLA-based policy automation has simplified our data protection operations. We are no longer scheduling backups or trying to figure out availability, or time slots, where we can back up our systems. For example, we don't have to consider things like we've got backups running at 1:00 AM, 2:00 AM, or 3:00 AM, and we're trying to find a slot. Instead, the SLA engine that they have is super easy to use and does that job for us.

It was really good for us to move to the SLA-based approach from a traditional backup because we were able to, for business use, cover tasks such as retaining email for one year. In their SLA engine, it's very easy to find that. Another example might be backing up a set of test-SQL servers where we only need 14 days. Through the policy engine, you set what you want the retention to be and it takes care of scheduling and managing those backups.

Once we have them set, they are stable and continue to work because we don't change SLAs often. We define the retention that we need for each app and each service, and then it just works. Overall, the SLA-based approach makes it very easy to achieve your backups.

Luckily, we have not used their ransomware recovery. We've not had any incidents or ransomware where we needed to, but we have tested recovering assets in the event that happens and we've always been able to recover in our test scenarios, in our tabletop exercises. This is the type of feature that you never want to rely on outside of testing because it means that you're having a bad day, so hopefully, we never have to use it. That said, if we do have to, we're confident that it would deliver.

Similar to the case with ransomware, we have been lucky in that we haven't had any major disasters where we had to fully recover anything. In the usual case, where files are lost because something is overwritten, or something gets deleted, it has definitely saved a lot of time with the instant recovery.

Using the predictive file search, we're able to put those files or directories back or roll back a database in a few minutes. It's very quick and has definitely reduced our recovery time. We've not had to do a lot of restores, but when we do have to restore the occasional file or put a database version back, it's very quick and has saved us quite a bit of time from what the old Unitrends system would have looked like.

This product has also saved us time with respect to managing backups. Prior to Rubrik, every day of the week, we were spending an hour or two hours or sometimes longer dealing with backups, and that's now completely gone. There are some times that we go for weeks and don't even log into the appliance because we get the reports and they tell us everything we need. We trust Rubrik because we've had it long enough now that we know that when it says it completed the backup, the backup's there, and if we need it, we can get it back.

What is most valuable?

The most valuable feature is the Instant Recovery, where we can restore a VM or SQL database or any server or application, and have it up and running on their appliance within a few seconds. The recovery time of the instant restore is instantaneous and there is no complexity to it. What we're recovering doesn't matter to them, and we don't have to wait for it to mount a recovery image or do anything like that. When they say instant, they mean instant.

The ease of use is important to us, as well. It's super easy to get set up. Within a few hours of them deploying the on-premises appliance, we were backing up data locally into the cloud and able to test restores.

Rubrik is really good about releasing updates and we have had no issues with the process. They make it very easy, working with their support when they do put out an update, and they assist with doing the health checks beforehand to ensure that there are no issues. They do a pre-flight check on those updates to ensure that they're compatible with the appliance. Then, we schedule a time off-hours to apply it. They are normally pretty quick and we've never had issues where we had to roll back. They've always been flawless updates.

The CloudOut technology allows us to replicate data in our environment to the cloud, and then it can be spun up and used in the cloud if our physical environment is not available.

The VM backup and the SQL backup are blazingly fast for both backup and recovery.

The web interface is really good. and it's only gotten better with every update. It was good, to begin with, but they've improved the speed and added features in each update. It is a modern interface that works in any browser, and we can get to it from a tablet or computer. The type of device you access it from doesn't matter because it fits all screens, and it's intuitive and easy to use.

The archival functionality is very good. It is very easy to archive data to the cloud, and this is something that we were looking for. You can do it all from their web interface, which is a plus. You don't have to jump into the command-line interface or run scripts or anything to make it work. It is all configurable in the UI and very easy to dump data off to the cloud and pull backups back from the cloud archives.

We have used the predictive search functionality and hands down, it's the easiest way that I've ever recovered files. It's just like searching Google, but it searches your own files for recovery. It's easier than if you told somebody you could use a Google-like search to recover files, I don't think they would believe you until they've used Rubrik, because it does work that well. It's quick to search, no matter if you're searching a VM or even a physical box, it works across them.

With their new global file search in the latest version of their CDM, you don't even have to know what host that file was on. You can just type in a file name or a part of the file name and it'll find it. When a user comes and says, "We lost the file and it was called something like this," with any other solution, I don't know how you would find it. I think it would take a lot of work. With Rubrik, within a few seconds, you have file results. It's a pretty great feature.

What needs improvement?

We would like to see more support for Hyper-V. They support Hyper-V and it works with our CloudOut, the cloud DR, but they seem to add features for VMware first and Hyper-V gets added second or sometimes several releases after the VMware feature comes out. Seeing more support for Hyper-V would be a plus.

For how long have I used the solution?

We have been using Rubrik for about a year and a half.

What do I think about the stability of the solution?

This solution is very stable, dependable, and reliable. We've had it for a year and a half and nothing has ever happened with the appliance, or come up where we'd think differently.

Their updates have been really good and we've never had an issue after applying an update where something didn't work.

Knowing that Rubrik has built a robust platform, which is what we're dependent on, gives us peace of mind.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

The vendor has world-class support, and some of the best support we have for our solutions. Rubrik support has been great to work with when we do have to work with them, which isn't often.

Which solution did I use previously and why did I switch?

Prior to Rubrik, we were using the Unitrends solution for our backup. We switched because we couldn't depend on the Unitrends product. It was missing backups, for example. There were some times where every day, every week, five days a week, we'd spend a couple of hours a day, or maybe an hour a day, in Unitrends trying to get backups to run because they would miss a whole set of SQL servers or miss VMs.

We also couldn't do cloud archiving with it. It just wasn't capable of that.

I think we had outgrown the Unitrends solution. I think Unitrends is great for a small company, but anything small to medium and larger, Unitrends just isn't a good solution.

It seems like a very traditional backup solution. It's not forward-thinking and innovative and new like Rubrik is. So, we just knew that we needed something that we could depend on because, with Unitrends, we knew that if there was a disaster, we couldn't recover and so that's why we started looking at something else. We were very happy when we found Rubrik. It restored the peace of mind that we didn't have with Unitrends.

How was the initial setup?

The initial setup is straightforward. Rubrik sends out a technical engineer when you get the appliance to help you get it online. Within a couple of hours of them being on-site, we were backing up data locally, as well as to the cloud. By the time they left, we had tested restores and our environment was backing up locally and into the cloud.

We did not have an implementation strategy and just followed Rubrik's guidance on how to implement it. They had a plan that was based on information that we provided them about our environment. That way, when they were on-site, we maximized our time with them to get it deployed. We really just trusted Rubrik with it.

What about the implementation team?

There were two people from our company and one person from Rubrik involved with the deployment. I was on the technical implementation side, and our CIO was involved in the purchasing, decision-making, and ultimate sign-off on the solution.

The deployment was handled by Rubrik's technical support engineer, who is assigned to you during the sales process. They are somebody local, in fact. They are based in Iowa where we are.

You work with them through the whole sales process and then they help you get the appliance set up and then they're even your contact even after it gets set up. This means that if you ever have questions or you need assistance, they're the person to help and they're very knowledgeable. Our engineer was able to answer any questions we had.

What was our ROI?

In the sense that we're not spending IT resources on managing the solution, that's really been the return on investment.

What's my experience with pricing, setup cost, and licensing?

Rubrik is definitely a premium solution, but if you can afford it and put it in your budget, they're definitely the way to go. They're not the cheapest solution on the block and I don't think they would tell you that they are. You pay a premium for Rubrik, but you're getting a premium service that comes with immutable backups, instant recovery, and world-class support. It's well worth the investment into Rubrik.

In the subscription, they have an appliance renewal program, and the maintenance is set up so that you know, upfront, what the potential increase is. They give you a range.

Which other solutions did I evaluate?

Before choosing Rubrik, we evaluated other solutions including Dell Avamar, which is their data protection solution. We also looked at Cohesity and with respect to Unitrends, we knew that they were out, so we didn't re-evaluate the product.

The results of our evaluation showed that Rubrik really outperformed the others, with just their support of Hyper-V. They all seem to support Hyper-V to some extent, but Rubrik seemed to have the best support for it at the time.

The speed of Rubrik and the ease of use also stood out, compared to the others.

The Dell solution was very much a traditional backup system and we wanted to get away from that. We wanted to go to something that was cloud-ready for archive and DR. We also wanted a product with great support for virtual machines because that's where our infrastructure was going. We just didn't get that feeling with the Dell solution. I'm sure that it is a great product and they probably sell a lot of it, but it wasn't the new solution we were looking for.

Then with Cohesity, we just didn't see it as a good fit. Overall, Rubrik just looked better and fit our needs better. We had to consider the infrastructure and the workloads we were protecting, as well as the features that we were looking for in terms of the easy backup and the immutable backup protection for ransomware, the CloudOut, and cloud DR technology. It all just was a little bit better in Rubrik and just beat out Cohesity.

We are heavily virtualized and have lots of SQL as well, which is why we picked Rubrik. These are two things that they are very good at.

They're definitely a forward-thinking and future-thinking company in terms of offering their VM backup and their SQL backup, so they really shine over the competitors we looked at.

What other advice do I have?

Although the updates are really good, we are a little bit behind for some compliance reasons. However, we have access to all their features and we try to stay as current as possible. We're on almost the latest version.

My advice for anybody who is considering this product is that it's a world-class solution. If you want peace of mind at night, immutable backups, cloud-native support, cloud DR support, all within a single solution with world-class technical support, Rubrik is the way to go. If you can afford it, you're getting the best. You're getting a premium solution and everything that they say they can do, they can do. They can prove it to you or customers can prove it. They've never oversold on what they can offer.

My biggest takeaway is that it's a good investment in your backups. It's not the cheapest solution, but the investment you're making protects your business and ensures that if you ever need your backups, they're going to work. You can trust Rubrik.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
RJ
Storage Administrator at a healthcare company with 5,001-10,000 employees
Real User
Top 20
Cut our backup management time significantly, and near-instant recovery reduces our downtime

Pros and Cons

  • "We do like the instant recovery... Now, we say, "Okay, give me 15 seconds and I can get this back up for you." And within that 15 seconds it's on and the only thing that we have to do afterwards is vMotion it off of the Rubrik storage back to where it should rest."
  • "The interface is still slightly clunky and has room for improvement. They do work with us whenever we mention anything that needs to be done or anything that we want. We find that bringing up the management interface is a little slow and not as intuitive as we would like, but it's been getting better as it evolves."

What is our primary use case?

We came from two different systems. We had one product that was for our campus side and a different product for the hospital side. We wanted to bring those together and not have too many products in one environment. Rubrik covers everything in our VMware, for both campus and hospital. It does all of our backups. Anything that gets backed up for either side now goes through it.

We were siloed out into many different teams on both sides and we had a backup team on campus and a backup team on the hospital side. When those were brought together, the backup teams were dissolved and they were put into the VMware side where they're now managing hardware and server hardware refreshes.

My team is now the storage and backup team and we've taken on that task. Backups are offered as part of pretty much any ticket requesting a new server, for campus or hospital, that is a request for a new server. We spin up the backup at the server creation.

Our Rubrik is all on-prem. We back up our VMware environment and we also do a few physicals. We do some SQL and we do some Oracle.

How has it helped my organization?

It depends on what we're recovering, but some recoveries, before Rubrik, would take 30 minutes-plus. Now, similar recoveries that we've done have taken only seconds.

Also, when we first put this into place, we were actually moving to a hybrid cloud approach as well. We were trying to offer server creation as a simple ticket. We were doing this through offering the products, the catalog, and the automation behind everything to spin up the servers and deal out the storage. The two products that we actually have in our environment weren't very friendly with that automation piece but Rubrik, with its SLA policies, makes it very easy for us to say, "Hey, if this is a tier-zero application, we want this SLA applied globally," although there aren't very many of those in our environment. And if it's a tier-one application we can say, "Oh, we want this SLA applied." It does a very good job of keeping things clean in our environment. We also went through making sure we have everything tagged in VMware so that Rubrik can just pull that tag and apply that SLA. So things work pretty smoothly with all of that together.

We use the archival functionality. We tend to keep things on a Brik for a certain amount of time and, of course, it's a larger amount of time for tier-zero applications. And then we archive off to a private cloud that we have here at the university. That definitely keeps costs down because we have a deep and cheap storage solution for that cloud, Hitachi Content Platform. That was one of the main reasons that we went with Rubrik, as well, as it is compatible with HCP. We have quite a few petabytes of that and we wanted to make sure that we could leverage that and use it to our advantage.

Another benefit has been that management time has gone down significantly. Before, we had those two teams, one team for NetBackup and one team for Commvault. Each of those teams had two people on them. Now, we have one person on the storage team who is dedicated pretty much to backups, and the rest of us jump in as needed. We've really been able to consolidate that effort, and since it's an easy to use interface, we were able to pick up and run with that as a storage team. But with NetBackup before, we did have to build out quite a few servers and other stuff to get it into HCP. The whole model behind that, having lots of media servers, was very costly when you add in all of the hardware costs, licensing, et cetera. With this, it's quite a bit cheaper.

And Rubrik has definitely reduced downtime, because if we can spin up a recovery faster to that local CPU and the storage of Rubrik and have it up instantly, we can definitely get back to work sooner.

What is most valuable?

We do like the instant recovery because, beforehand, we would tell people, "Hey, it's going to take anywhere from 30 minutes to an hour to spin this up and, in that time, we're going to need your help with certain questions." We would sit there and work with them, but it always took quite a while. Now, we say, "Okay, give me 15 seconds and I can get this back up for you." And within that 15 seconds it's on and the only thing that we have to do afterwards is vMotion it off of the Rubrik storage back to where it should rest.

We also like the web interface. We mainly log in to the node and work from that, but occasionally we will log in and look at things when offsite. It's very intuitive and it works really well.

In addition, the solution's APIs play in with our automation piece for hybrid cloud. We wanted everything to work without manual interaction. We wanted everything to just play through when a ticket is submitted and automatically spin up the backup that we wanted, based on the tag in the VMware object. Our VMware team was the one that mainly looked at those APIs and built all of that out, but they haven't had any issues with it. It's worked exactly as designed.

What needs improvement?

The interface is still slightly clunky and has room for improvement. They do work with us whenever we mention anything that needs to be done or anything that we want. We find that bringing up the management interface is a little slow and not as intuitive as we would like, but it's been getting better as it evolves.

Rubrik is a somewhat new company, so it needs to become a little more established, and that just comes with time. It's not really too much of a concern or a weakness. It's just something that hasn't happened yet.

For how long have I used the solution?

We've been using Rubrik for about a year and a half to two years now.

What do I think about the stability of the solution?

The stability has been good. We don't run into a ton of issues on it.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

When we have run into issues, we've reached out to our support team at Rubrik and they've been very quick to respond. Whether they're in the office or not, they do take our calls and help us out. It's always a quick response.

They're a newer company, so I'm sure they're still establishing their place, but the escalation teams and everybody that we've worked with have been capable and they've been able to fix our problems without having to bring in too many people.

Which solution did I use previously and why did I switch?

We had Commvault and NetBackup before. Both of those were based on costly consumption-based licenses, and our CIO really disliked that model. The licenses that we had had been increasing in cost year after year and it just wasn't feasible to keep two separate products that weren't a good fit for the automation piece, for hybrid cloud. And they were on a slightly more pricey model. So rather than going to one or the other, we went out to see if there was anything that made more sense at the time. And that's when we found Rubrik.

With Rubrik, we have an agreement where it isn't license-based, and we are able to add more Briks as needed and more clusters as needed. It makes it extremely easy to expand our backup environment as the need arises.

With the other models out there, you would buy one quota and then you would hit it and prices would change and other things would happen. They have you locked in, no matter what. It was basically a situation where you had to pay whatever price they said you had to pay. With Rubrik, it's been very nice to have all of the equipment in our own data center and to have a little bit more control. For example, if we think we're going to need this much next year, this is what the hardware cost is going to be, and we can pay for any additional capacity that we need. That's been really nice with Rubrik.

How was the initial setup?

Setting up Rubrik was both a little bit straightforward and a little bit of complex. We had the team that sold us the product there with us during setup and we went to add in all of the nodes at the same time. That was something that even that team had thought we could do, and then they remembered, in the middle of adding all the nodes at the same time, that we needed to do it in groups. That does take time. We were putting in something like 16 or 20 nodes, and we had to do it four-at-a-time. We had already done the physical installation and all the cabling, and all that portion. But when we started to add in the nodes, we had to do four and then wait for it to finish on that, and then do another four and wait for it to finish on that.

I think that, with time, they may implement a system that cues them up and continues to add nodes as it can. But that seems to be a similar problem to what occurs with other products in the same category. We also have Cohesity in our environment, which we don't use as a backup product, we use it strictly as a NAS, and it suffers from that same issue.

Our Rubrik setup took a few days, between our getting network issues figured out on our side, getting all of the cable management figured out with our data center team, the physical installs, the configuration with the Rubrik partners, and then adding in those nodes four-at-a-time until we had them all in.

We could have done it with less staff but we did want to make sure that all of us were aware of how the implementation worked, so we brought in all five of our team, two Rubrik partners, and two of our reseller partners, as well.

For maintenance of Rubrik we require two to three people. One works on Rubrik pretty much all the time, and the other four of us just jump in as needed on little things here and there.

In terms of Rubrik users, in addition to the five of us who do administration, we've given out access to a few of our database groups, so far, where there are 10 to 15 people.

What about the implementation team?

Our reseller was ASG at that time, now it's Sirius. Everything was fine with them. On the Rubrik side, we had an engineer and a sales engineer, and that worked really well.

What was our ROI?

With Rubrik, we have been able to allocate FTEs to the other areas. We could have eliminated them but we chose to reallocate them. As we've had people either retire or move on to something different, we've either not replaced some, or we've been able to replace some of them with lower-level staff, simply because of the ease of use of this product.

On the hospital side, the ROI is from the lower cost, less work to manage it, and the smaller footprint in the data center, which means less power and cooling.

What's my experience with pricing, setup cost, and licensing?

The pricing and licensing of Rubrik is better than products that we've had in the past. It was quite a bit cheaper than Commvault and NetBackup.

Which other solutions did I evaluate?

We actually reached out with our VAR and we evaluated anybody that could use the HCP that we have for archive storage. There weren't too many on the market that could do that. Rubrik was really the only solid option that we had at the time, other than Commvault and NetBackup. We weren't too happy with the latter two because of how much they were costing at that time.

What other advice do I have?

We did physical PoCs in our environment and we did have Cohesity and Rubrik side-by-side, as well as NetBackup and Commvault. We did PoCs for moving to public cloud as well, for some of these services. The PoC with Rubrik stood out. 

Make sure that you work with your support team that's going to support you after your purchase and make sure that you're able to work with them well, before you pull the trigger on it. We like to build partnerships. When we have those partnerships, we're able to really rely on them for a long time.

I am a fairly new entry into the backup field. Before, we had Commvault and NetBackup, and when they were showing us how to use those, and trying to teach us some of the terms in the backup world, it felt like backup was a very niche piece of IT, and that there was a lingo and a language behind it. It seemed that there were definite things that people had experienced before that were common among all backup products, and things that they were left wanting or hating. With this new product, Rubrik, we walked into it blind, not being backup admins, and it made a lot of sense to us. And when we did bring in a backup admin, they said it was quite different to anything that they had worked on previously, and that it made more sense and that it was just quite a bit easier to manage.

Rubrik is something that everybody can understand fairly easily, and when we have given others access to it, such as the database teams, and we've let them run with it and see what they can do, they've been able to implement it really well. They've been able to figure out how to implement the tool in exactly the way that they wanted, whereas before there may have been limitations.

We haven't used the ransomware recovery at this point. We've got some protection behind that, where they are locked down and require additional effort to delete and to change. We follow guidelines from our IT security team and Rubrik together. We just haven't seen a scenario yet where we've actually needed to use that.

We have used Rubrik's predictive search, although we don't use it too much right now. Mainly, the way that we've used it so far has been the traditional backup and restore, where we get tickets stating that a backup needs to be spun up and it's done automatically. Then, when somebody comes back later on and says, "Hey, we need this item restored," we're able to call them up and restore it with them on the phone, within a matter of minutes. We haven't really had to use the file search too much or a lot of the tools that they have available for us, just because the need hasn't been there yet.

When it comes to recovery, we usually spin it up and turn it over to the team that asked us to recover that data. The information and identity access management team had to spin one up recently. They said that they had a bad patch and wanted us to spin back to that morning. We did that, and it had lost some of the network settings and some of that stuff that they were used to getting. We spent about 15 to 30 minutes with them and everything was back exactly the way that it should be. But that was pretty much exactly the same with other products that we had so it wasn't something new for us.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Learn what your peers think about Rubrik. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
552,136 professionals have used our research since 2012.
BurhanShakil
Systems Engineer at Harvard University
Real User
Top 5
Automates most of our backup workflow, automatically adding VMs and assigning the SLA, and provides instant recovery

Pros and Cons

  • "There is a live-restore feature, their Live Mount, and the way it works we can instantly recover a VM, a past backup, to be directly attached to our VMware environment. Rubrik will act as a disk for it. It's like an instant restore. Within a few minutes our VM is up and running. And then, if we want to restore it, we can just migrate it to our actual storage."
  • "Capacity reports could definitely be improved. It's hard to determine what is using the space and why. For instance, you can see that some host is using 2 TB on the Rubrik node and the disk space on that host is 400 GBs. It's hard to explain how there can be 2 TBs of data on local storage when nothing has changed on the host for the past three days."

What is our primary use case?

This is our main backup system. All of our VMs, our hardware hosts; everything is backed up using Rubrik.

Disaster recovery is one of the options we have explored, so that in case of a big disaster we could utilize their image conversion to run our VMs on AWS, but that is just a proof of concept at this stage. We have tested it. It works. But we don't have a proper plan in place for that.

We have only one physical server that we are protecting with it and the rest are all virtual servers. We have around 400 server VMs and all of them are protected using Rubrik. Most of our environment, around 90 percent, is VMware, while 10 percent of our environment is Hyper-V. 

With the VMs we are also taking backups of our CIFS shares. We have our file clusters running Windows Servers so we are taking backups using the SMB mount. We have NFS clusters as well, for the Linux side, which we're backing up using the built-in NFS connectors. We explored SQL backups, but right now we are using our SQL Server to dump the data and then the files are being backed up. We're not directly backing up SQL using Rubrik.

How has it helped my organization?

The SLA-based policy automation has had a very good effect on our data protection operations. We came from Commvault and we used to have tape backups. It was a full-time job for one of our sys admins to update the tape library, replace the tape cartridges, recycle them, scratch them, and then bring them back. It was a huge process. We were using offsite storage to store our tape backups which were continuously going back and forth from our campus. Now it's all automated. We barely have to manage anything. We are now consumers instead of actually setting this up. It was one set up and we just maintain it now.

It saves us time when it comes to managing backups because we barely do anything, other than just verify. We get a daily report to see if any of the VMs are out of our SLA. The only action item we have, if something is out of SLA, is to verify what happened, why the backup failed or missed its window. Given that it was tape before, it has gone from hours to minutes. It used to be more proactive, where we were continuously checking everything and replacing the tapes and making sure that everything went through. Now, it's more of a reactive situation, where we only look at a backup when there is an issue.

It has also definitely reduced the time we spend on recovery testing, because it can do Live Mounts and that does not require an actual recovery. So our VMs are instantly available. And the file restore feature allows us to explore the file system of every VM, instead of restoring it, and then just restore the files that we need, and that has been amazing so far as well. Within a few minutes, we have either the VM or the files available. I don't even know how to compare it to Commvault and the tape backups. When I joined Harvard, they already were on Rubrik and we were decommissioning Commvault, so I know a little bit about the process. We do classroom recordings in Harvard Law School and those were still going to Commvault. That was the last project that I was involved in and I saw the crazy amount of work involved where we had to bring all the tape libraries from safe.

And when it comes to recovery time itself, it's an instant recovery in most circumstances, even if we have to recover something that's more than three days old. In our environment, after something is more than three days old it goes to an archival location on S3. When we restore data that is between three and 42 days old it is downloaded from S3 and then made available. For us, that situation is a little bit slower compared to the Live Mount. Depending on the size of the VM, it could range between a few minutes to a few hours. But if the data is on premises, it downloads the data instantly.

We don't have to worry about the solution too much, which definitely has helped our productivity. Most of our workflow is automated, where VMs are automatically added. The SLA is automatically assigned. Things are automatically archived. Anyone can take action. We have on-call people who look at the reports and take action as needed.

What is most valuable?

There is a live-restore feature, their Live Mount, and the way it works we can instantly recover a VM, a past backup, to be directly attached to our VMware environment. Rubrik will act as a disk for it. It's like an instant restore. Within a few minutes our VM is up and running. And then, if we want to restore it, we can just migrate it to our actual storage.

Rubrik's web interface is very simple to use. We have a very simple SLA configured so that everything is backed up every day. Any new VMs we configure in our environment automatically get added, the SLA is automatically assigned to them. All the VMs, after three days, are archived to AWS S3, and then there's a life cycle on the AWS side to work with that.

The archival functionality is one of the main features because the Rubrik that we have has about 60 or 70 TB of total local storage, which is definitely not enough for our data. We have around 140 TB of data stored on AWS and, without the archival feature, we would have to buy at least three times the number of nodes that we currently have to keep all the data secure for 42 days, based on our SLA. It's definitely saving us on costs. It also gets us away from having to keep redundancy on the data, because if we were storing it on-premises we would have to make sure that we have redundancy and offsite storage. Now, all of that is AWS. We no longer have to worry about that.

What needs improvement?

Capacity reports could definitely be improved. It's hard to determine what is using the space and why. For instance, you can see that some host is using 2 TB on the Rubrik node and the disk space on that host is 400 GBs. It's hard to explain how there can be 2 TBs of data on local storage when nothing has changed on the host for the past three days. 

They have improved a lot on the SLA reports. We used to get a lot of false alerts before, because a snapshot was missed. In the reports it would remain a "non-compliant to an SLA for 42 days, until the 42 cycles were done. They've removed that. If it misses an SLA and if you take another snapshot or to take an automatic backup, it automatically fixes the SLA report to show us it's protected.

Most of their documentation for cloud stuff can be improved. This could be old information, as we did the PoC last year and maybe their documentation has been updated now, but we literally had to contact support every day, and at every step for things like, "Okay, what do we do with the AMIs? How do we get Rubrik configured? How do we convert the image?" None of that was available in a single documentation format. It was spread around in different documentation.

For how long have I used the solution?

I've been using Rubrik for the past three years, since I joined Harvard, but I think it was deployed on-premises four or five years back.

What do I think about the stability of the solution?

It's very stable. We have had an instance where one of the nodes was offline for no reason, but working with their support it was determined that there was a cache issue and they fixed it.

We don't have to worry about backups. We have been using it for more than four years and so far there hasn't been a single incident where we have had any issues recovering any of the files or VMs. It is very robust, continuously updating.

What do I think about the scalability of the solution?

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. 

How are customer service and technical support?

Rubrik support is amazing. When we are involved in upgrades we always open a ticket and there is a tech person joined through a tunnel and looking at the upgrade while it's being done. It's like everything is off our shoulders in terms of managing it. If something goes wrong, they're always available to support us.

Every time we've opened a ticket with them, even to explore new features, we have always gotten an instant response, and even when it comes to trial licenses. The whole proof of concept project we did on AWS for DR was provided from their support, and it has been amazing. The experience has been really good.

Most of the time, their turnaround time for tickets is less than 24 hours, especially with high-priority tickets. Recently, we have had some issues with our VM storage sizes not reflected properly. We were looking at a capacity report and we were seeing some of the VMs using way more storage on Rubrik than they should. This has been a difficult problem and they have continued to escalate it to different engineers. That is the longest interaction we have had and the issue is still pending.

We are not running the bleeding edge, so there is a possibility that if we do switch to 5.2 we might see an improvement already on that deduplication; that might be the reason that this is happening. They are looking into it. They have suggested a couple of actions from our end to actually delete those backups, archive them, and restart the backups, but they're still looking into it.

Which solution did I use previously and why did I switch?

We wanted to get away from tapes. We tried Veeam but it did not work very well for us. There were a couple of shortcomings which we couldn't maintain, plus it wasn't cloud-ready at that moment, at least not to the extent that Rubrik was.

Rubrik was very fresh in the market at that time, but it was bringing features that we were looking for. We were already set on using either Azure or AWS and it had the needed support for them.

How was the initial setup?

I've been involved with upgrades but not an install because we just have the one on-premise device. I've been involved in multiple proofs of concepts. For example, they launched a couple of features along the way where we were testing cloud workloads and converting our images to native AWS images so that we could use it as a disaster recovery site in the future, if needed. All of our backups are going to AWS.

Upgrades are very straightforward. Their support is always with us, so we haven't had any hiccups during the upgrades. They go very smoothly. I've been involved in multiple upgrades, and we were at some point running the bleeding edge software, when we were looking for some features that were available, without any issues. So we did upgrade to the latest and greatest version. Our general policy is to stay one version behind to iron out all the bugs. But with Rubrik we have attempted to run the latest version, to use the features, and it has been stable enough for us and the upgrades have gone smoothly.

We usually block out a two-hour maintenance window for upgrades. There have been major upgrades which required some database work, and they have taken more time. In the move from version 4 to version 5 their whole database infrastructure was changed.

What's my experience with pricing, setup cost, and licensing?

We got grandfathered in the licensing terms. Their licensing is much more narrow now and you have to buy licenses for every cloud feature, but we got most of those things as a package.

We got really good pricing because we're in the education sector and we were one of the first big organizations to start using Rubrik.

Which other solutions did I evaluate?

Recently, when we were looking for direct backup to glacier, we started using CloudBerry which is a very basic product. It's a standalone install on our media servers and it's directly backing up to glacier. It's a single unit license on the single server; there's no hardware involved with it.

The only advantage of CloudBerry is that we're not keeping an on-premises copy. When we take a backup with Rubrik it creates an on-premises copy of all of our media files and then uploads them, and that requires more storage on Briks that we don't want to spend money on. The Rubrik feature we tested, where you connect to NAS storage, wasn't available when we acquired the license from CloudBerry.

What other advice do I have?

Rubrik is an amazing product. There are some features still missing. For example, you cannot do a granular backup or restore of Active Directory. That has been on my wish list. I have posted that on their tech forum where people discuss new features and new things that they are launching. I know that it will come because they have been adding other granular backup support with VSS. The AD-level granular backup, so we can restore a single account or a single computer, is the one of the last features that we are requesting. They usually do bring out whatever features we request in their next update.

We have not used the solution's ransomware recovery. I have attended a couple of seminars where they have recently been talking about that, but we haven't tested it. We haven't had any incidents which would require us to use that feature.

We have also not used its pre-built integrations or API support for integrations with other solutions. We played with a couple of features, such as the organization features to segregate some of our VMs, but we found that it was not possible the way we handle the system. We wanted to make our domain controller backups inaccessible to our backup administrators, because we wanted that to be part of the DCA job. So we explored the organizations, but the way it works we would have had to move everything into an organization and our backup administrators were taking care of everything except domain controllers. So we dropped the idea of using organizations.

In terms of downtime, I don't think Rubrik has reduced that in a meaningful way. We have a pretty redundant environment anyway. If something happens to our VMware hosts, the VMs automatically fail over to other hosts so there is rarely any downtime. We have been off physical servers for quite some time. If there were physical servers, Rubrik could help reduce downtime, but since we don't have physical servers we don't even know what the recovery would look like with Rubrik. With tapes it was crazy when something happened. If someone did not look at RAID and we had a two-drive failure or a three-drive failure, then it would be a full recovery from tape. But now, because everything is running on VMs, we have no downtime, most of the time.

Overall the product is really good. Rubrik is very competitive. Even if you now look at their positioning on the industry review sites, they are doing really well. It's a very good product. We recommended the product to our Central IT department. We are Harvard Law School, but Harvard has a Central IT which manages other schools, and they are doing a PoC right now. It's a good product to recommend.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Kevin Mortimer
Head Of Operations at University of Reading
Real User
Top 5
SLA-based functionality means we don't have to manually manage backup windows, and recovery times have been notably reduced

Pros and Cons

  • "Not having to specify a time to run a backup with a fixed schedule is something that's really beneficial. In the past we had to schedule and try to manually stagger things over the window, to back up everything. Because Rubrik is SLA-based, you say, "Well, I need it to fit in this window here," and it just backs it up when it's most convenient for the Brik and for the third-party system. It looks at the CPU usage and says, "Okay, it's not as busy now. I know I've got time to take the backup." That's a real advantage."
  • "Looking at how the data is broken down, we can see the total story, but sometimes it's difficult to see how big a particular snapshot is. Across 90 days of snapshots, which one is a particularly large one? Looking at the data holistically could be a lot easier."

What is our primary use case?

We use Rubrik for VM backups, NAS backups, and SQL backups. Most of what we protect is virtual. It's AHV and VMware, primarily. We have a half dozen physical machines, but most of it is virtualized. We don't do any cloud-native protection yet, although we're about to start doing Office 365.

We have the Brik as an on-prem piece and we offload all our data to Azure.

How has it helped my organization?

Not having to specify a time to run a backup with a fixed schedule is something that's really beneficial. In the past we had to schedule and try to manually stagger things over the window, to back up everything. Because Rubrik is SLA-based, you say, "Well, I need it to fit in this window here," and it just backs it up when it's most convenient for the Brik and for the third-party system. It looks at the CPU usage and says, "Okay, it's not as busy now. I know I've got time to take the backup." That's a real advantage.

When it comes to its archival functionality, automatic is probably the best way to do it. You set it up in the SLA to archive the data, and tell it where to put it, and it just does it. You don't have to worry about it. You don't have to check it. It just works. That's true with a lot of Rubrik's functionality. The big thing, the big benefit, it gives us is that it just works. We don't have to handhold it or check it to make sure things are still working. It does just work.

Another way it has improved our organization is recovery time. In the past, when we wanted to recover one of our SQL databases—our student record system is about 1.5 TB in size—to recover that from tape used to take about four or five days, and then get it onto a disk and have it visible in SQL Server. With Rubrik, when we've had to recover that, we've actually put it into the Live Mount capability. It runs on the Brik in the SSD layer. When we timed this, it took nine seconds to mount it so it was available in SQL Server and, within 30 seconds, it was out-performing production on queries. So within a minute you can have recovered what you might need to recover, rather than having to wait days to recover something. And if you have to completely replace the database, then you can migrate that over. Or if you have to just take some data out, you can just pull that out as well. It's an instant approach to database management, rather than having to worry about the time it takes to get data out.

And when we've had to recover a backup of SQL data, it has reduced downtime. It's allowed us to get back up and running within 10 or 15 minutes, rather than having to wait days to recover something, especially where the state needed to be adjusted as well. The impact, the downtime, is much reduced now.

When it comes to backup testing, we don't have to worry about validating that the backup has run. We can spin up a backup into Live Mount. We run our DBCC checks for SQL against the Live Mount instead of production. That helps protect the production platform performance, but it also allows us to validate that our backups are smooth and are recoverable as well. Having a backup is one thing, but proving that you can restore them has always been a bit tougher. So we pick databases on a weekly basis and recover those with Live Mounts to make sure that we can access the data in them.

We also don't spend time managing backups now. That's the really important message. We used to have about half an FTE looking after our backup state, making sure jobs were running, or actually changing their tapes on a daily basis. That's all gone away now. If anything, it might be 0.1 FTE, just to just keep an eye on things occasionally. Some weeks there might be two days of stuff we might need to do, whether it's for upgrade prep and then doing an upgrade, or adding some new bits to the backup piece, or removing things as we decommission them. But it's more operational now, rather than actually managing the backup piece itself. It's just another part of the process. Part of the business case for us was the time it was going to save us in managing the backup, to add more value back into the organization.

Rubrik has given us that half an FTE back. We don't have to worry now about what the backups are doing. We can actually now focus on other things. As a result, our IT security posture has improved because we've realigned that resource to improve our IT security resource count. We're now being more proactive with our security stances. We are able to use our resources more efficiently.

The Polaris, SaaS-based framework for extracting metadata is what the ransomware product actually is surfacing. You have the core Polaris product which is the GPS, and then Radar is actually in that. We do have Sonar as well, which is the data classification product search, to look for data that shouldn't be in certain places. The benefit of Polaris is that I don't have to be onsite to look at that. I can log in remotely. It allows me to have visibility of what we're doing in terms of our backups. That's particularly true if we have a ransomware alert that is triggered in the early hours. When I wake up I can have a look at that alert through the Polaris interface, rather than having to log in to my laptop and onto the VPN to get into the CDM product. Polaris is really helpful in giving us the agility.

The Sonar piece really helps because it allows us to look for data that shouldn't be in certain places, and it even helps the efficiency of platforms. For example, when our HR product creates the payroll, it actually creates a copy of that temporarily on the HR platform. When it's processed, it should be deleted or moved into archive. But when we ran Sonar against the HR platform, we actually identified that a lot of the data hadn't been tidied up as part of that process. So if that server had been compromised by either internal or external access, it would have potentially allowed a lot of that sensitive data to be leaked out. It's helped them to change their processes to look after the data better.

What is most valuable?

It backs up everything to Azure, so we no longer have to worry about tapes. When we went into lockdown, as a response to COVID, we didn't have to think about, "Well, we need to send people into the site to change backup tapes." That all carried on working. We could do a lot more remotely than we would have been able to do otherwise.

We also have the Radar product for ransomware detection. That looks for anomalies in our backups and will trigger an alert if it sees something that is an abnormal amount of change. That could be lots of deletes or modifications, compared to normal. Or it could be some VMs that have suddenly had a lot of folders added or deleted. We haven't had anything so far, at least, that was problematic, but it's nice to know that it's keeping an eye on how much change is happening with backups and helping us identify problems. It can detect when someone has gone in and deleted a substantial amount of data on a VM. If that's abnormal it will flag it and say, "Well, you might want to investigate this." 

Our finance was doing a big refresh of non-production data. They deleted a load of log data and the app flagged it and said, "Well, this is strange activity. You might want to just check this out." I referred that to the finance team and they said, "Yeah, we're just refreshing the VMs, that's okay." That was cool, because we moved on. But if they had said, "Well, no one has touched that for months," then we would have looked at it in a bit more detail to see what it could have been. But without that alert, we wouldn't have any clue that anything happened. It's helping us keep an eye on what's normal and not on the estate. It's worth it because it doesn't always have to be external actors that are causing problems. You could have somebody internal being malicious if they're looking to leave or dissatisfied in their role, for example. It helps keep an eye on those situations as well.

Its web interface is really easy to use. It's just click and go. It's fast and intuitive. We've never had any problems in navigating.

What needs improvement?

Looking at how the data is broken down, we can see the total story, but sometimes it's difficult to see how big a particular snapshot is. Across 90 days of snapshots, which one is a particularly large one? Looking at the data holistically could be a lot easier. 

With the Radar product, it would be helpful if it gave us a bit more insight into the alerts. It might be alerting on an object like this VM, but what particularly on that? A bit more oversight, without having to do digging, is the biggest gap they should be filling now.

For how long have I used the solution?

I've been using Rubrik for nearly three years now.

What do I think about the stability of the solution?

It hasn't gone down yet. Even when we've had a power problem, and the Brik actually lost power because our UPS is failing, we turned it back on and it just picked up where it left off and carried on. It does just work and it's intelligent enough to rebalance itself as well.

What do I think about the scalability of the solution?

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.

Which solution did I use previously and why did I switch?

Prior to using Rubrik we used NetBackup onto tape, and we used a bit of StorSimple as well. It used to take us six days and 23 hours to back up on those, as a full. We only had just just enough time in a week to fit it all in and then we had a very small window to change the tapes and start it off again. That was an ongoing problem we'd always had so it needed very close monitoring. If backup jobs failed it was always hard to work out why. And we had the whole tape-changing piece as well. In addition, StorSimple was quite expensive. 

Rubrik reduced our backup costs and our backup time. It increased our snapshot position as well, because we're doing incremental forever. It just made the whole process so much more efficient.

How was the initial setup?

The initial setup was really straightforward. From unboxed to being in production it took less than two hours. That was with some of the networking we had to do around it as well. 

But we did go a bit too fast in terms of deployment. Even though it's incremental forever, it has to do that first full backup. We pointed a little bit too much at it the first time around and it struggled to ingest it all and move forward. After 24 hours, we stopped and started again because we were still backing up through the old method as well. When we started again we slowed the pace down to happen over three or four days rather than one day. At that point we had ingested everything and, from there, it's been smooth sailing. We haven't had any problems. 

The biggest thing I always say, if anyone asks, "What would you do differently?" is to slow down the initial rollout to make sure that you're not overloading the first full backups. The incremental forever won't be in position as quickly, but it will be a bit more stable.

I was the only one involved in the deployment. My platform team handles maintenance of it. I've got a junior infrastructure engineer who essentially looks after it. Her role is to look after monitoring and backups. But it's not something we ever really have to look at these days.

What was our ROI?

Our ROI is actually neutral because we're backing up more. We could never back up everything we needed to back up, and that was always a risk that we carried. While the return is neutral, we are doing a lot more than we could before.

Which other solutions did I evaluate?

We looked at Veeam, but I didn't want to have a large on-premise implementation, as that is very much an appliance model. I would have had to roll out quite a lot of infrastructure to cover that.

We looked at Druva, to see where that was in the market but that didn't really fit our model.

We looked at Cohesity as well, and they seemed to be a few months behind Rubrik, and just duplicating everything Rubrik were doing.

The main requirement we did have was that it had to post to AHV as well. Three years ago, there were not many products out there that could backup VMware and AHV.

What other advice do I have?

We haven't explored the API yet. It's been on our list for quite a while, but it's always been hard to prioritize. We have so much technical debt that we've been dealing with, rather than focusing there. As an API-first product, it makes a lot of sense to go that way. For us, it's just a matter of prioritizing that. I have had a little play with the API interface, to prove we can get some information we want to get out of it.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PL
Director of Technology at a financial services firm with 201-500 employees
Real User
Top 20
Reliable, easy to automate tasks, good PowerShell support

Pros and Cons

  • "We have a great success rate for backups with Rubrik and because of the ease of automating tasks, we also run periodical restores to check the quality of the backups."
  • "I would love to be able to just get from the dashboard to a file that I need, or a system that I need."

What is our primary use case?

We are a financial company and we have redundant data centers, with a VMware Metro Cluster staged between the two locations. We have Rubrik running in our data center and it is used for backing up our on-premises infrastructure.

We keep the backup of the environment on-premises for two weeks, just to be able to restore in case we lose or corrupt part of the virtual infrastructure. We also send copies of some of the data into the cloud for long-term archiving because we're under a regulatory requirement to store certain parts of the business data for up to seven years.

At this point, our environment is probably close to 90% virtual. We use physical servers for market data and essentially, there is nothing to back up on those systems because there's no data that's worth saving there. Should one of these servers fail, we just put a new one in place. It would be deployed, including the operating system, and it would start processing market data for us. We consider these as compute nodes and there is no persistent data on them.

We are highly virtualized, so Rubrik is used to back most of the VMs up. We are running VMware ESXi for our VMs, and application-wise, we are a Microsoft shop so we backup SQL Server, Exchange Server, and Microsoft file shares. We also back up a lot of business data, which is contained outside of that server.

How has it helped my organization?

The biggest impact that Rubrik has is that it allows us to have the reliance on the backup, knowing that the data is there and that the ability to restore is there. It provided the safety net we needed to deploy faster. This is because it played a great role in convincing developers and operations to do rapid releases, as opposed to doing it the old way where we didn't have reliable backups. It meant that we had to wrap all the releases in the solid recovery plan in addition to just the rollout. Now, we have the confidence in the backup and can release faster.

Rubrik has saved us time with managing backups in general. For recovery testing, the SLA policies have greatly reduced the time that we have to babysit backups. This is simply because Rubrik put thought into designing their system the right way. Instead of adding a server by creating jobs and creating schedules on top of the jobs, you're just dropping them into an SLA and all of the legwork is done for you, so adding the systems is easier.

The fact that they're SLAs, I don't need to go through the job log and analyze it to figure out why there was a job failure. Similarly, I don't need to look into the impact of the failure. This is because I know that if the machine is protected within SLA guidelines, I will get an alert in case of a problem with a machine. In this case, it means that I need to act and somebody needs to take a look at it. Essentially, it has reduced a lot of repetitive babysitting steps that don't really produce any business value.

We have never had a problem such that Rubrik has saved us downtime. But, it's certainly a great thing to have this additional safety net, which is a reliable backup solution. Everything we have is redundant, so even there is a hardware failure, another piece of hardware kicks in. We won't rely on Rubrik specifically for disaster recovery, but we do rely on it for business continuity. If for whatever reason, both of our data centers lose power or lose internet, or are inaccessible, then Rubrik will help us rebuild the environment. What we don't rely on it for is daily disaster recovery.

As we moved away from our previous solutions, using Rubrik has improved our overall efficiency. These days, we rarely have to do anything with the systems. Most of the time when we have to resolve an issue with the backup it's because the target system has become unavailable or has been taken offline for maintenance. It may also be the case that we have another restore request. These are the only two reasons that a restore might be delayed. It is not the same as we had with NetBackup, where we had to update the agent and software. We don't have to do anything of that nature. Backup is now pretty much gone from our weekly schedule.

What is most valuable?

The most valuable features are reliability and programmability. We have a great success rate for backups with Rubrik and because of the ease of automating tasks, we also run periodical restores to check the quality of the backups.

Rubrik makes it really simple to automate the restore task, which is important because I don't care about the backup. I care about the restores, and Rubrik did a great job of assuring restore reliability.

Our time spent on recovery testing has improved simply because we're able to automate it. It saves us between two and four hours per week, whether it is simply adding a new machine or going through the logs and seeing what failed.

We don't do recovery on a daily or weekly basis. We receive between two and four recovery requests per month. Because it is mostly manual stuff, it is comparable to the old system if we're talking about restoring something within a two-week timeframe when it's still on disk. However, if we're talking about restoring from the cloud versus restore from tape, the timeframes are not even on the same level. This is simply because we use the offsite storage for tapes, so sometimes the restore task from tape will take weeks.

The web interface is easy to navigate and pleasant to look at.

The SLA-based policy has simplified our data protection operations tremendously. It goes back to caring about restores instead of backups, and the fact that it allows me to easily drop systems into the SLAs greatly reduces the amount of time it takes to set up the system for backup.

It allows me to create a protection policy and while it's running, I know that the systems that I've assigned to that policy are being protected accordingly. If that is not happening then I get an alert or a notification telling me that the systems are outside of the protection horizon. It's a great approach.

The archival functionality is impressive. Just by eliminating reliance on the tape technology, it's greatly improved the rate of successful restores that we were able to perform. In two and a half years, I can't remember a case where we couldn't locate data that was backed up using Rubrik.

We have not needed to use the ransomware recovery function but I know that Rubrik backups are essentially immutable. Even if an intrusion does happen, we'll be able to restore the data quickly.

I have used the rapid restore functionality and I noticed that on many occasions, I was able to mount a virtual machine or database on the Rubrik cluster itself. So, I know its high-speed connectivity options are excellent and support VMware well.

With the previous version, we had to do some Python scripting because the API was better and more developed than the PowerShell support. However, with the new version, it seems that PowerShell covers all of the functionality that we need, which is great, especially because we are a Windows shop.

The restore success rate is very good. I don't care so much about improving the time spent on the resource. Rather, it's the success rate. At this point, we have a 100% success rate, which was definitely not the case with any prior system that I've used.

What needs improvement?

I would love to be able to just get from the dashboard to a file that I need, or a system that I need. I believe that right now, there's the ability to search by system name, and then it will take you to the system. It would be great if I can reduce the number of clicks that I need to take in order to do a restore, or maybe to a system and the file, or maybe just directly to the file. It would be like continuous integration with PowerShell.

As we go into the Cloud in addition to Polaris, I would love to see a future where I can back up pieces of the Cloud, perhaps ARM templates or Azure Active Directories from the Cloud to on-prem. I know it sounds counter-intuitive, but just as the Cloud becomes more popular and used on a daily basis, I would love to have just a single pane of glass to provide visibility into the backups.

For how long have I used the solution?

I have been using Rubrik for approximately three and a half years.

What do I think about the stability of the solution?

In addition to just great recovery rates, we haven't had any unforeseen outages with Rubrik itself, due to hardware failure or anything like that. Even the Rubrik software upgrades are non-disruptive in the sense that because they're multiple nodes in the chassis as the upgrade happens, Rubrik never actually goes down and can continue doing the backups on the nodes that are not directly affected by the upgrade.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

Our experience with technical support has been great. We had a couple of questions in the beginning, so we interacted about two and a half years ago. You would email them and would get somebody from there, without having to exchange many emails.

They will do the upgrades for you, so lately, probably over the past year, the only interaction we have had with support is when we needed to do an upgrade. It's a great experience where you just open up a support ticket with them, they open up the secure remote channel, and they come in to complete the upgrade.

Which solution did I use previously and why did I switch?

Prior to Rubrik, we used Veritas NetBackup for the backup and CommVault for the tape system. We switched to Rubrik because our success rate was poor. The restore rate was horrendous, especially when we had to go to the tape system. it was hovering around a 75% success rate.

How was the initial setup?

The initial setup is extremely straightforward. We went through the exercises and were provided configuration details that were required from us. I think that they were as simple as supplying IP configuration information. Then, once they assembled all of the racks and wires, the Rubrik technician showed up, configured the system, and it was all done in probably less than 20 hours in total.

Because we're virtual, it meant that our implementation strategy was simple. Essentially, once the Rubrik system had been configured, all we had to do was to point it to VMware vSphere vCenter servers and from there, it automatically picked up all of the virtual machines that we had. Then, it was just a question of assigning them to SLAs and removing them from the old backup system. That final piece is not included in the 20 hours because 20 hours was just to get the Rubrik running. But, it was extremely easy to integrate.

What about the implementation team?

We worked directly with Rubrik to help with the deployment.

For maintenance, you really don't need more than two persons, and that's for redundancy purposes. You can have a single person manage terabytes of backups.

What was our ROI?

By now, we have probably made the money back in reduced support costs. Beyond that, we don't value this type of product by how much money it produces. Simply, the compliance requirements come with steep fines and other repercussions if they are not adhered to. Because this product gives us assurance in our ability to restore data if needed, it satisfies our compliance requirements.

What's my experience with pricing, setup cost, and licensing?

You get what you pay for. Rubrik was probably the most expensive solution but in the long run, it's justified by the value of the data that it protects. We were able to make a case that it's a good investment.

They have a very straightforward pricing model.

Which other solutions did I evaluate?

We evaluated a couple of other solutions, but Rubrik offered the best appliance. We looked at products from Veeam and the present solutions from Veritas and others, but it looked like Rubrik was the most modern solution.

What other advice do I have?

I am familiar with the predictive search but we're not employing it. Usually, when we need to restore, we have to restore the whole machine or we know the location of the file or data that was deleted.

We've considered using the Polaris SaaS-based framework as we're looking into leveraging the cloud a little bit more. Polaris is definitely on our radar, but we're not using it in our day-to-day operations.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
FL
Senior Technology Architect at a comms service provider with 1,001-5,000 employees
Real User
Top 20
We don't need to manage maintenance or backup windows anymore

Pros and Cons

  • "The main benefit is that we are secured in terms of workloads. We know that if we need to restore any VMs, or even any files inside a VM, that we will succeed 100 percent. This means that we don't need to spend much time administering the backup environment because we know it is self-healing and efficient. So, we are spending that time on something else, which is always a plus."
  • "There is always room for improvement with some shortcuts for the web interface. They could make it even more beautiful."

What is our primary use case?

We have the r6000 series as the physical appliance. We also have the Rubrik Edge, which is a virtual appliance, depending where it is deployed. So, we have three strategic data centers where we are placing physical appliances. For test purposes and some branch offices, we are using the virtual appliance.

Most of our workloads (98 or 99 percent) are virtual on-prem, then half a percent are physical and half a percent are in the cloud. In the cloud, we have both AWS and GCP, but it is still very light. We are in the process of migrating a percentage of our on-prem workloads into the cloud.

We are in a telecom environment, so we have a lot of homegrown applications based on the Linux operating system. We have MSSQL and MySQL as well on the Linux environment. We are also protecting Windows Active Directory. We don't have a lot of proprietary applications, like SAP, but we have Oracle, MySQL, SQL Server, Active Directory, a couple of file servers, and the rest are mostly home-developed applications.

How has it helped my organization?

The main benefit is that we are secured in terms of workloads. We know that if we need to restore any VMs, or even any files inside a VM, that we will succeed 100 percent. This means that we don't need to spend much time administering the backup environment because we know it is self-healing and efficient. So, we are spending that time on something else, which is always a plus.

We use Polaris. Polaris is the front-end, which provides us a centralized view of all our Rubrik deployments in the company. It is a way to see each event's alert reporting and have a map of the world where you have Rubrik deployments.

A backup solution can help you with downtime. When you have something to correct, then it means that you need an immediate activity/action to restore the service. With Rubrik, we can immediately restore the corrupt data or VM. You don't need to worry about finding, loading, and indexing the date, then finding the relevant information to initiate a restore. With Rubrik, we don't need all those activities. We just need to do the search, click for the right VM, and push the restore button. That is it. We can probably reduce the downtime by a factor of 10 without any depth.

What is most valuable?

Rubrik's web interface is an eight out of 10. It is very easy to use, clear, and responsive. You don't need to click into many different places to get the information that you are looking for; it is intuitive. I like it a lot.

The SLA-based policy automation that Rubrik brought to market five years ago was really a game changer. In the previous backup product, you always managed your backups on a job basis, so what you needed to do is, to say, "Okay, I'd like to backup that specific workload, but I need to stop at this time." With Rubrik, it is completely different. You just need to configure an SLA, saying, "Okay, I would like to have a daily backup," or "I would like to do a backup every six hours. However, Rubrik, start when you think it's the most appropriate time." Then, you don't need to manage maintenance or backup windows anymore. In our environment, where we have based our data centers in the US, Europe, and Asia, it is not a headache anymore to configure our backup jobs, since Rubrik deals with it. When you configure the Rubrik environment, it is a few clicks. Then, you are good to go, and it's already doing backups by itself.

The solution’s archival functionality is very interesting because you have a lot of options. You can either archive on-prem or in the cloud. On-prem, you have the choice between object storage and block storage, which is nice, as it fits any environment. Archiving in the cloud is very easy as well. There is no support in GCP and AWS history in Glacier, so it is a very good option. 

It is easy to offload your local storage. If your brick is becoming full, you have two options: 

  1. You buy an extra brick, expanding the cluster, but it has a cost. 
  2. You can decide to archive your data. This means that the snapshots that you have on the Rubrik cluster can be migrated to another place. Another place can be either in the same data center or in the cloud. This is a great option, and we are using it.

We are scripting a lot using the Rubrik API to gather some information about usage, monitor what is going on, or do some very specific actions, like initiating a backup from the command line within a scripted environment. So, it is very handy.

There is a search feature inside the cluster. So, if you want to restore a specific file from a snapshot, you can then do a search inside the snapshot. The time that it takes to find and recover applications/files is almost instant. In the previous backup software that we were using, we didn't have the ability to dig inside and browse the snapshot, or even search inside the snapshot to find the required file. We can find instantly what we were looking for by searching inside a snapshot because Rubrik is maintaining a metadata DB where we can find anything that we want. Whether it is on-prem or archived already in the cloud, we can find anything using this search mechanism.

What needs improvement?

There is always room for improvement with some shortcuts for the web interface. They could make it even more beautiful. While there is always room for improvement, it is already a great product from a UI point of view.

It would be nice if we could do a live mount of the Nutanix AHV VMs, but this is not really an issue on the Rubrik side. This is more an issue on the Nutanix side because they need to share the relevant API to allow Rubrik to do that. I know Rubrik is intensively discussing with Nutanix to solve this problem, or at least to open this functionality to the rest of its customers. That would be nice to have the Nutanix AHV live mount, but this is probably for the future. I know it is on the roadmap, but it is not easy because there are some politics between the two vendors.

Today, there is no way to migrate archives from one location to another. This is being evaluated by Rubrik at this time. I know because I am pretty much involved with the Rubrik engineering team as a customer advocate.

For how long have I used the solution?

I have been using it for about four years.

What do I think about the stability of the solution?

We have been a customer for the last four years without any hardware failure. That is one aspect of its reliability. 

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

If you have any issues with the software, then the Rubrik support is trained and responsive enough to get you covered. I would rate the technical support as a nine (out of 10).

Rubrik selected a bunch of customers who are active with the product, trying to make it evolve. From time to time, we do meetings saying, "Okay, what could be nice to have in the future?" They are taking advice from the real users, and I am a part of that.

Which solution did I use previously and why did I switch?

We were looking at a way to standardize our data security platform, because we were using a lot of different software, like Veeam, Aranda, HPE Data Protector, etc. In total, it was something like six or seven different backup solutions. It was completely scary to manage on a day-to-day basis. Depending where in the world that we needed to do backups, it was a different software. 

It was completely crazy to manage, not only because you needed specific knowledge of the product, but also because every product didn't have the same behavior and capabilities. This was one of the many issues that we had. Then, we decided to standardize into a common platform everywhere, and that was why we switched to Rubrik. 

The main driver was to find a way to back up over where Nutanix stressed us, because we are a Nutanix customer. At that time, not many vendors were able to protect Nutanix AHV workloads, but Rubrik was one of them, and we decided to do a trial with them. It was absolutely successful in each aspect. It was easy to use and efficient. You didn't need to worry about our restore tests, which were very easy. So, the use case that we have was to protect our Nutanix workloads and SQL DBs. Also, the flexibility that Rubrik has given us is absolutely crazy.

How was the initial setup?

15 minutes is the time that you need to deploy a Rubrik cluster from unboxing to the first backup. In other words, the initial setup is very easy and straightforward. As soon as you have the network ready to accept the hardware, the right credentials to configure the different vCenters in the Nutanix cluster, and all the backup elements, 15 minutes is the time that you need to be up and running.

What about the implementation team?

I deployed it myself. It is too easy to involve a third-party, which would be a waste of time and money.

What was our ROI?

Rubrik has reduced the time that we spend on recovery testing. Previously, when somebody was requesting to restore a file, everybody was trying to escape that task. Now, it is the opposite. Everybody wants to do it, because it is so simple.

We don't need to manage our backups anymore. We just need to configure them, and from time to time, check if everything is okay. If something is wrong, then we will get an email from Rubrik anyway. It is almost a product that you can configure once, then forget it. The time that I am spending on Rubrik daily is less than half an hour. This time allocation is for anything that is data protection-related.

What's my experience with pricing, setup cost, and licensing?

You need to understand what you're getting for the price. You are getting a backup solution, which is state of the art and works absolutely flawlessly. You are getting the storage needed to store your backups. You have all the sexy features that a modern backup solution can provide you, like deduplication, erasure coding, compression, fast execution time, secured data, and top-notch customer support. So, it might be expensive on paper. It's not free, but when you analyze what you are getting and the time you can spend on other stuff, then Rubrik is very cost-efficient.

We started to use Rubrik Go about a year ago. It is a bit of pity that we discovered that only two years ago, because Rubrik Go is the best solution for us because we are an OpEx company. This means that we are using leasing a lot. All our previous appliances have been leased with a third-party. If we knew that Rubric Go existed, we probably would have used it a long time ago because you are dealing with only one vendor, which is Rubrik. This brings two very important advantages:

  1. As soon as there is a hardware refresh, you can benefit from that hardware refresh at no cost. It's already included. So, if I know that in a couple of months, there will be a new hardware released by Rubrik. What will happen next, they will provide us with the new hardware and send an engineer to migrate all the data from the old version. Then, they will take the old version back with them. This is great. I don't know another vendor who does this.
  2. We have access to the Polaris framework because it is included. We have started to use Polaris because of the Rubrik Go initiative.

Which other solutions did I evaluate?

We looked at the next version of Veeam. Back then, it was not satisfying. We identified three issues: 

  1. Veeam is only a software. With Veeam, you still need to find storage in the company to deploy the tool and store the backups. This is not the case with Rubrik, which is a turnkey solution. You have everything: the storage, compute, and software. 
  2. Veeam was still using the old way of managing backup jobs, meaning that you need to say, "Okay, at that time, I need to start that job. At that time, I need to start that other job, etc." It was very complicated. Since then, Veeam also moved to an SLA-based policy. So, they actually copied Rubrik. 
  3. The lack of Nutanix AHV support, though Veeam now supports this.

I'm still convinced that Rubrik was the best choice for the company because it is so easy and efficient.

What other advice do I have?

The best thing to do at first is to start a PoC. Usually, you can get the physical hardware onsite for a month, then you can play around with it and be involved with the product from day one because you will see it works. You will enjoy it a lot and won't want to give the PoC hardware back to Rubrik because it's so impressive. That is what happened to us. We kept the hardware for two months. I was actually negotiating with Rubrik to keep it longer. I was battling internally to convince the management to get the first brick, knowing we have 15 bricks all over the world. If you start and test it, then you will love it.

We are not using Polaris Radar to get more insights about ransomware.

I would rate this solution as a nine (out of 10) because perfection doesn't exist.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Lee Apps
Cloud Services Manager at Tecala Group
MSP
Easy to use with minimal training required, innovative, good support

Pros and Cons

  • "The ease of use and innovation are the features that stand out for us."
  • "The Office 365 protection could be improved."

What is our primary use case?

We predominantly use Rubrik to back up VMware, VMs, SQL databases, Windows files, NAS data, and EC2 instances in Azure VMs.

We have two data centers with Rubrik installed on the bricks in those locations. Then, we have virtual nodes installed that are at customer sites. We are using it for AWS and a little bit of Azure, as well.

Rubrik covers my need for backup and disaster recovery for customers. We back up in our primary data center, replicate data to a secondary data center, and provide hot mount capabilities for customer VMs in the event of a disaster. We also use it for long-term archiving of on-premises customer workloads.

How has it helped my organization?

The SLA-based automation is a lot easier than worrying about what time we schedule jobs and what job needs to run at what time. Having the system determine the priority and scheduling jobs to meet compliance has made it a lot easier.

We have used the Ransomware Recovery feature and it is good. However, I think that it lacks a management-type reporting dashboard. It could be used to show the value in the product because generally, until something happens, it's seen as something that sits in the back end and you wonder if it's ever providing value. 

It has reduced the time we spent recovery testing. We can now automate using a script rather than a human. To do this, we utilize the APIs in PowerShell for generating those automation test restores.

We have a self-service portal for our customers, so our customers can log in and restore files themselves. Previously, that wasn't a capability that was available. In terms of time-saving, it's massive because if we can provide that functionality down to a customer and the customer can restore themselves, it's taken a hundred percent of the workload off of us and empowered the customer to do what they want to do.

What is most valuable?

The ease of use and innovation are the features that stand out for us. It provides the capability to drive down to the end-user, service desk level one, and use the system with minimal training.

The web interface is excellent, and we really like it. The Google search, capability for file restore, and the ability to integrate the API into third-party products are really good.

The archival functionality is excellent, supporting all the major cloud vendors. For our situation, it supports pretty much all of the archival methods that we would want to use for long-term retention. We archive data for up to seven years.

We have used the API support for integration with vCloud director to create a tenant self-service portal. Our next project will be looking into automation with ServiceNow.

We have used the predictive search feature and it drastically reduces the time it takes to find and restore data for people. It used to take perhaps hours to hot mount an image and then search it for a file. Now, we use the Google-like search to look not only across an individual VM but across the whole environment, with all of the VMs. We can find any file across terabytes of data in under 30 seconds and have a restore done, depending on the size of the file, in generally under five minutes.

What needs improvement?

The Office 365 protection could be improved. Specifically, the design of deploying a Kubernetes cluster to Azure for protecting Office 365, and only being able to protect in Azure Blob storage, is something that should be improved. Our preference would be to protect external to Azure. We could backup using the local bricks or appliances that we already have from Rubrik or alternatively, have the capability to protect out to AWS using alternative storage that's not visual-based.

For how long have I used the solution?

I have been working with Rubrik for three years.

What do I think about the stability of the solution?

Stability-wise, it is really good. We've only ever had one node that needed to be rebooted, which didn't affect the uptime of the system. Excluding upgrades, we've had 100% uptime on the system for the past three years.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

Our experience with technical support has been really good. Feature requests are predominantly what we're asking for, and every single time that we've ever asked, the engineering team's been really good at incorporating those features into future product releases. Being able to meet with the engineering teams on the future design of the UI and the actual functionality of the product has been really good.

Having that direct contact with engineering and being able to drive what we want the product to do has been really helpful, and we see that come out in a frequent cadence.

Which solution did I use previously and why did I switch?

Previously, we had an Avamar data domain backup environment. It meant that anytime we had capacity constraints, what would happen was that Dell would come in and say that it was just as cheap to buy a new unit as it was to upgrade the existing one. It was always a big sell to supply the customer the newest and greatest thing, which sort of capped out at a certain capacity and couldn't really be expanded past that point.

Being an MSP, having expansion capabilities was really key for us. Having the ability to just add nodes, and have that capacity online inside 30 minutes was really fantastic. We know that the investment being made into the existing equipment isn't dead in the water, having to be thrown away later.

Implementing Rubrik has saved us time and money in managing backups, and I estimate that we've saved approximately 80% in terms of time compared to previously. This was in maintaining the system and doing upgrades. In terms of cost, we have had to hire a very expensive backup administrator that was really well versed in the Avamar product, and we constantly had problems with the upgrades once they were done. So, to move down to a lower-skilled and lower-cost resource, and have the task be completed in less time, was a significant dollar saving.

In the past, when we did upgrades, we could be offline for a week troubleshooting. Now, once we do an upgrade, we're back to doing backups within half an hour to an hour. 

We switched for ease of use, the total cost of ownership, and the cost to maintain. It came down to the financial benefits and the time benefits and in terms of ease of use and customer self-service. There were a significant number of reasons why we switched to Rubrik from the other platforms.

How was the initial setup?

The initial setup was very easy. The longest time it took to deploy was getting the network team to configure network ports for us, and the IP addressing. Once that was done, we were up and running within 30 to 40 minutes of the initial deployment.

Starting with the racking and stacking in the data center, the entire deployment probably took half a day for half a petabyte of data protection.

To develop our implementation strategy, we had an initial meeting with Rubrik on the design and requirements from their side, in terms of network connectivity requirements and IP addresses. We had done a little bit of pre-work with the network team to get that up and running, and ready for plugin once the equipment was delivered.

What about the implementation team?

Two of our staff were all that was required. You just need enough to lift and stack the equipment in the data center. We had assistance from a systems engineer at Rubrik.

We don't have anyone dedicated to day-to-day maintenance. I utilize my cloud staff to do the upgrades when required, but once the SLAs are configured, it almost runs itself. My service desk staff does the day-to-day backup checks and restores if needed.

What was our ROI?

Our ROI against the other products was within the first six to twelve months.

What's my experience with pricing, setup cost, and licensing?

When we originally started using Rubrik, it was under an MSP program, where we were paying a subscription fee for the consumption of the appliance. We've since switched over to outright purchase and buy as we need.

The pricing has been quite good from our perspective, in terms of being able to negotiate with the Rubrik team to get the product that we want and be able to sell that out to our end customers.

I can't complain, but nonetheless, I'll always say it could be cheaper.

There are no additional costs in addition to the standard licensing fees that we're aware of.  We haven't implemented the Sonar feature at this stage because it cannot be licensed on a per-customer basis. Rubrik has a multi-tenant functionality, and given that we're an MSP, we provide that capability to our customers. However, Sonar is an all-or-nothing addition, so given the cost of that, we wouldn't be able to sell that to all of our customers. In fact, that is one of our pain points at this time. We would like to be able to enable it on a per-customer tenant basis.

Which other solutions did I evaluate?

Prior to selecting Rubrik, we looked at Cohesity, and we looked at maintaining our investment in our current platforms, which were Veeam and Avamar. We also had a brief look at Commvault, but the cost of ownership appeared too high.

Cohesity and Rubrik were the two front runners, given the next-generation platforms that we are developing. At the time we selected, there was no local support in Australia for Cohesity, which was one of the key reasons why we went with Rubrik. Rubrik did have local support and we felt that not having it would be a major problem.

Being a relatively new company, we also had concerns about whether Cohesity would be in business in two or three years. We had initially looked at Rubrik five years ago, and at that time we did not select them. It was not from a capability standpoint, but rather from financial viability. We wanted to make sure that Rubrik were financially viable before we selected them as a partner. After a two-year gap, we ended up implementing Rubrik.

What other advice do I have?

The lesson that we learned from using Rubrik is that it is really good to have a vision of what we want and actually see it come to pass. We have the support of Rubrik to develop a product that we're really happy to use and we're happy to present and sell to our customers. Having Rubrik in the Gartner Magic Quadrant Leaders and visionaries quadrant in the past twelve months has proven out our product selection for data protection.

My advice for anybody who is considering Rubrik is to test drive it or get a temporary environment set up. You won't regret it.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
JH
Sr Storage Administrator at a insurance company with 501-1,000 employees
Real User
There's a lot of day-to-day time savings that allows us to get freed up to do other things

Pros and Cons

  • "When it comes to saving time managing our backups, Rubrik has saved us a lot of time compared to what we were using. It feels like it has saved us lifetimes of time because the process used to be difficult. It's not just the day to time savings. When something goes wrong, that's where the real time savings comes into play. We are able to get back to where we need to be more confidently and with much fewer steps."
  • "If there was something that we could get Rubrik to fix, it would be when our DBS takes snapshots of a server or the database, the replication doesn't kick off fast enough. They can't remote it to the peer site and manipulate it back up in order to move it over, take a copy of production, slap it over, and test it out. As I understand, they are working on it. Replication works. We also get spoiled by how good things are now. We get to a point where it is so easy but when something isn't instant gratification, it seems that everything else is so amazing, why isn't this right?"

What is our primary use case?

Our primary use case is to back everything up. Rubrik backs up all of our servers on a schedule that takes the bulk of every bit of the mundane tasks out of our hands. It automates everything and frees us up to be able to look at issues where something may not have backed up correctly. We can then investigate those servers to see if they need to be updated or if there's a problem. 

A lot of times, admin will drop new servers out without telling anybody. We have SLA domains set up in order to catch those so that we're not completely caught off guard by them. We can put them in the proper SLA for the correct backup schedule and proper retention if it needs to be replicated automatically right away and from one site to the other. From there, if it needs to be kept longer, it'll go up to the cloud for cold storage.

How has it helped my organization?

When it comes to saving time managing our backups, Rubrik has saved us a lot of time compared to what we were using. It feels like it has saved us lifetimes of time because the process used to be difficult. It's not just the day to time savings. When something goes wrong, that's where the real time savings comes into play. We are able to get back to where we need to be more confidently and with much fewer steps.

As far as the day-to-day stuff goes, I don't know if there is a way to put an actual value on that other than things are not nearly as hectic on the day-to-day, stressing over whether or not the backups ran because, with Rubrik, we already know they ran.

In terms of reducing our recovery time, it has saved us hours. For a recovery event, it used to take hours into days and now it's less than an hour, it takes minutes. It's really impressive. Rubrik makes the job much easier. It's very intuitive, where everything used to be very complicated. You can almost have better job security because of how complicated it was. Whereas now, the setup of the whole system takes no time. There's a lot of day-to-day time savings that allows us to get freed up to do other things, but also to make sure that what we do have is working optimally. Before, there was a lot of stuff that would fall through the cracks that we wouldn't really know about until something went wrong.

Rubrik affects my team's productivity. I'm not even the main backup specialist on our team, but it freed up enough time for our backup specialists to show me how to do everything. It's ridiculously easy. It's simple enough for me to be able to do it where it's not my top priority task throughout the day. When something happens and someone needs a recovery, I'm able to go in and do it, even though I haven't done it in a week or so. Before, there wouldn't have been the time to show anyone else or take the time to actually learn to be able to instruct someone else on how to do it effectively and correctly.

It provides a lot of time for education and deep-diving into figuring out why certain things didn't work and then correcting those issues.

We protect virtual environments. It's all VMware, SQL database, and a few Oracle. There are some physical machines as well that require backup agents.

What is most valuable?

The recovery is the most valuable feature. The interface is very clean, streamlined, and simple to actually perform a recovery. It's four clicks away from being done, depending on what you want to do. That's on something that is already automated on top of that. All of the backups are already automated, so when something comes up and someone's requesting a backup or recovery of a server for whatever reason, it takes very little time to get in, find what you're looking for, and get it done. It's not a drawn-out process. 

The web interface is very intuitive. I compare it to an iPhone. Everything is where you expect it to be. The main tabs are very well laid out. The drop-downs inside of those tabs make sense. It's very easy to use and it makes sense. It's not the traumatic experience of older products.

The learning curve is incredibly short. The beautiful part about it is that it makes sense so that you don't have to use it every single day to be able to go back in and do what you want to do. There's a lot to be said for that.

I use Rubrik daily to ensure that everything backed up as expected. I look to see what may or may not have backed up and why. I do that aspect now a lot more. I do backups periodically when the main contact is not available. 

We use SLA-based policy automation. It solidified our data protection operations. That alone gave us the ability to simplify and streamline the process. We were able to come down with independent SLAs that met the specific needs for whatever department or server was being protected. Whether it's production, DevTest, utility servers, whatever the case is, there are individual SLAs that we're able to make simple changes at the wholesale level, if we need to. Once they're set up, they're good to go. It makes things very easy and we can set up a bunch of them which makes life tremendously easier.

In terms of the archival functionality, we pushed things off to S3 and it works. At that point, when you're bringing things back from archival, that can be a little slow, but that's a matter of things outside of Rubrik's control. It depends on what it is, where it's at, how old it is, and what it is you're paying for.

Predictive Search to find servers makes life so much easier. We're able to drill down and put it in a simple part of whatever server name it is. A lot of times people need the server restored. We check the server name and they give us some name that's not exactly the technical server name. We're able to fish down and find what we're looking for much quicker than trying to rely on them to give us the proper name. The Predictive Search definitely helps everywhere.

What needs improvement?

Our main Rubrik guy has used the API. I continually hear that it needs better documentation. I can't even get the API to work right but that's mainly on me. 

If there was something that we could get Rubrik to fix, it would be when our DBS takes snapshots of a server or the database, the replication doesn't kick off fast enough. They can't remote it to the peer site and manipulate it back up in order to move it over, take a copy of production, slap it over, and test it out. As I understand, they are working on it. Replication works. We also get spoiled by how good things are now. We get to a point where it is so easy but when something isn't instant gratification, it seems that everything else is so amazing, why isn't this right?

They're doing everything I need it to do. When everything works so well, and it's so fast, and then you stumble upon something that's not the speed of light, it's confusing. 

For how long have I used the solution?

I've been using Rubrik for five years. 

We use both SaaS and physical appliances because we have Edge devices that are considered physical, but for the most part, the majority of everything we do is SaaS.

What do I think about the stability of the solution?

It's always on. It is available all the time.

What do I think about the scalability of the solution?

Scalability is not an issue. 

How are customer service and technical support?

Technical support is pretty good. You can reach out to a support agent and have someone talking to you that you can actually work with after 15 minutes. Opening tickets online is decent. 

If you give them a sad face on a review, someone will reach out and ask what happened and what they can do better. They're definitely all about customer service and customer support.

How was the initial setup?

The installation was pretty simple.

The deployment strategy was four nodes on each side of each location and we have two locations. We did a POC and it was set up in no time. It was ridiculously fast and simple. Now, we're up to 16 nodes in each location.

There's not much to it. It's not a 28 step process. There's a little bit to it but it's plug-and-play, as much as a solution could be. 

What other advice do I have?

My advice would be to do a proof of concept. You won't be sorry. Play with it. We came from other products that were nowhere near as capable or user-friendly as Rubrik, so when we got in, it was a night and day difference that Rubrik was so easy. 

Rubrik is so much better. We're always looking at other avenues and options because other companies will always ask us to show us their product but there's nothing out there that has made us even consider switching. There's a lot to be said for competence.

I would rate Rubrik a ten out of ten. 

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
Buyer's Guide
Download our free Rubrik Report and get advice and tips from experienced pros sharing their opinions.