- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Once a read replica is promted to master it will cut its ties with the inital master and now is orphaned. There is no native way to replicate the data back.
I believe AWS docs recommend that you follow the same process but in reverse.. Create a new read replica from Account B back to Account A and then promote account A to be the Master again. At which point re-create the read replica in Account B.
Hi,
AWS RDS offers PITR (Point-In-Time-Recovery) features that will help you achieve what you want : see https://repost.aws/fr/knowledge-center/backup-coordinates-pitr
Also have a look at https://docs.aws.amazon.com/aws-backup/latest/devguide/point-in-time-recovery.html#point-in-time-recovery-supported-services
Best,
Didier
Hello.
How about temporarily stopping the application and migrating the data using something like mysqldump?
In this case, the application will be stopped for a period of time, but the data can be moved reliably.
I think there are other methods such as using DMS etc. to perform replication.
https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Introduction.html
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
@Gary thanks for the answer can you provide the doc link where it is mentioned , that will be helpful
Of course.. I believe it was in this blog. https://aws.amazon.com/blogs/database/use-cross-region-read-replicas-with-amazon-relational-database-service-for-sql-server/#:~:text=With%20cross%2DRegion%20read%20replica,to%20a%20new%20AWS%20Region.
under clean up subject heading