How to re-sync back after MySQL read replica is promoted

0

We have a cross-region MySQL RDS replication and I believe if we promote the replica server it becomes a standalone master server. Now how to bring back the sync between them again, Instead of creating new read replicas for the new master, is there any other possibilities? Can we use mysql.rds_set_external_master to sync back? any supporting document would be much appreciated.

Sravan
asked 9 months ago209 views
2 Answers
0

Hi, the proper Recovery Failure using Read Replicas is detailled in section "Implement Failure Recovery" of https://aws.amazon.com/blogs/aws/amazon-rds-for-mysql-promote-read-replica/ and in final sections of https://aws.amazon.com/blogs/database/implementing-a-disaster-recovery-strategy-with-amazon-rds/

I also highly recommend the reading of this foundational wp "Disaster recovery options in the cloud": https://docs.aws.amazon.com/pdfs/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-workloads-on-aws.pdf#disaster-recovery-options-in-the-cloud

All AWS-recommended DR models are in there

Best,

Didier

profile pictureAWS
EXPERT
answered 9 months ago
  • The document just shows how to promote the read replica but I'm looking at how to re-establish the sync back with old master.

0

Once you promote a read replica it is no longer related to the old source instance.

AWS
MODERATOR
philaws
answered 9 months ago
  • Yes, but can we have the sync back again? Before promoting the read replica note the binary_log_file_name, and binary_log_file_location of the master and then once the read replica becomes a standalone master, can we re-establish the replication sync using the mysql.rds_set_external_master stored proc?

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