What is our primary use case?
This project initially started out as a replacement for our legacy backup system, IBM Tivoli, which was backing up our VMware environment. Since our environment is almost entirely virtualized, protecting those assets was the primary goal. We also knew that we wanted to get to a state where our backups were protected against ransomware via immutability or air gapped backups, which we've now accomplished with Rubrik.
Shortly after the initial deployment, we realized the full capabilities of Rubrik. We are utilizing Rubrik's backup integration with Oracle databases and SQL databases. There are several other business critical applications, like Tableau, that are also being protected via Rubrik.
Due to Rubrik's ability to execute in protecting our on-premises assets in the data center, we decided to utilize Rubrik's Office 365 and AWS Cloud Native solution to protect our data in the cloud.
How has it helped my organization?
The SLA-based policy automation has streamlined our data protection operations. We have moved away from backup windows and moved to letting the SLA policy actually determine when is the most efficient time to do backups. We apply the SLA based on business rules to certain artifacts or entities within our environment and let Rubrik run with it. It has been extremely efficient and has cut down on the operational overhead of managing backups.
In addition, we have absolutely seen a reduction in the time we spend on recovery testing. We have automated the validation of backups for our tier-one assets using Rubrik's API.
We're seeing about a 62 percent TCO savings and 90 percent management time savings since switching to this solution. And we've reduced the data center footprint, which comes with operational overhead, by 75 percent since switching from Tivoli.
Since acquiring Rubrik's Polaris GPS offering, we have further increased our productivity by utilizing SLA policies that extend across clouds and multiple on-premises data centers.
What is most valuable?
It's hard to specify a feature that is most valuable. The overall architecture is where we find the most value. Having an API-centric approach has allowed us to utilize a lot of automation to trigger the capabilities of Rubrik. This helps us minimize the operational overhead of managing and restoring backups. We have integrated Rubrik with our ticketing system and have some custom triggers to present Dev/Test environments from Rubrik to our development team.
The web interface is extremely intuitive and, with recent changes to the API, it has become more responsive than it was when we initially implemented the product two years ago.
We love the archival functionality and we utilize it a lot. We archive out to Azure Blob Storage to have an additional layer of protection and extend SLA times.
From an information security and business continuity perspective, the solution’s ability to recover from a breach, is one of the biggest features of the product. We don't have to worry about the operational complexity of air-gapped backups and can rely more on the immutability approach. It is a highly valued feature in this solution.
What needs improvement?
At the time of this review, Rubrik is still missing several components to their Office 365 backup offering. These ideas have been voiced to Rubrik and their product management team.
It's been our experience that when our ideas are surfaced to Rubrik, we are brought into a feedback session with Rubrik's product team. We now view Rubrik as a partner in our business continuity and disaster recovery strategy.
For how long have I used the solution?
We've been a customer for three years.
What do I think about the stability of the solution?
The stability of the Rubrik solution has been extremely solid. In the 2 years we've owned the solution, we've had no downtime because of hardware or software failures.
What do I think about the scalability of the solution?
The ability to just attach additional bricks to scale-out capacity is great!
How are customer service and technical support?
Rubrik's tech support is amazing, which is yet another differentiator with this solution.
Which solution did I use previously and why did I switch?
Before Rubrik we used IBM Tivoli; however, we could never get Tivoli successfully tied into VMware. Tivoli's snapshot technology was a continual failure, and even with the support of IBM, we could not get it working without it causing infrastructure issues to our VMs. This left us in a state where we had no confidence in the ability of the product to actually execute backups or restores.
How was the initial setup?
The initial setup was extremely straightforward. The install took place one afternoon and included an upgrade. Within three hours we had our VMware environment tied in, SLAs configured, and we were prepared for the initial round of backups that were going to take place over a weekend. By Sunday morning, we had our entire infrastructure protected by Rubrik.
What about the implementation team?
There were two people directly involved in the implementation, Rubrik's pre-sales engineer and one of my engineers.
What was our ROI?
We have 62 percent TCO savings.
What's my experience with pricing, setup cost, and licensing?
Rubrik Go was not available when we initially acquired the solution; however, as we look to further investments in Rubrik, we plan on executing with their subscription model.
Outside of extending into the SaaS platform with Office 365 and Cloud Native offerings, there have been no additional costs.
Which other solutions did I evaluate?
We looked at Veeam and Cohesity.
With Veeam, it seemed like they were stitching solutions together to provide the single platform. Also for several reasons, we did not want to write our backups to the same storage array as our production system. These two factors quickly eliminated Veeam.
Cohesity was positioning themselves not only as backup solution, but also as secondary storage offering. We quickly determined that Cohesity was not as intuitive or as simple in their backup approach, which eliminated them as one of the products we were considering.
We felt it was the best strategic decision going forward to choose Rubrik since their engineers were solely focused on solving backup and their solution was the simplest and most intuitive to manage.
What other advice do I have?
The biggest lesson I've learned throughout our time using Rubrik is that the investment in simplicity, has proven to be extremely valuable.