- 최신
- 최다 투표
- 가장 많은 댓글
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
Once you promote a read replica it is no longer related to the old source instance.
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?
관련 콘텐츠
AWS 공식업데이트됨 2년 전
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.