Transcript
data you have, but how your data protection solution is storing that data. Often, we pay for the same data over and over. Rubrik does it differently, and let's see how. Let's say we have a data lifecycle policy like so. Daily backups for 7 days, weekly for 4 weeks, monthly for a year. Most native and legacy solutions will adhere to this and begin backups in an incremental forever fashion. Day 1 is a full, with incrementals following that. It sounds great, but there's problems. You see, once we have our day 9 snapshot, day 2 should be expired. But each snapshot depends on the one before it, so day 2 is needed in order to restore day 9. So we can't delete it, we simply just leave it and, well, pay for it. So what do we do? Well, there's basically 3 options. One, we could keep it through the roof. Two, some vendors perform what's called a reverse consolidation, allowing day 2 to be merged into the day 1 full. While this works great in a data center, in the cloud, we need to compute to perform this, and compute costs money, so therefore, again, increasing that overall TCO. Finally, and most commonly, we see traditional vendors breaking up that backup chain by periodically taking another full backup. While this process does allow us to expire more snapshots, we end up having to store multiple full backups, which, you guessed it, drives up TCO. At Rubrik, we pride ourselves on driving down your cloud TCO, which is why we've announced our latest TCO saving feature, Optimize Snapshot Retention. Let's have a look. Let's take that same data lifecycle policy. Like the others, yes, Rubrik will take that first full backup on day 1, and then those incremental snapshots for the days thereafter. The difference? Once Rubrik detects a new frequency in the policy, we'll start an entirely new incremental chain using the initial full as the base. This frees up those expired backups to be successfully purged from storage. And this process continues, again, creating new and expiring old incremental chains. Once it's time for a monthly, yet another chain is created. Subsequent weekly chains then use our monthly chain as a base, which in turn is based off that first full backup. This hierarchical chaining approach achieves both a lower overall TCO as compared to some of the legacy and native solutions out there, and also ensures snapshot chains are kept to a minimum length, providing optimal performance when it comes time to restore. And hey, don't take my word for it. Visit rubrik.com slash explore to try it out for yourself by taking one of our self-guided hands-on labs to see how your organization can truly become cyber resilient.
