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
DocumentaçãoData Transfer ServicePreparationsNetwork PreparationInterworking Between local IDC and Tencent CloudVPN Access

VPN Access

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2024-04-30 17:14:44

Overview

To use VPN access, users need to purchase a Tencent Cloud VPC and VPN gateway, establish a tunnel between the VPN and IDC, and connect the local IDC database to the Tencent Cloud VPC through nearby access, then use DTS for transfer tasks.




Directions

For instructions on establishing a VPN tunnel, see Establishing Connection Between VPC and IDC.
In this scenario, the user's VPC network is TomVPC, subnet is Subnet A, with the subnet range of 192.168.1.0/24 . The newly created VPN gateway is TomVPNGW, and the public IP address of the VPN gateway is 203.195.147.82 . The host IP address of the user's IDC database is 10.0.1.8 .


Subsequent Steps

1. After establishing connection between the VPN and IDC, select VPN Access on the DTS configuration task page.
Parameter
Description
Sample Value
VPN Gateway
Name of the VPN gateway created in the VPC.
TomVPNGW
VPC
Name of your VPC.
TomVPC
Subnet
Name of the subnet of your VPC.
Subnet A
Host Address
IP address of the source database server.
10.0.1.8
Port
Port used by the source database. Below are the default ports for common databases (if they are modified, enter the actual ports):

MySQL: 3306
SQL Server: 1433
PostgreSQL: 5432
MongoDB: 27017
Redis: 6379
3306
2. Click Test Connectivity. If the test fails, troubleshoot as follows:
The Telnet test fails. In the created VPC ("TomVPC" in this example), purchase a CVM instance and ping the source database server address from it:
If the address is unpingable:
The source database has a security group or firewall configured.
The SNAT IP address is blocked in the source database.
The port settings of the source database are incorrect.
If the address is pingable: Submit a ticket for assistance.
The Telnet test is passed, but the database connection fails.
The migration account is not properly authorized. Authorize it again as instructed in the corresponding scenario in data migration and data sync.
The account or password is incorrect.
Anterior: Overview of Preparations Related to NetworkPróximo: Direct Connect

Ajuda e Suporte

Esta página foi útil?

comentários