By using AWS re:Post, you agree to the Terms of Use

Migrating RDS not in VPC (EC2 classic platform) to VPC

0

We have RDS (mysql) instances which are currently on EC2 classic platform. They are not in VPC and we have received notification from AWS to move them to VPC. We are following this guide for migration. However, this process will take about ~20 minutes for us (creating snapshot and then restoring RDS from snapshot in a VPC). During this time, the updates happening to the current RDS will not be propagated to the new RDS. We'll have to do a data migration post this process to recover the lost data. We wanted to know if there is a better way to do this VPC migration. We don't want to loose the data or cause a huge downtime because one of the RDS is very heavily used. Please advise. Also, AWS is asking to complete this migration by August 15th. Will there be any disruptions caused to our existing RDS if we are not able to migrate the RDS by that date. Thanks!

1 Answers
0

Hello,

As pointed out in your own link provided: Using the following alternatives, you can move a DB instance not in a VPC into a VPC with minimal downtime. These alternatives cause minimum disruption to the source DB instance and allow it to serve user traffic during the migration. However, the time required to migrate to a VPC will vary based on the database size and the live workload characteristics.

Alternatives:

AWS Database Migration Service (AWS DMS) – AWS DMS enables the live migration of data while keeping the source DB instance fully operational, but it replicates only a limited set of DDL statements. AWS DMS doesn't propagate items such as indexes, users, privileges, stored procedures, and other database changes not directly related to table data. In addition, AWS DMS doesn't automatically use RDS snapshots for the initial DB instance creation, which can increase migration time. For more information, see AWS Database Migration Service.

DB snapshot restore or point-in-time recovery – You can move a DB instance to a VPC by restoring a snapshot of the DB instance or by restoring a DB instance to a point in time. For more information, see Restoring from a DB snapshot and Restoring a DB instance to a specified time.

I would recommend reaching out to your assigned TAM/SA to plan for the maintenance. They will provide you the necessary resources and also make sure that you get minimal downtime by suggesting you the best way forward.

SUPPORT ENGINEER
answered 5 days ago

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