Delayed Replication w/ Aurora MySQL

0

A customer is interested in implementing Delayed Replication for their Aurora MySQL DB instances as a way to recover quickly from a failed database migration or human error. It looks like this feature was added to RDS for MySQL in August 2018 , but not Aurora MySQL.

  1. Is this something that can be implemented with Aurora MySQL?
  2. For Aurora MySQL customers looking to have a multi-hour delay between replicas, what is the best path forward? Should Aurora Backtrack be instead positioned here?
AWS
asked 5 years ago838 views
1 Answer
0
Accepted Answer

Yes, Aurora backtrack is the solution for the delayed replication however the limit for a backtrack window is 72 hours. Also, there are other limitation.

Backtrack Demonstration: https://www.youtube.com/watch?v=20xXnoQA2j4&feature=youtu.be&t=1468

The RDS MySQL the replication uses the traditional binary log MySQL replication between the MASTER and Read Replicas.

However, in Amazon Aurora replicas share the same underlying storage as the source instance and replication happens on the storage layer (Without binary logs). For a write to be considered durable in Aurora, the primary instance (“master”) sends a redo stream to six storage nodes, two in each availability zone for the storage volume, and waits until four of the six nodes have responded.

AWS
VijayK
answered 5 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions