Recently I have spent a lot of time working with existing customers to understand their requirements and help them take full advantage of the Imanis software for their modern data management needs. During these conversations I’ve realized that even customers with whom we’ve been working for some time have not always internalized the full power of our product. There are two topics that crop up more often than others, so I want to discuss these in more depth.
Incremental Forever Backup
“No, you never have to create another full backup after your first one”
“No, this does not impact your ability to recover quickly from a data loss incident”
“No, Imanis Data does not have any issues finding the one specific data object across terabytes or petabytes of data”
This is a fairly accurate representation of my interactions with customers when we discuss the Imanis backup architecture and philosophy. I’ve written in the past about why an incremental-forever architecture is an absolute necessity in the big data world.
Let’s use a concrete example to highlight why this approach works. Assume that you use Imanis Data to back up your Cassandra database on a daily basis and that you keep seven days worth of restore points. A full backup is done the very first time the backup workflow is initiated. All subsequent backups are incremental. On day eight, Imanis Data will delete the very first backup that was created. And this is a very important point: even if the very first full backup has been deleted, Imanis Data never needs to execute a full backup ever again. All the relevant data is still available on the Imanis Data storage cluster. This is because we create a “virtualized full” image for each incremental backup that we do. This is in stark contrast to the traditional approach of periodically doing a full backup and then doing incremental backups during other intervals which creates significantly greater overhead and is uneconomical at big data sizes.
We understand the ultimate goal of any backup and recovery solution is to minimize the impact of a data loss or downtime incident. There are two key capabilities that allow us to help companies meet their recovery point (RPO) and recovery time (RTO) objectives:
Our white paper describes these capabilities and our architecture in quite some depth, and I’d also encourage you to watch our product video so you understand how quickly companies can initiate and execute enterprise level data management workflows.