CCN can interconnect a VPC with another VPC or a local IDC. To use CCN access, you must establish cross-VPC and VPC-IDC interconnections through CCN in advance.
In this scenario, you have used CCN to interconnect the following three networks: vpc-Guangzhou, vpc-Nanjing, and vpc-Shanghai, and plan to migrate a database in the Guangzhou region to the target database. vpc-Nanjing or vpc-Shanghai is selected as the VPC associated with CCN.
Establish interconnections as instructed in Network Instance Interconnection in One Account.
CCN only provides bandwidth below 10 Kbps between all regions free of charge. However, DTS requires a higher bandwidth. Therefore, bandwidth configuration in the link is required.
On the DTS task page, select CCN.
|VPC-Based CCN Instance||CCN instance name.||ccn6-xxxx7d|
|CCN-Associated VPC||Select a VPC whose name and region are different from those of the VPC of the source database. For example, if you use a database in the Guangzhou region as the source database, you should select **vpc-Nanjing** or **vpc-Shanghai** as the **CCN-associated VPC**. Here, **vpc-Nanjing** is selected.||vpc-Nanjing|
|Subnet||Name of the subnet of the selected VPC.
If you cannot pull the subnet, there may be a problem with your account. The account of the CCN-associated VPC must be the same as the migration account.
For example, to migrate a database under account A to account B, you should use account B to create a task. Therefore, the CCN-associated VPC must be under account B.
|Host Address||IP address of the source database server.||172.16.0.0|
|Port||Port used by the source database. Below are the default ports for common databases (if they are modified, enter the actual ports):
Click Test Connectivity. If the test fails, troubleshoot as follows: