tencent cloud

Data Transfer Service

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Data Migration
Data Sync
Data Subscription (Kafka Edition)
Strengths
Supported Regions
Specification Description
Purchase Guide
Billing Overview
Configuration Change Description
Payment Overdue
Refund
Getting Started
Data Migration Guide
Data Sync Guide
Data Subscription Guide (Kafka Edition)
Preparations
Business Evaluation
Network Preparation
Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
DTS Service Permission Preparation
Database and Permission Preparation
Configuring Binlog in Self-Built MySQL
Data Migration
Databases Supported by Data Migration
Cross-Account TencentDB Instance Migration
Migration to MySQL Series
Migrating to PostgreSQL
Migrating to MongoDB
Migrating to SQL Server
Migrating to Tencent Cloud Distributed Cache
Task Management
Data Sync
Databases Supported by Data Sync
Cross-Account TencentDB Instance Sync
Sync to MySQL series
Synchronize to PostgreSQL
Synchronization to MongoDB
Synchronize to Kafka
Task Management
Data Subscription (Kafka Edition)
Databases Supported by Data Subscription
MySQL series Data Subscription
Data Subscription for TDSQL PostgreSQL
MongoDB Data Subscription
Task Management
Consumption Management
Fix for Verification Failure
Check Item Overview
Cutover Description
Monitoring and Alarms
Supported Monitoring Indicators
Supported Events
Configuring Metric Alarms and Event Alarms via the Console
Configuring Indicator Monitoring and Event Alarm by APIs
Ops Management
Configuring Maintenance Time
Task Status Change Description
Practical Tutorial
Synchronizing Local Database to the Cloud
Creating Two-Way Sync Data Structure
Creating Many-to-One Sync Data Structure
Creating Multi-Site Active-Active IDC Architecture
Selecting Data Sync Conflict Resolution Policy
Using CLB as Proxy for Cross-Account Database Migration
Migrating Self-Built Databases to Tencent Cloud Databases via CCN
Best Practices for DTS Performance Tuning
FAQs
Data Migration
Data Sync
FAQs for Data Subscription Kafka Edition
Regular Expressions for Subscription
Error Handling
Common Errors
Failed Connectivity Test
Failed or Alarmed Check Item
Inability to Select Subnet During CCN Access
Slow or Stuck Migration
Data Sync Delay
High Data Subscription Delay
Data Consumption Exception
API Documentation
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
Service Agreement
Service Level Agreements

Cloud Connect Network Access

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-04-30 17:19:27

Overview

To use CCN access, users must first use VPN/Direct Connect to connect their local IDC database to Tencent Cloud VPC (e.g., VPC1) through nearby access, and then use CCN to interconnect VPC1 and access VPC2.
In this scenario, you may select CCN under the DTS task account (i.e., the root account of the target database), or under a different account. Using another account's CCN feature is suitable for resource sharing between multiple companies. For example, if the CCN resources belong to the parent company's root account A, and the user's DTS and target database resources belong to subsidiary's root account B, and account B does not have CCN resources, you may use the CCN resources under account A to connect to the self-built database and then carry out the DTS task.
This section takes CCN under the same account as an example. For details on cross-account CCN configuration, see Migrating Data from Self-Built MySQL to TencentDB for MySQL Through CCN.




Network Interconnection Through CCN Access

1. To establish interconnection between a self-built IDC and VPC, see Establishing a connection between VPC and IDC.
2. To establish Interconnection between VPCs, see Connecting network instances under the same account through CCN.
Note:
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.

DTS Task Configuration

1. Purchasing a DTS Task

When purchasing a DTS task, select the region where the VPC (VPC2) is located as the Source Instance Region, that is, region B. Select the region where the target database is located as the Target Instance Region, that is, region C.

2. Configuring a DTS Task

Source Database Settings
Select CCN as Access Type. Select My Account as CCN Instance Account. Select "VPC2" as CCN Associated VPC and choose a subnet as Subnet2. In Target database settings, select Database as Access Type.
CCN-associated VPC refers to the VPC that is connected to DTS through CCN. You need to select a VPC other than the one used for source database access from all VPCs connected through CCN.
When selecting a subnet, if it can't be retrieved, it might be an account issue. The account for CCN-associated VPC and the DTS task account need to be consistent. For instance, to migrate a database instance from account A to account B, you need to create the task with account B. Therefore, CCN Associated VPC must be under account B.
VPC Region: No need to configure, but it's required that the source instance region selected by the user when purchasing a task remains consistent with the VPC region selected in the CCN Associated VPC above. If inconsistent, DTS will modify the region to be consistent.
Target Database Settings
Access type: Select Database.

3. Connectivity Test

If the database and its associated network have configured security access rules, such as security groups, firewall, IP access restrictions, etc., it is necessary to allow DTS IP address, otherwise, connectivity test may fail.

Allow DTS Service IP

1. When the connectivity test fails, follow the instructions in the popup to access "DTS Service IP".
2. Sequentially check if the database has set the following network rules, and if so, allow DTS IP address in the corresponding rules.
Check if the database-associated network layer has set network ACLs or security groups.
Check if the server layer where the database resides has set up a firewall (e.g., iptables rules for Linux systems).
Check if the source database layer has set IP access restrictions.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック