Rubrik Cloud Cluster

We have been working with Rubrik  product, the cloud backup solution, implemented with the storage space direct. That was a good solution at the time when I was looking at that. There were some challenges happening, but the team was quickly helping to identify the problem and then come up with a solution. Reliability was good and helped IT operation, providing very valuable inputs all the time.

I worked with both end users and also consulted on the integration of the system.

We have two main solutions from Rubrik . One of them is VM, virtualized machine, VM snapshots, the backup. The second one is SQL database, Oracle and also Microsoft SQL databases backup every 15 minutes.

The portal management was really good. The flexibility of the on-prem gateway, on-prem gateway solution was really handy for any different scenario where we needed it. In some places, we needed a cloud solution which was good enough. In some places, we needed to make it more secure and we ended up with massive data. So we were able to implement their on-prem solution to create a gateway to their cloud, but we still could use the cloud portal to restore anything we wanted, giving us lots of different options to export the data, which was really handy. Sometimes, picking the one file inside of the backup or the entire snapshot to deploy somewhere else was very handy and fast.

The self-healing was really amazing. Even if corrupted data occurred during the maintenance time, in the next cycle, they were automatically repairing the corrupted chain of the backup. That was a really handy thing. We basically did not need to do anything. In the next cycle, their automation was able to repair that. That was amazing. We did not need to create any cases or look after anything else. That was good. Also, in the last six or eight months, they came up with the cybersecurity defense features. They were adding additional features for free, such as previews. For the ransomware attack encryption things, if it happens, they were able to detect it. That was nice as well. We have not had the opportunity to see how that works because there was no attack, but from what we saw, it was good.

Portal identity management should improve. We end up losing people's identity, which was not sufficient enough to read the events. That was the only place I could see for improvement. They keep changing the layouts and descriptions, giving the user confusion if they have not used it for maybe three months. When they come back, the interface is changed. They lost the legacy support, and it is not consistent. Some of the options for the restore give a very hard time for the engineer if they come back after three months to use it because the phrases have changed completely. That is why they were not able to select whether they should select this option or should select another option. Where it comes from, the documentation we gave them does not match anymore. That was a challenge.

My consultation part was about how to integrate the technology with each other for the platform or storage or database. I did not deal with any price metrics or scaling the storage. I have no idea about the pricing part. I never joined any meetings or any documents to disclose the pricing. It was quite good in general. Recently, in March 2025, they did a new update which enabled them to update their agents remotely and built in, in-place mode. That is bringing the cybersecurity perspective. That was a big challenge. I said it is a challenge, but I do not know because I left the company, so I am not sure if cybersecurity addressed the solution. Rubrik support is usually very accommodating and very flexible. I am not sure, but the last challenge I saw was that.

I worked with Rubrik definitely from August 2023 until July 2025.

Their infrastructure was stable. We did not get an outage, but the only outage we got was because our network was impacted. Nothing on their side was an issue. One thing I can say about how stable it was is that the backing up is actually important when you turn to restore needed. When you need to restore some backup, every product is doing the same job. But when you do the restore, it is also stable and quickly delivering what we have been looking for. That makes Rubrik different. Sometimes if we cause an issue, Rubrik always notifies us that there is some issue and we cannot take the backup. Do you want to pay attention to it? That was very handy for the engineers to look after it. Where should we look? That was really good. Overall, it makes operational life way easier.

They are quite responsive, and their solution part is quick delivering. Case handling is very short. That was a good outcome. They are always approachable. We usually get quick assistance every time we approached them regarding any problem to ask for their help, and every solution and every problem was solved in less than a week.

We did use Veeam, which was horrible. Comparing Rubrik and Veeam was really relieving the headaches. Veeam was giving too much headache for data corruption. When we realized the data corruption happened and we tried to restore some things, the data was not there. That was horrible.

Comparing Rubrik to Veeam, Rubrik is much better in the market.

That is a pretty stable product. I am quite happy, and I recommend it to everyone to relieve the headaches. I am not sure about the price. They may be too expensive or not, but I do not see them in the market much. They are not very popular. Definitely comparing to Veeam, they are much better in the market. If I were to rate them from one to ten, I would give them eight or nine easily.

I would say eight to nine. I give it a nine. I am hesitant to give a ten because I am sure there is better somewhere. My overall rating for Rubrik is nine out of ten.

For Rubrik , my use case is day-to-day management, as we have configured backup for our infrastructure. I manage day-to-day activities, and if anything goes wrong or if any restoration happens, it comes up to me or related management tasks.

Rubrik  has their cluster application and hardware that allow the leverage to configure the backup on that cluster, which is on-prem, and they also provide the facility to configure that type of cluster on the cloud infrastructure, which is a good feature.

Rubrik's Instant  Recovery and file level recovery features are good and work fine for me.

Rubrik has automation capabilities that help streamline my workflows.

Rubrik is integrable with different applications, various storages, and cloud solutions through APIs. It is easy to integrate their product.

Rubrik supports Azure  and all types of clouds for multi-cloud environments.

Based on my experience with Rubrik, I think they could improve by providing more customer-friendly technical support, even though they currently offer the best support.

I have been working with Rubrik for almost three years.

For Rubrik's stability, I would rate it a nine.

For scalability, I would rate it a nine.

When comparing with NetBackup, which I used long ago, the support from NetBackup is good compared to Rubrik. I don't know if that kind of feature is available now.

The initial setup of Rubrik is simple, with cluster creation and new node addition being very straightforward.

Regarding pricing, Rubrik is a costly solution, and I would rate it an eight.

For comparing Rubrik, NetBackup is a good option, and Veeam is also available.

Rubrik is integrable with different applications, various storages, and cloud solutions through APIs.

I am currently working with an end user company in a storage-related role. There are different products we are using, including Rubrik software for backup.

I rate Rubrik a nine out of ten.

I tested out 12 use cases for infrastructure and DB prospects. One important use case involves retrieving data when a complete VM becomes corrupted using snapshots, or retrieving only the C drive binaries. The second use case involves retrieving a corrupted database from among 200 databases.

Regarding BCDR, we currently use on-premises cohesive backup, and we configured Rubrik  for both BCDR and BAO operational purposes. We identified challenges with around 24 terabytes of database volumes, which takes longer than expected compared to on-premises. We achieve the same tasks within 15 to 20 minutes on-premises.

We tested a backup of six terabytes in cohesivity which takes only 25 minutes for restoring. The same test case in Rubrik  takes more than six to seven times longer. This means the on-premises SLA is significantly faster. Currently, we are considering using only snapshot level backup and redirecting SQL backups into cohesive. For BCDR solutions, we are implementing snapshot level backup into Rubrik from West US 2. Currently, we have tested it for DR solutions, not for BAO operations. We are implementing automation, though pipeline setups, data retrieval, and data transformation take considerable time in the Rubrik solution. We continue to explore alternative approaches for achievement.

The solution is available in the Azure Marketplace , but approaching directly is more cost-effective. The Marketplace approach incurs additional platform and reporting costs.

We initially built Rubrik at host level and DB level. We encountered latency issues when reverting back, with numerous snapshots available. This resulted in increased costs and occupied spaces. I performed manual deletion of snapshots and verified with the Rubrik team for confirmation.

The GUI reporting functionality lacks flexibility. For instance, obtaining specific server reports considering drive space and backup quantities is not possible, as it only provides overall reporting.

It is a mixed situation that varies case by case. I can confirm they are accurate 50 to 60% of the time. The remainder still needs improvement, particularly in providing technical support.

I have been dealing with Rubrik solution and implementation for the last two years.

The implementation takes approximately one and a half days. The prerequisite dependencies with the cost team site, infrastructure, port opening, and adding the complete Rubrik console module take time, depending on the volume of servers and storage occupancy.

The main concern is latency and the current implementation process. Azure Backup  solution offers faster restoration for data over six terabytes compared to on-premises. Complete host level restoration across different cloud subscriptions and domains requires GUI method alignment for a more user-friendly working environment. The automation feature has limitations, particularly with snapshot restoration to other subscriptions, which works in Azure  but not in Rubrik.

The implementation process is straightforward with simple clicks, cluster implementation, discovery, and adding components.

I worked with CommVault Backup and IBM. I worked with CommVault from 2015 to 2018 for a major Sony client, but only with on-premises solutions, not cloud platforms. Recently, I started working with Veeam Backup solution in our environment and have gained some hands-on experience.

For use case testing, I performed manual implementation. We have PowerShell scripts available for direct VM attachment and database movement.

I handle infrastructure implementation and configuration of Rubrik. We have configured and implemented Rubrik solution for approximately 300 servers across production and non-production environments, managing database level and snapshot level backups, ensuring SLAs and security compliance.

For Azure Backup , I implemented database level and infrastructure snapshot level backups considering SLA retention periods. Azure  provides inbuilt backups with default 34-day retention periods and minimum seven-day periods based on standard premium settings. For infrastructure as a service with SQL applications, we configure using Azure Recovery Service solution. This Microsoft backup solution integrates with Azure Arc for centralized discovery, backup reporting, and configuration.

The Rubrik agent installation provides specific server access levels. After installation, we can discover the complete server and configure security and backup retentions. The initial backup configuration is followed by incremental backups.

The solution is straightforward to implement with simple clicks, cluster implementation, and discovery processes. Snapshot restoration to other subscriptions remains a limitation. The implementation can be completed through manual processes or automated scripts. Based on the overall experience, I rate Rubrik 7 out of 10.