3 ms·
At the risk of being repetitive, I just want to point out, this is not "amazing new technology". Point-in-time database restores are provided by maintaining dat
by cookiecaper 8y ago
At the risk of being repetitive, I just want to point out, this is not "amazing new technology". Point-in-time database restores are provided by maintaining database write logs and should be a normal part of any serious backup/restore process, not just because they allow for point-in-time restores, but because they're an integral part of standard database recovery situations. They're used to replay changes made between the last backup snapshot and the time of the incident that warrants recovery.
AWS may have contributed some new technologies, but for the most part, they've just wrapped things up in a GUI. I'm not denigrating that as a valid market niche to fill, but people should know that there are non-AWS solutions for virtually everything that AWS provides, and that your company's admins probably already employ a good portion of them.
- inyourtenement 8y agoRDS already has PIT restore, and yes there is a UI for it. This is different. They would not be making an announcement for PIT restore. A good question is, how is it different. With PIT restores, they create a new instance from snapshot and play back the logs up to the relevant point. With this Aurora-only feature, they take advantage of Aurora's storage capabilities, and rewind the same database to a previous point. No new instance, no cold recovery from snapshot, no long log replay.
- cookiecaper 8y agoYeah, I know that Aurora already had point-in-time restore. It's disingenuous to pretend like this is something different. This is, at best, an upgrade to Amazon's processes to make the restore process smoother in the ways you've mentioned.
- awgupta 8y agoAs the previous commentor said, this isn't point in time restore or a change in our processes. It is a change to our database and storage engine to mark regions of log-structured storage as if they did not occur. That's why we can complete a Backtrack in a few seconds - we're just moving some pointers around and restarting the database.