Configuration Parameter | Description |
Service Type | Select Data Migration. |
Creation Mode | New task: Create a task. Create similar task: Quickly create a task with the same configuration as a historical task. The default settings of the new task, including the database type, access mode, billing mode, and migration type, are automatically filled to match the historical task, and can be modified based on actual conditions if needed. |
Billing Mode | Only the pay-as-you-go mode is supported. |
Source Instance Type | Select the source database type, which cannot be changed after purchase. Here, select Distributed Cache. |
Source Instance Region | Select the region where the source database is located. If the source database is self-built, select the region closest to it. |
Target Instance Type | Select based on your target database type. This selection cannot be changed after purchase. Here, select KeeWiDB Storage Edition. |
Target Instance Region | Select the region where the target database is located. |
Version | Currently, only NewDTSV3 is supported. |
Specification | Currently, only Xlarge is supported. |
Tag | Set tag keys and values for migration tasks to facilitate efficient management of multiple tasks through tags. |
Task Name | If users select Name after creation, the task name is the same as the task ID by default. After the migration task is created, the task name can be reset. If users select Name immediately, enter the task name in the input box below. |
Agreement Terms | |
Quantity | Up to 10 migration tasks can be created at a time. |
Configuration Parameter | Description |
Task Name | Specify a business-relevant name to facilitate task identification. |
Running Mode | Immediate execution: The task will be started immediately once the pre-check passes. Scheduled execution: Set a start time for the task. After the pre-check passes, the task is not started immediately, but is started at the scheduled time. |
Automatic Retry | If it is selected, the migration task will automatically retry within the specified time range in case of task interruptions caused by network exceptions or similar issues. No manual intervention is required.
The retry mechanism restarts the data migration from the beginning. During the retry process, any data that was previously migrated to the target end will either be cleared or overwritten. |
Configuration Parameter | Description |
Source Database Type | Source database type selected during creation. It cannot be modified. |
Region | Source database region selected during purchase. It cannot be modified. |
Access Type | Select the network type through which the source database connects to Tencent Cloud. Different access types require different network connectivity operations. For details, see Network Preparation Overview. If the source database is an IDC self-built database/other cloud vendor database, the access method can be set to Public Network/Direct Connect/VPN Access/CCN. Public Network: The source database is accessible through a public IP address. Direct Connect: The source database can connect to Tencent Cloud Virtual Private Cloud (VPC) through DC. VPN Access: The source database can connect to Tencent Cloud VPC through VPN Access. CCN: The source database can connect to Tencent Cloud VPC through CCN. If the source database is a self-built database on CVM, select "Self-Built on CVM" as the access method. If the source database is a TencentDB instance, select "Cloud Database" as the access method. |
Node Type | This parameter is available when Access Type is set to a value other than Cloud database. Select it based on actual conditions. Single-node migration: refers to a cluster architecture with one master node and multiple replica nodes. Cluster migration: refers to a cluster architecture consisting of several shards, with each shard containing several replica nodes. If selecting Cluster migration, fill in the node information. Fill in the addresses and passwords for all shard nodes of the source database cluster (in the format of IP address:Port:Password or IP address:Port). For multiple nodes, fill in each on a new line. When the source database is AWS, you need to enter the PSYNC name (IP address:port:PSYNC name:password or IP address:port:PSYNC name). The PSYNC name refers to the PSYNC command prefix, which needs to be requested from AWS. If the PSYNC command has no prefix, set the Service Provider parameter to "Normal" and migrate it as a normal cluster. It is recommended to fill in the addresses of replica nodes of the source database. Migrating from a replica node avoids affecting business access to the source database. |
Public Network | When Access Type is set to Public network, the following parameters need to be configured. Host address: IP address or domain name of the source database. Port: port used by the source database. Password: The password for the migration account of the source database. |
Self-Built on CVM | When Access Type is set to Self-Built on CVM, the following parameters are required to be configured. CVM instance: The instance ID of the CVM. Port: port used by the source database. Password: The password for the migration account of the source database. |
Direct Connect | When Access Type is set to Direct Connect, the following parameters need to be configured. VPC-based Direct Connect gateway: Only the VPC-based Direct Connect gateway is supported for the Direct Connect access type. Confirm the network type associated with the gateway. VPC: Select a VPC network and a subnet. Host address: IP address or domain name of the source database. Port: port used by the source database. Password: The password for the migration account of the source database. |
VPN Access | When Access Type is set to VPN Access, the following parameters are required to be configured. VPN gateway: Select the VPN gateway instance that connects to the source database network. VPC: Select a VPC network and a subnet. Host address: IP address or domain name of the source database. Port: port used by the source database. Password: The password for the migration account of the source database. |
Database | When Access Type is set to Cloud database, the following parameter needs to be configured. Cross-Account Migration Same account: The source database instance and the target database instance belong to the same Tencent Cloud account. Cross-account: The source database instance and the target database instance belong to different Tencent Cloud accounts. For detailed cross-account operation instructions, see Migrating Between Cloud Database Instances Across Accounts. Cloud database instance: Specify the source database instance ID. Password: Enter the account and password. For the default account, only the password. Note: Tencent Cloud Distributed Cache supports custom account. Enter the custom account connection parameters, such as user@password. |
CCN | When Access Type is set to CCN, the following parameters are required to be configured. When CCN access is used, both same-account CCN access and cross-account CCN access are supported. As this involves complex network configurations, see Migrating Self-built Databases to TencentDB via CCN. Host Network: Select this option based on the actual situation. If the source database is a TencentDB instance, select "Tencent Cloud"; if the source database is a self-built database in an IDC, select "Self-Built IDC"; if the source database is from another cloud vendor, select the corresponding network. Host address: Host IP address of the source database. Port: port used by the source database. Password: The password for the migration account of the source database. CCN instance accounts: My account: The CCN resources and DTS belong to the same Tencent Cloud root account. Other accounts: The CCN resources and DTS belong to different Tencent Cloud root accounts. VPC CCN: Specify the CCN instance name. Access VPC: Select the access VPC and subnet. The access VPC refers to the VPC network that is connected to the migration link within CCN. Select VPC networks associated with CCN, excluding the VPC network to which the source database belongs. Access VPC region: The region of the source database you selected when purchasing the task must be consistent with the region of the access VPC. If they are inconsistent, the source database region will be automatically changed to the VPC access region. |
VPC | When Access Type is set to VPC, the following parameters are required to be configured. VPC: Select a VPC network and a subnet. Host address: IP address or domain name of the source database. Port: port used by the source database. |
Connection Method | Secure Sockets Layer (SSL) connection refers to the use of SSL to establish a secure connection between DTS and the database, encrypting the transfer link. Enabling SSL secure connection may increase the connection response time of the database. Generally, Tencent Clouds private network linkage is relatively secure, and enabling SSL secure connection is not necessary. However, for scenarios using public network, DC, or other transmission methods where higher data security is required, enabling SSL secure connection is recommended. Ensure that SSL encryption is enabled in the database before selecting SSL secure connection. |
Configuration Parameter | Description |
Access Type | Select the access type based on your scenario. The configuration principles for different access types are similar to those of the source database. Note: Migration off the cloud is supported. When the source database access type is set to Cloud Database, the access type of the target database can be set to Public Network/Self-Built on CVM/DC/VPN Access/CCN. |
Node Type | This parameter is available when Access Type is set to a value other than Cloud database. Select based on the actual situation of the target database. Valid values are Single-node migration, Redis cluster migration, and Proxy cluster migration. |
Configuration Item | Description |
Migration Type | Full+incremental migration is selected by default and cannot be modified. This option migrates both the existing historical data from the source database and any new data added during the migration process. |
Migration Objects | Entire instance is selected by default and cannot be modified. |
Enable Key Filtering | Prefix filtering rules can be configured for multi-key commands. For details, see Key Prefix Filtering. |
Target Database Writing Mode | Clear Target Instance: When the source database data is synchronized to the target database, the existing data in the target database will be cleared and then rewritten. Overwrite: When the source database data is synchronized to the target database, the keys from the source database will overwrite the keys in the target database. For the scenario of migrating data from the cloud to on-premises environments, if Overwrite is not selected in the DTS task configuration, the pre-check will fail when existing data is detected on the target database, and automatic retries will not be triggered. |
Enable Target Database Read/Write | Allows DTS or other services to write data to the target database. Target database read/write must be enabled for Distributed Cache migration scenarios. |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan