What is our primary use case?
We have been mainly using Rubrik's backup and recovery solution for our microservice-based products, which we have for different trading applications. We have a trading application, where the customer makes use of any workflow through the GUI of the trading application. The request goes through our microservices server REST API. These microservices server REST APIs are sometimes using DynamoDB as a database solution.
Our applications are quite scalable and user-friendly. We wanted our database solution to be highly scalable. Since all the trades being carried out between customers are highly secure in nature and carry sensitive data, we wanted this in case there was some type of application crash due to a timeout or downtime. Our database should not crash and the data should not be lost. For that purpose, we needed to use Rubrik's backup and recovery solution. So, on a weekly basis, we take regular snapshots of our databases via Rubrik's solution in case of any downtime, especially during the week from Monday to Friday when trading is being done at a high peak level. At that time, we take snapshots. In case there are any issues, then we will simply roll back our database to the previous snapshot which we had captured.
We are protecting VMs. They are all virtual.
How has it helped my organization?
It has reduced our maintenance efforts. The amount of time and effort that would have gone in troubleshooting various issues related to a data crash has been addressed by Rubrik. So, it has helped to improve our productivity. The data is being captured about our customers periodically that is secure and safe.
Our entire team uses the Grafana application to monitor the response time of various API that we have in the application. Because we can restore our application to its normal state, gradually the graph of the downtime comes down for APIs. For Grafana plotting, we are using different error codes. We see in graph form if there are any spikes in the error code, for how long those spikes remain, and how much time it took for the spikes to go down their normal level.
What is most valuable?
From a security point of view, data is highly-encrypted using the Rubrik security solution. Therefore, we don't have to worry about any image/data loss or data leakage.
If there is any corruption of the snapshot, e.g., the target is corrupted while taking the snapshot, Rubrik is our faster option to have two snapshots: snapshot one and snapshot two. If there is some issue with snapshot two, then we still have the option to restore the data to snapshot one. In this way, we never lose the customer's trade data.
Rubrik's web interface is very user friendly and easy to use with all its navigation, e.g., it is easy to identify if you're looking for any help. So, the help features are there. The customer support feature is very nice. We are regularly using that. The alignment of all the fields of the platforms on the Rubrik GUI are very good.
Its archival functionality is very nice. On a regular basis, we snapshot our VMs and server logs. So, we keep archiving the logs and snapshots into Rubrik for archival functionality on a monthly basis. For 30 days, we maintain the snapshots of our data using the Rubrik archival functionality. Whenever we need to retrieve any snapshots that have been stored for the past one month, we can easily retrieve them. The retrieval process is also very fast from the archival function, and it doesn't take too much time.
For how long have I used the solution?
We have been using Rubrik for around three years.
What do I think about the stability of the solution?
In my experience of using Rubrik, once or twice it didn't work and the issue was resolved quickly. Otherwise, it is quite stable.
My colleague, my assistant, and I manage it.
What do I think about the scalability of the solution?
It is highly scalable. We can easily add more VMs to our configurations or Rubrik account. It also can easily take snapshots.
In-house users are around 25 to 30 people who are mostly from the DevOps profile: software engineers, the infrastructure team and release managers. Developers are also involved.
How are customer service and technical support?
We have received excellent customer support from Rubrik when addressing any of our queries, from time to time.
The technical support is very good. They are quite well-versed with the Rubrik solution, so they provide quick solutions to our queries.
Which solution did I use previously and why did I switch?
We were not previously using another solution.
We learned third-party backup and recovery solutions can be good enough to handle and exhaust all our requirements. Instead of starting to build a backup recovery solution from scratch, we explored outside our organization. Now, third-party vendors are very good and intelligent data recovery solutions are available.
How was the initial setup?
The initial setup was between an easy to medium difficulty level. To install the Rubrik application, we created an account, then specified the contribution of our VMs. The microservices took the most amount of time during the setup part. Later on, defining the duration and frequency at which we want the snapshots to be taken was easy.
The setup took three to four days.
What about the implementation team?
A colleague and I deployed it. Whatever we couldn't do, we directly contacted Rubrik for that.
What was our ROI?
Due to this effective, faster backup and recovery solution, we are now able to focus on other creative tasks to meet our entire pipeline. So, we have seen ROI in terms of the improvement of productivity in our team. We save around one million dollars a year.
The solution has saved us 25 to 35 percent of our time.
The maintenance has been very quick and fast to retrieve our snapshot from the archival functionality. If you had to source for any data research query, then that used to take around one hour for one terabyte of data. Now, that has been reduced to 20 to 25 minutes. It takes less time for us to restore data as well as reduces recovery time.
The downtime has been reduced. Downtime used to be around five to six hours. Now, it has been reduced to three to four hours. This reduction happened after two or three weeks.
What's my experience with pricing, setup cost, and licensing?
The licensing cost is quite high. That is something that needs to be worked out, because so many times it happens that the team does not have the budget or there are other issues at that time. Cost has become an important factor in deciding whether to continue with the Rubrik solution.
The maintenance cost is low.
Which other solutions did I evaluate?
We also initially evaluated Cisco, Dell EMC, and Nutanix and found the Rubrik solution to be the most effective for our requirements. Almost all these solutions were equal. With the other vendors, the main problem was the customer support when we initially gauged those vendors, e.g., to get hands-on training to get a demo, then later on to follow up with their teams, the entire process wasn't smooth. However, with Rubrik, we didn't see this problem.
We are considering migrating our microservice stack from a VM-based solution to Docker-based solution. So, we are considering a Docker integration with Rubrik for the communication of our microservices with ModAPI of our solution. For that, we probably need a handshaking mechanism. For that purpose, we are considering the Rubrik security REST APIs.
What other advice do I have?
I would strongly recommend trying the Rubrik solution. Their solution is stable, scalable, and intelligent. It has cloud solutions for our backup and security needs.
We are not using the SLA-based policy automation feature of Rubrik. We might look at this in the future. Now, we have our own separate SLA-based automation tool.
We are using Polaris, but there is another team at my organization who handles governance and compliance.
They are in touch with our team to understand our entire integration, setup, architecture, how things have been done, and how Rubrik is helping us. The plan in the future is that certain teams will start using Rubrik in their application.
I would rate this solution as a nine (out of 10).
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Which version of this solution are you currently using?