A small startup company is looking to migrate a 4 TB on-premises MySQL database to AWS using an Amazon RDS for MySQL DB instance. Which strategy would allow for a successful migration with the LEAST amount of downtime?
A.
Deploy a new RDS for MySQL DB instance and configure it for access from the on-premises data center. Use the mysqldump utility to create an initial snapshot from the on-premises MySQL server, and copy it to an Amazon S3 bucket. Import the snapshot into the DB instance utilizing the MySQL utilities running on an Amazon EC2 instance. Immediately point the application to the DB instance.
B.
Deploy a new Amazon EC2 instance, install the MySQL software on the EC2 instance, and configure networking for access from the on-premises data center. Use the mysqldump utility to create a snapshot of the on-premises MySQL server. Copy the snapshot into the EC2 instance and restore it into the EC2 MySQL instance. Use AWS DMS to migrate data into a new RDS for MySQL DB instance. Point the application to the DB instance.
C.
Deploy a new Amazon EC2 instance, install the MySQL software on the EC2 instance, and configure networking for access from the on-premises data center. Use the mysqldump utility to create a snapshot of the on-premises MySQL server. Copy the snapshot into an Amazon S3 bucket and import the snapshot into a new RDS for MySQL DB instance using the MySQL utilities running on an EC2 instance. Point the application to the DB instance.
D.
Deploy a new RDS for MySQL DB instance and configure it for access from the on-premises data center. Use the mysqldump utility to create an initial snapshot from the on-premises MySQL server, and copy it to an Amazon S3 bucket. Import the snapshot into the DB instance using the MySQL utilities running on an Amazon EC2 instance. Establish replication into the new DB instance using MySQL replication. Stop application access to the on-premises MySQL server and let the remaining transactions replicate over. Point the application to the DB instance.
on-premises MySQL server -> mysqldump utility -> snapshot -> copy to S3 ->MySQL Utility on EC2 -> import to AWS RDS MySQL -> Establish replication into the new DB instance using MySQL replication -> Stop application access to the on-premises MySQL server -> let the remaining transactions replicate over. -> Point the application to the DB instance.
Installing new SQL software on an EC2 just for the sake of migration threw me off. Getting that much data through an s3 gateway endpoint would get the data from on-prem to the VPC but directly on to an EC2 instance seems ridic to me. So answer is D
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
novice_expert
Highly Voted 3 years agoaws2023a
Most Recent 1 year, 9 months agomegramlak
1 year, 11 months agolollyj
2 years, 4 months agovkruger
2 years, 5 months agolollyj
2 years, 4 months agodamaldon
3 years, 6 months agoSuresh108
3 years, 6 months agoSuresh108
3 years, 6 months agoAesthet
3 years, 7 months agoshantest1
3 years, 7 months agostd2021
3 years, 7 months ago