2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
Currently the best option is to take a backup of your instance with mysqldump. And record the binlog coordinates. Then on a new RDS instance that is sized appropriately, reload the backup and then you can configure this RDS instance to replicate from the original source by using self managed replication with the rds_set_external_master stored procedure.
0
Using DMS would minimize the downtime through replication:
https://aws.amazon.com/premiumsupport/knowledge-center/rds-db-storage-size/ https://docs.aws.amazon.com/dms/latest/userguide/CHAP_GettingStarted.html
답변함 일 년 전
I test. dude, but after restore the backup + DMS, we dispend more than 50 hours to finish with errors ....
관련 콘텐츠
- 질문됨 일 년 전
- 질문됨 7년 전
AWS 공식업데이트됨 3년 전- AWS 공식업데이트됨 일 년 전
If I were to follow technical steps.
It would be like this?
Back up the schemas in this source productive instance.
-"record binlog coordinates" , How do I do it?
restore the backup made in step 1 in a new instance already adjusted to its correct size.
Regarding the next step, do you comment that the destination instance should be receiving replicated data from the source instance, would that be it?
Already in step 5 that he comments on the item rds_set_external_master , you are also telling him to be receiving this configuration, precisely after it, the data that is being received in the source instance, will be replicated to the destination instance.
Was that the plan?