Rubrik: modern take on backup with common sense results. Crazy right?
November 06, 2018
Rubrik: modern take on backup with common sense results. Crazy right?
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Rubrik
We currently use Rubrik for enterprise backups and DR. We use Backup with offsite Replication, and archival abilities, to allow us to be versatile with our data and provide assurance that we can can recover our data both quickly and confidently. This is managed by our IT departments for Virtual\Physical\Application (SQL, Oracle, Exchange) environments. This product addresses a lot of issues we have faced over the years. With previous backup solutions, we'd spend a good amount of time trying to keep our backup solutions running so that we could have consistent backups. However since we have switched to Rubrik, we no longer have that issue, so we can focus on the company data rather than the backup application reliability. With its ability to have multiple destinations to comply with company SLA's in regards to backups and DR, we can move forward with an improved DR plan. With previous backup solutions, we could not have multiple targets or had to rely on tape backups, and we had to hire another company to take them every day and store them.
- Performance: with its ingest speeds, as well as its block level dedupe and compression, we can store a large amount of data with a small footprint in our data centers.
- One Console to rule them all provides convenience and simplicity without sacrificing its abilities.
- Easy to use and manage
- I would like to see a little more improvement on the user management (though currently it's not bad.) Just so we could get a little more granular with specific users.
- We were able to save a lot of money by getting away from previous support contracts from a previous vendor. Also it was a cheaper option to purchase Rubrik as opposed to upgrade our existing system, which we hated.
Networker was our backup solution but they have not stayed current, and their hardware/software is peceed together from acquisitions which are forced to work together even though they are not designed to.
Cohesity was very close, but their terminology/wording made it difficult to train new users, etc. Instead of Instant Mounts (Recovered) systems they called it Test/DEV, and everyone asked the same thing. Why would they call it Test\Dev if its a Restored system from a backup?
Cohesity was very close, but their terminology/wording made it difficult to train new users, etc. Instead of Instant Mounts (Recovered) systems they called it Test/DEV, and everyone asked the same thing. Why would they call it Test\Dev if its a Restored system from a backup?