00:06
Today I wanted to talk to you a little bit about EverPure volume snapshots and specifically how they can simplify database operations. Generally, database teams I know don't struggle with backups. They have scheduled backup windows, plenty of backup automation, and hopefully they're running regular restores to ensure their backups are actually recoverable.
00:26
What I do see teams struggling with today though are the, size of data nature of backup and restore-based workflows. Specifically things like dev test refresh, you know, pulling down production data to your dev and test environments on a regular basis, creating replica servers for HADR purposes, be it on premises or in the cloud, and things like post-incident data analysis, you know,
00:47
recovering that database after the fact to see what went wrong. They also struggle with ever-growing databases. As they get larger and larger, backups can take longer to run, restores can take even longer, and things like logical database checks and validations can't happen inside of a regularly scheduled maintenance window anymore.
01:06
Over the next few minutes, you're gonna learn how EverPure volume snapshots can help either reduce or completely remove the size of data operations from your workflows and even increase innovation. Traditional backup and restore workflows are built around size of data operations. Every time you execute one of these operations, be it a backup or a restore, you've got to
01:26
read and write all of the data, and every new workflow is another copy of that data. Every operation also pulls that same data across the network, either to your, your target destination or to your backup destination, whatever it is. This model can work fine until the estate grows or development velocity increases. So suddenly you have multi-terabyte databases that are taking a lot longer
01:51
to back up and restore. You've got more and more databases across more and more environments that can be very, very taxing on a network. And then more frequent dev refresh cycles. You wanna get features out as fast as you can in your organization, but people are waiting around for the dev environment to refresh 'cause the restores are taking too long.
02:10
That's really not ideal. Snapshots can help avoid these size of data bottlenecks. They're metadata only a near instant to take. It's about updating pointers to blocks, not rewriting the whole database. They're also very space efficient.
02:24
Only the changed blocks will consume additional capacity over time. They also offer data consistency across multiple volumes through something called protection groups. So if you have a database that spans multiple volumes, which is extremely common, you can snap it all at one time and recover to a specific point in time.
02:44
Snapshots don't completely replace backups. They really supplement them by speeding up and adding efficiency to your existing workflows, increasing recovery coverage for large databases. So if you've got a database that takes a long time and you can only take fulls, with snaps you can take more frequent backups to supplement those fulls.
03:03
And finally, by enabling quick rollback after a bad deployment. Imagine if you could recover from a bad deployment in a matter of seconds. Snapshots keep backups focused on what they're best at, which is long-term retention and fine grain recovery. They can also be the key to innovation in your organization, which might sound a little bit weird.
03:22
But they don't just remove challenges and add efficiency, they can open new possibilities. Think about the sorts of things you could do if restore time and capacity were no longer a concern. Are you looking for a way to reduce impact on critical production systems for your new AI initiative?
03:39
Snapshots might be a way to do that. Have you ever delayed upgrading a database system solely from concerns about restoring the databases involved? Snapshots can help there as well. Want to do something brand new, like create a self-service process for developers and teams
03:54
to spin up test systems and try new ideas? With snapshots, this can be a reality. Snapsh-snapshots take some of these ideas from it'll take days to restore the data to let's try it this afternoon. Now, snapshots exist on a lot of different platforms, but EverPure snapshots do have some
04:14
unique benefits. First, they're immutable by default. You can't change them. Once you take a snapshot, the snapshot is set. Nobody can go in and alter that. they're extremely space efficient, like I'd mentioned before.
04:27
Only change blocks consume space, so there's very, very little storage overhead to taking snapshots, and the creation and recovery is near instant. They're portable between arrays and in the cloud, and they have a extremely efficient transport mechanism to replicate the snapshots around. And there's also many op-options for integration into existing workflows.
04:49
there's a REST API, there's a Python client, PowerShell, obviously there's a UI as well. Backups are still how you meet your long-term retention and fine grain point-in-time recovery goals. Snapshots on EverPure are how you replace or supplement the backup and restore steps inside your operational workflows. And maybe more importantly, they're how you can unlock brand-new workflows you never
05:14
thought were even possible. They allow you to stop worrying about capacity and time constraints and start worrying about how you can use your data. If you'd like to learn more about how snapshots can fit into your environment, check out the resources linked to this video.
05:29
Thanks for watching.