- Newest
- Most votes
- Most comments
20GB should not take 5 hours. Looks something is not right there.
As you said, there are multiple ways to do the migration with zero or near zero downtime using replication tools. And I would recommend the approaches using DMS or any other tool for production databases to minimize the downtime.
But I see that you prefer the snapshot copy approach. This is what you can try:
-- Enable the cross region automatic snapshot copy of the RDS Instance. This will replicate snapshots and transaction logs to a destination AWS Region of your choice. -- During your outage window, you can just stop the current RDS, wait for the transaction logs to be restored on the other region. You can verify that by checking Latest restorable time and restore the RDS instance using that snapshot in the other region.
Above is the documentation on that. I recommend you to try it on some test environment before you plan this approach for your production instances.
Hi!
Finally what we did was to schedule the maintenance and snapshot copy overnight, strange enough both were full copied under 2 hours. First time they took little above 6 hours.
Thanks for your response, it has very good insight. Never thought of using DMS for this kind of job, in my head it was a tool just for on-premise migrations, but what you suggested is a very good approach, will keep that in mind for the future.
Thanks and best regards!
Relevant content
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago