News for hackers. Stuff that matters.

A comment on Amazon Aurora Backtrack. Parent comment

Re:Amazon Aurora Backtrack by koolba on Thursday May 10, 2018 @12:14PM (#17040218)
Features like database rewind aren’t something that would be bound to your core app structure either. While you could structure business process’s around it, it’s more of a shit hits the fan restore scenario, not a daily or weekly action.

Replicating it on a different platform could also be fine with a combination of logical and physical backups.

[ Parent | on HN ]
Re:Amazon Aurora Backtrack by cookiecaper on Thursday May 10, 2018 @04:45PM (#17042804)
Point-in-time database restores are a best practice that is provided by maintaining database write logs for the timeframe that you expect to have point-in-time restoration for. You don't have to use Aurora to get them, Aurora just has the clicky buttons to make it a clicky-button matter. Any serious DBA should know how to do this without Amazon's platform wrapping it up in a GUI.
[ Parent | on HN ]
Re:Amazon Aurora Backtrack by awgupta on Tuesday May 15, 2018 @10:15PM (#17079510)
We've had point in time restore for quite some time. Backtrack is different. It moves you to a different point using the same instance. Since we don't do destructive writes to blocks (it is log-structured storage), we can simply mark a portion of the log as "ignored". It is a server feature, not a UI enhancement.
[ Parent | on HN ]