Rubrik Reviews

My clients primarily use it for for backing up enterprise workloads like VMs, databases, and other enterprise products.

I work for an IT service company. I design solutions for our customers and use many Rubrik services, including Rubrik Cloud Vault, Office 365 protection, and data center protection. So, I design and implement, and my team supports the solutions.

Rubrik is an important tool for data recovery in case of a ransomware attack. It's a crucial part of their overall venture, as data recovery would be difficult without it.

The guarantee of data restoration in a crisis is the main benefit.

It's a combination of all features that offer value, like ransomware remediation and sensitive data discovery, that are better than other solutions.

Rubrik is emerging with its AI capabilities. Rubrik's AI companion is called Ruby which is very useful. 

For data security, anomaly detection, site monitoring, and threat hunting are very important features that help customers.

Rubrik offers extensive automation capabilities. Usage varies depending on the customer. We create automation for testing, recovery scenarios, and other testing scenarios.

The only disadvantage is the price due to the extensive features.

I'd like to see a cloud backup service for smaller customer environments that may not support a physical or virtual appliance.

I have been working with Rubrik for three years.

It's very stable.

It's incredibly scalable. The size of the environment varies greatly depending on the customer. Some have two or three people, while others have thirty to forty peple.

The customer service and support are good.

Positive

The initial setup is very easy and not complex at all.

Deployment process:

We plan, design, and track everything. If it's in a data center, racking and cabling are done. Then, we integrate with VMware, the application manager, and deploy the VMs. 

If it's a public cloud, it's a similar process, but we have to submit changes to the organization.

Deployment time:

It depends, but in a data center, we can be up and running in one to four weeks.

We have multiple customers, so we work with different versions. 

For deployment resources, we usually need two people with minimal support from the data center for facilities, network, and security.

We haven't calculated the exact ROI, but it is a bit higher. Sometimes, customers hesitate initially due to the cost.

It is expensive.

I would recommend using it. 

Identify your specific feature requirements, compare different Rubrik versions (Foundation, Business, Enterprise), and carefully consider sizing to avoid overbuying.

Overall, I would rate the solution a nine out of ten.

We use the solution for backups. We transitioned from Veeam to Rubrik, and we currently have on-premises backups for production and disaster recovery purposes. These backups are clustered between both sites, with 60 appliances used for backup operations.

Rubrik simplifies our data backup and recovery processes significantly. It's very straightforward to use. We start by tagging through VMware, and everything tagged for Rubrik is backed up automatically. Backups are much better and faster because Rubrik takes a full snapshot of the virtual machine. We recently conducted a verification by performing a restore, and even during the restore process, we could bring up the server in less than 10-15 minutes. Additionally, we have set up alerts for sensitive data, which helps us track data. 

We have set up all the alerts for sensitive data. It's not exactly data governance fully, but it does help us to identify those data. The tool helps us to avoid vulnerabilities and any cyber protection issues. For example, if any antivirus or other security measures are on the system, Rubrik flags it immediately, indicating that a backup and an air gap are required. This ensures that no other backups would be impacted if there's an issue with one backup. Additionally, Rubrik comes with live monitoring capabilities, allowing its support team to identify and address any issues immediately. 

The tool's most valuable features are the management of sensitive data, the air gap backup functionality, and the real-time monitoring capabilities. Additionally, the speed and reliability of the platform are also highly beneficial.

Instant recovery with Rubrik has significantly improved our RTOs. The process is much quicker than traditional backups, allowing us to restore backups with minimal downtime.

I hope to see enhancements in areas like data governance and the incorporation of new features in future updates.

On a scale of one to ten, I would rate the stability of Rubrik as a ten. It meets our requirements and has become our primary backup solution.

The solution is scalable. 

We faced no significant challenges while integrating Rubrik with our IT infrastructure. Their support team was excellent and assisted in the deployment process. Even after deployment, their responsiveness to tickets was impressive, addressing any issues promptly.

Positive

I rate the product's deployment an eight out of ten. 

I rate the tool's pricing a six out of ten. 

We found that Rubrik offered a comprehensive solution with a single appliance that met all our needs without requiring additional services or infrastructure. Other solutions often involved purchasing separate storage, servers, and proxy servers, which could be costly. In terms of cost, while Rubrik initially seemed more expensive, the overall cost was more favorable compared to the multiple components required by other solutions. 

I rate the overall product a nine out of ten. 

We're using the solution for backing up email to file servers and for Oracle backups.

The solution's technical support team is very responsive and proactive.

I don't like Rubrik's user interface because it's not intuitive, and I find it hard to get the information I need. Rubrik is an expensive solution, and its pricing could be improved. There are issues with the compatibility between Oracle and Rubrik.

I have been using Rubrik for one year.

I rate Rubrik an eight out of ten for stability.

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

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

The solution's technical support team is very responsive and proactive.

Positive

We previously used Tivoli Storage Manager (TSM).

The solution's initial setup is easy enough, and we paid for a Rubrik expert to install it for us. It was easy in most systems, but there were ongoing issues with the Oracle backups.

The solution's deployment could take a week or so. However, the deployment took a few months for us because of the compatibility issues between Oracle and Rubrik.

Rubrik is an expensive solution.

Rubrik is deployed on-premises in our organization. We're also doing a total backup to the cloud. It's backed up to our main data center, where we have a Rubrik cluster. That Rubrik cluster is replicated to the Rubrik cluster in our DR center. From there, we do a total backup to an archive out to the cloud. So, we have a mixture of everything going on.

If users are buying Rubrik to back up their Oracle database, I suggest they speak to a customer who has implemented Rubrik with Oracle. They should investigate and ensure they understand what they're buying before proceeding.

Overall, I rate Rubrik a five out of ten.

We primarily use Rubrik to back up and restore our VMware VMs and our Microsoft SQL databases and also to perform long-term archival.

Compared to other enterprise backup restore solutions, it is really easy to start using Rubrik to perform a backup and restore. The solution's interface is really intuitive.

For Microsoft SQL databases, Rubrik allows to perform a live mount of a database backup. Instead of doing the whole tedious restore procedure to get an older copy of the database back, you can also mount the database directly to the database from the backup storage. You will have a read-only copy on the backup server, which you can use to retrieve your old data.

Rubrik is a very scalable and high-performing backup restore solution. We can back up a large number of databases and also restore them with a very good backup restore performance.

Rubrik's disaster recovery capabilities could be improved. If you are using Rubrik and want to use it to do a quick and easy restoration of a site if one data center goes down, some small improvements can be made there.

I have been using Rubrik for four to five years.

Rubrik is a very stable solution, and we hardly have any issues with it.

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

I rate Rubrik a nine out of ten for scalability.

We contacted the technical support team for some technical questions, and the experience was very positive. They follow up quickly on our support cases, and we get the technical expertise we seek. If we are looking for a particular feature that is not yet available, they add that requested feature to their backlog to implement it in a newer version of the solution. We are very happy with the technical support for the solution.

I rate Rubrik’s technical support eight and a half out of ten.

Positive

We previously used the latest backup restore capabilities offered by Microsoft SQL Server. We used our custom scripts and methods to perform backups and restores. We switched to Rubrik because we wanted a uniform backup restore solution and more advanced data protection against ransomware attacks. With Rubrik, we can safeguard our data more easily than our old custom backup solution.

With Rubrik, I was not involved in setting up the backup restore solution. From a database administrator's perspective, it is really easy to set it up if you want to configure backups for a database server. You have to install the agent, and then the server pops up in the Rubrik environment as a new server. Then, you can configure your backup configuration and backup policies, and you're good to go.

If you choose Rubrik, you will most likely have a positive experience. You should perform a thorough assessment and comparison to see if Rubrik is indeed the best fit for your environment. In my personal experience, Rubrik is a very good backup solution if you can afford its price.

Overall, I rate Rubrik a nine out of ten.

I use Rubrik daily for streamlined data management. It simplifies monitoring, administration, and security tasks. With easy backup job setups and automation, it simplifies routine operations.

I appreciate Rubrik because it stands out compared to other products. One key advantage is its native security features, eliminating the need for third-party tools. This means we don't have to constantly rely on external support for security posture, scanning, or capacity management. With everything built-in, we avoid potential vulnerabilities from third-party patches, making our solution more secure and self-contained.

The most valuable feature of Rubrik for me is its user-friendliness and efficiency. While other products may have similar security and scanning features, Rubrik's dashboard simplifies access and retrieval of information. Unlike some alternatives, it allows me to quickly find what I need, saving time and making my workflow more focused and manageable.

Rubrik could improve in customization options for dashboards. The current lack of flexibility forces a standardized approach, which may not suit every environment. Unlike some competitors, like Commvault, Rubrik's dashboards are not easily customizable. Additionally, more detailed logs and reports would be beneficial, as well as a streamlined support process to reduce the dependency on opening multiple tickets for various issues. One feature I'd like to see added to Rubrik is the ability to manage multiple resources for databases more efficiently. Currently, it is a manual process, going one by one. Also, enhancing the management of SLA domains, especially when dealing with multiple domains, would be beneficial. It is challenging to run group-specific reports, and improvements in this area would enhance usability.

I have been working with Rubrik for over a year.

I would rate the stability of Rubrik as a seven out of ten. In my experience, the stability is solid, and the fact that it is hyper-converged, and integrated with hardware, gives it an edge. However, like many products, it does depend on specific use cases and configurations.

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

The technical support is generally good. While their knowledge is good, I find there is a bit too much dependency on support for every issue. As a backup engineer, I prefer having more autonomy in problem-solving without needing support for every case.

The initial setup is straightforward.

My advice to others is that for smaller environments, Rubrik is a good choice, but for larger enterprises, thorough evaluation is essential. It may lack some management capabilities for extensive setups. Additionally, check compatibility with legacy servers, as Rubrik may not support them, unlike some other products that do. Overall, I would rate Rubrik as a seven out of ten.

We back up our virtual infrastructure with it. We have about 400 virtual machines that we back up.

We are using its latest version. We upgraded just recently.

It is basically a backup solution, and we use it when we need to. We have had Veeam, IBM TSM, and a couple of other solutions before this. From the business perspective, the users don't see anything different other than submitting a ticket saying that they need something restored.

Our DBAs utilize it as well. They do test environments. They'll pull stuff from the backup system into their testing areas so they can test different scenarios, and so far, they're liking it fairly well, which is completely different from when we utilized Veeam. We basically had to go and do it for them. With this, we were able to offhand different tasks to different departments, and they could do their own tasks. So, it has made it much easier in terms of infrastructure where we can give other departments the ability to perform their own tasks and projects.

Its reporting is most valuable. I like how it reports that everything is successfully backed up. It provides a summarized report that I can give to auditors and management.

Their documentation can be improved to provide information about how some of the things work.

They should give more access to the backend capabilities. From a customer point of view, you do not have access to all the features on the system. You have to engage their support to perform some of the tasks. It would be helpful for an experienced engineer to be able to go and do some of those tasks prior to contacting the support.

I have been using this solution for about three or four years.

There are no issues on the side of Rubrik itself. Rubrik seems to be very stable, especially when it comes to their physical installs. If it's a physical backup appliance, it works really well.

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

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

We contact their technical support a lot. It is about two times a week, but it's usually where we've gone beyond the norm of what a normal customer utilizes the system for. So far, they have been very responsive, and nine times out of 10, they are able to accomplish the task that we're trying to perform.

We had Veeam before this, and we've also had IBM TSM, Tivoli. We've also used a couple of other solutions out there.

We switched because the cost of Veeam was too much. After 200 core licenses, the support cost was almost the same as buying Rubrik for the first time.

I've been here 13 years, and I actually deployed it. I've deployed five different sites, so we don't have just one. For the most part, it was pretty straightforward. It took about 30 minutes.

The first time, we used a consultant from Rubrik, and after that, we did it ourselves. Our experience with them was exceptional. It was really good.

I don't remember the cost, but I know that for Veeam, we were spending almost $250,000 a year for 205 licenses. It was an enterprise version. When we purchased Rubrik, it was just a little bit more. It was not a terribly huge amount, and if I recall, that was for three years of support as well. So, Veeam priced itself out of the market at a certain point in time.

In terms of additional costs, there are some add-ons that they have built. Since the time we purchased it, there have been different cloud offerings. When you purchase the appliance or Rubrik basic services, you get all services. As far I'm aware, you don't necessarily have to purchase extra things. They don't nickel and dime you.

I would advise others to do a PoC, test it, and see how well it works. They should compare it to some of the other solutions that they can PoC as well. That's because we've seen that there are a couple of places in our environment where Veeam still makes logical sense versus Rubrik. Rubrik is able to hit about 95% to 98% of the things that we want to do, which is not going to be the case for every company, but it will fit most customers' needs.

I would rate it a nine out of 10. They're able to hit the mark about 95% to 98% of the time, and when we have problems, they're able to jump on and help out. We're always able to work through it. Sometimes, it might take time. There is no perfect product out there that I'm aware of, or else we would look at it.

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.

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.

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.

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.

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

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

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

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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. 

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.

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.

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.

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.

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.

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.