3 ms·
You don't even need to stay away from Aurora ince it's MySql/Postgres SQL API compatible. You would just want to stay away from Aurora specific features like t
by RhodesianHunter 8y ago
You don't even need to stay away from Aurora ince it's MySql/Postgres SQL API compatible.
You would just want to stay away from Aurora specific features like the one in OP.
- koolba 8y agoFeatures 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.
- cookiecaper 8y agoPoint-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.
- awgupta 8y agoWe'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.