이 페이지는 귀하의 언어로 번역되지 않았습니다. 번역 요청

Step 1: Create an AWS DMS Replication Instance

PDF

An AWS DMS replication instance hosts the software migrates data between the source and target. The replication instance also caches the transaction logs during the migration. The CPU and memory capacity of the replication instance influences the overall time needed for the migration. Make sure that you consider the specifics of your particular use case when you determine the size of your replication instance. A full load task consumes a lot of memory if it is run multithreaded. For more information, see Choosing the right replication instance for your migration.

For our use case, we have a limited time window of 8 hours to complete the full load, and the sales table that includes 197 GB of data. Our goal is to fit into the 8 hour window. Therefore, we scale the replication instance to accommodate these requirements.

Each type of instance class has different CPU, memory, and I/O capacity. Sizing the replication instance should be based on factors like data volume, transaction frequency, large objects (LOBs) within storage of the data migration, and so on. We initially chose a DMS t3.medium instance running the latest AWS DMS engine version. This instance completed the migration in 18 hours. We then upgraded to a DMS c5.12xlarge instance. This instance size, combined with the proper task configuration, brought the full load time to under 8 hours.

We also upgraded the storage of the replication instance to 200 GB, and as a result, 600 IOPS were available for our replication instance. By default, DMS allocates 50 GB of storage to a replication instance. This may not be sufficient for use cases where more tasks are running on same replication instance or when running tasks with parallel load for large tables. With 600 IOPS, we saved several minutes of migration time. For more information about storage volume performance and burst I/O credits, see General Purpose SSD (gp2) volumes.

Because we replicate production data in this walkthrough, we use the Multi-AZ deployment option for our replication instance for high availability. Also, we didn’t make this replication instance publicaly accessible for additional security.

For information about best practices for using AWS DMS, see Database Migration Service Best Practices.

To create an AWS DMS replication instance

1. Sign in to the AWS Management Console, and open the AWS DMS console.

2. Choose Replication instances, then choose Create replication instance.

3. On the Create replication instance page, enter the following information.

   Parameter	Action
   Name	Enter oracle-s3-migration-replication-instance. If you use multiple replication servers or sharing a user, choose a name that helps you quickly differentiate between the different servers.
   Description	Enter Replication instance that suports Oracle to S3 data lake migration. You can change the description to fit your use case.
   Instance class	Choose dms.c5.12xlarge.
   VPC	Choose the virtual private cloud (VPC) where AWS DMS launches your replication instance. If possible, select the same VPC in which either your source or target database resides (or both).
   Multi AZ	Choose Yes.
   Publicly accessible	Turn off this option.

4. Choose Create.