Which solution should a database specialist use for a timely migration?
Perform a full backup of the source database to AWS Snowball Edge appliances and ship them to be loaded to Amazon S3. Use AWS DMS to migrate change data capture (CDC) data from the source database to Amazon S3. Use a second AWS DMS task to migrate all the S3 data to the target database.
Perform a full backup of the source database to AWS Snowball Edge appliances and ship them to be loaded to Amazon S3. Periodically perform incremental backups of the source database to be shipped in another Snowball Edge appliance to handle syncing change data capture (CDC) data from the source to the target database.
Use AWS DMS to migrate the full load of the source database over a VPN tunnel using the internet for its primary connection. Allow AWS DMS to handle syncing change data capture (CDC) data from the source to the target database.
Use the AWS Schema Conversion Tool (AWS SCT) to migrate the full load of the source database over a VPN tunnel using the internet for its primary connection. Allow AWS SCT to handle syncing change data capture (CDC) data from the source to the target database.
Explanations:
AWS Snowball Edge allows transferring large data volumes to S3 with minimal bandwidth usage. DMS can then migrate the change data capture (CDC) after the initial load, reducing downtime during migration.
Incremental backups using Snowball Edge for syncing CDC would result in more complexity and a longer timeline. AWS DMS is more efficient for real-time CDC migration.
Migrating 80 TB over a VPN connection using the internet for the primary connection would take a significant amount of time, causing unnecessary downtime.
AWS SCT is designed for database schema conversion, not for migrating data. It doesn’t support syncing CDC data during the migration process.