Learn how RDS point-in-time recovery works both behind the scenes and how to use it to help in real-life disaster recovery situations.
- [Narrator] Let's imagine that I've just made a terrible mistake and deleted some important data out of the source, 'MySQL' database. We have the read replica, but that stays in sync with the source, so it's really not that much help. What am I going to do? Well, remember that when we set up the RDS database, we selected that it should keep seven rolling days of snapshots that are taken nightly. So, that means I can at least get back to last night. But usually, that's not good enough. We need something a little sooner. Fortunately, RDS has our back here. If we have the MySQL highlighted and go to Instance Actions, you'll see 'restore to point in time.' This is a really helpful feature that has genuinely saved me in real life a few times.
You see that we have some options here. 'Use latest restorable time', which is just a few minutes ago. And 'use custom restore time', which appears to let us put in any time that we want. How does RDS accomplish this? Well, we have the nightly backups, but to get something in between, RDS looks at the actual change logs of the database engine. So, it goes to the most recent backup that we have and replays the changes through the day up to the point in time you specify. So, it can get really specific. If we leave this at latest restorable time and scroll down, you see that the rest of what we have to fill in is just to say, 'what is our new instance going to be?' Remember that RDS doesn't do restorations in place, but it creates a new instance for you to log into.
So, you can see the name of the source here. And I could just copy this, (mumbles) restore here so I know which is which. I can leave everything else the same or I could change instance type or change some of the other configurations. But really, I don't need any of that and here I click, 'Launch DB instance.' Now, RDS is creating a new instance based on my previous one at the exact point in time that I specified. When I need to get the data back, all that I need to do is created a new connection using MySQL workbench to go to that database and extract the new important data that I accidentally deleted.
I can either, from there, manually restore it to the original database, or if I like, I could take my applications that are connected to the source and reroute them to the new restoration database.
Join AWS architect Brandon Rich and learn how to configure object storage solutions and lifecycle management in Simple Storage Service (S3), a web service offered by AWS, and migrate, back up, and replicate relational data in RDS. Find out how to leverage flexible network storage with Elastic File System (EFS), and use the new AWS Glue service to move and transform data. Plus, learn how Snowball can help you transfer truckloads of data in and out of the cloud.
- What is data management?
- AWS S3 basics
- S3 bucket creation
- S3 upload and logging
- S3 event notifications
- S3 data lifecycle configuration
- Working with Amazon Elastic Block Store volumes
- Creating and mounting an EFS
- Creating an AWS RDS instance
- RDS backup and recovery
- Moving data with AWS Database Migration Service
- Moving data with Data Pipeline and Glue