Which solution meets the company’s requirements?
Shut down applications over the weekend. Create an AWS DMS replication instance and task to migrate existing data from SQL Server to Aurora MySQL. Perform application testing and migrate the data to the new database endpoint.
Create an AWS DMS replication instance and task to migrate existing data and ongoing replication from SQL Server to Aurora MySQL. Perform application testing and migrate the data to the new database endpoint.
Create a database snapshot of SQL Server on Amazon S3. Restore the database snapshot from Amazon S3 to Aurora MySQL. Create an AWS DMS replication instance and task for ongoing replication from SQL Server to Aurora MySQL. Perform application testing and migrate the data to the new database endpoint.
Create a SQL Server native backup file on Amazon S3. Create an AWS DMS replication instance and task to restore the SQL Server backup file to Aurora MySQL. Create another AWS DMS task for ongoing replication from SQL Server to Aurora MySQL. Perform application testing and migrate the data to the new database endpoint.
Explanations:
This option suggests shutting down applications to migrate existing data, which leads to downtime. The requirement is to minimize downtime, making this option unsuitable.
This option utilizes AWS DMS to migrate existing data and set up ongoing replication, allowing for minimal downtime. Applications can continue running while the migration occurs, with only a brief cutover needed for final synchronization.
Creating a database snapshot and restoring it to Aurora MySQL is not a direct method for migrating to Aurora MySQL. Additionally, while it mentions ongoing replication, the initial snapshot process is not conducive to minimizing downtime as required.
This option involves creating a SQL Server native backup and restoring it to Aurora MySQL. It does not address the ongoing replication effectively and may introduce significant downtime during the restore process, contrary to the requirement for minimal downtime.