"With our legacy solution, we were unable to perform granular restores. With Rubrik, the difference is night and day—it takes minutes to recover our data from on-prem and the cloud. We also have the granularity to recover exactly what we need."
"Rubrik’s consumption model allows for pay-as-you-go flexibility, which provides us with a low-risk and low-cost recovery platform and helps us establish long-term profitable relationships with our customers."
"We were having issues with our EFS volumes with our legacy solution; we spent many hours with the support team, but the problems weren’t getting fixed. We were also frustrated by having to speak to first-line engineers every time we contacted support. In one case, we were down for a week and it took four days to reach third-line customer support. This was unacceptable."
"Growth was a consistent concern with our previous solutions. Expanding our environment required substantial planning, as well as additive licensing and hardware costs. Our previous vendor also did not support global deduplication, which led to high storage overhead. In addition, backups were complex and time consuming, and required manual scheduling to accommodate expansion."
"Prior to Rubrik, the team relied on fragmented multi-point solutions for data protection. Rubrik consolidates our backup software and hardware into an all-in-one platform that simplifies our entire data management process."
"On top of that, Rubrik’s API playground was very helpful when our team was generating code for database recovery. These APIs allow our less technical engineers to work with Rubrik and provide even more value to the business."
"As a CTO, it’s my job to be strategic about the technologies we leverage. Bringing in cutting-edge tools like Rubrik allows us to work smarter by automating manual tasks and reallocating time towards higher value initiatives that move our organization forward."
"Previously, we archived our data between hospitals, meaning that each facility had an archival partner. This had been turned off prior to the wildfire, leaving us with no valid recovery method. With Rubrik’s seamless cloud integration, we are archiving all of our hospitals’ data in AWS S3 for long-term retention and are confident that we can recover critical data in case of a disaster."
"We had been using the same legacy data management system for 13 years. It had reached the end of its usefulness for us and was causing issues that included hardware malfunctions and a lack of storage capacity. Our backup servers were Windows-based standalone machines, which we identified as a weak point that could be prone to ransomware. We wanted to ensure that our data management solution would not be affected by end-user systems susceptible to hackers."
"From an IT perspective, we’re always looking towards the future. We were blown away when we first saw Rubrik in action. With Rubrik, you could restore a database in seconds. We also loved that it provided a single interface across all our applications. There wasn’t a single vendor that offered a comparable solution to Rubrik in the market."
"Our data engineering and database teams need to honor different SLAs for each application team. Traditional disk backups do not provide a logical, application-consistent view of the data, which removes flexibility from database teams."
"Rubrik is a solution that’s built to operationalize for efficiency. When paired with exciting technical innovation like the Live Mount capabilities and granular file search, it was easy to see the impact it would have on the productivity of our entire company."
"Backup is not the most glamourous part of IT, but when it goes wrong, it can be very tricky. Using the right solution is absolutely critical."
"The ability to use Rubrik’s APIs with our software developers also eliminates the need for training. They also no longer need to reach out to the IT team to do a backup. We supply them with a set of commands built with the APIs and all the complexity is hidden behind the scenes, making everyone’s lives easier."
"With our old solution, there were far too many variables; we needed our own storage, our own switches, our own compute. We were spending far too much time scheduling jobs and figuring out optimal backup windows, not to mention dealing with backup failures."