Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Using VPN to Enable Network Communications

Updated on 2025-01-21 GMT+08:00

Before configuring a real-time synchronization task, ensure that the source and destination databases can communicate with the real-time compute resource group that you want to use to run the real-time synchronization task. You can choose a proper network solution based on the network environments of the databases.

This section describes how to use a VPN to enable communications when the database is deployed in an on-premises IDC.

Figure 1 Network diagram

Notes and Constraints

  • The resource group uses a private network segment that cannot overlap with the network segment of the data source. Otherwise, the network cannot be connected.
  • The resource group does not have a public network segment and can only connect to the private network of the data source.

Prerequisites

Preparations

Obtain the network segments of the related objects (including the data source, transit VPC, and resource group).

Table 1 Network segment planning for resources

Resource

Description

Example Private Network Segment

Data source network segment

Private network segment of the data source of the on-premises IDC. Obtain the value based on the site requirements.

192.168.0.0/24

Transit VPC and its subnet

Used for the communications between the data source and resource group. In this solution, a VPC configured for the virtual gateway of VPN and the corresponding subnet are used.

To obtain the VPC and subnet, perform the following operations:

To obtain the VPC and subnet, log in to the VPN console. In the navigation pane on the left, choose Virtual Private Network > VPN Gateways. In the gateway list, locate the virtual gateway used by the on-premises IDC and click its name to view the associated VPC and subnet.

Figure 2 Viewing the VPN gateway

VPC: 10.186.0.0/19

Subnet: 10.186.0.0/24

Resource group VPC

VPC to which the real-time computing resource group belongs. The resource group is created under the resource tenant of the user account and uses the VPC network segment of the resource tenant.

To obtain the VPC, perform the following operations:

Log in to the DataArts Studio console, access an instance, and click the Resources tab. On the Real-Time Resources page, expand the target resource group to view its VPC network segment.

Figure 3 Obtaining the resource group network segment

172.16.0.0/19

Network Configuration Process

  1. Configure a whitelist for the databases of the on-premises IDC.

    Allow the VPC network segment (for example, 172.16.0.0/19) of the migration resource group to access the databases of the on-premises IDC. The method of configuring a whitelist varies depending on the database type. For details, see the official documentation of each database.

    NOTE:

    The ports used by different data sources vary. Configure the ports for security group rules by referring to Which Ports Should I Configure in the Data Source Security Group to Enable Access to the Resource Group.

  2. (Optional) Configure the VPN peer gateway for the on-premises IDC.

    Enable the communications between the database of the on-premises IDC and the VPC network segment (for example, 172.16.0.0/19) of the Huawei Cloud migration resource group by referring to Configuring the Remote Device in the Virtual Private Network Getting Started.

  3. Add the resource group network segment to the local subnet of the VPN.

    To allow VPN to access the resource group network segment, perform the following operations: Log in to the VPN console. In the navigation pane on the left, choose Virtual Private Network > VPN Gateways. In the list, locate the VPN gateway used for connecting to the on-premises IDC and click Modify in the Operation column. In the displayed dialog box, enter the VPC network segment (for example, 172.16.0.0/19) of the migration resource group for Local Subnet.

    Figure 4 Adding a local subnet

  4. Create a real-time network connection (VPC peering connection) for migration.

    To connect the transit VPC to the real-time resource group VPC, you can create a VPC peering connection between the two VPCs using the resource management function provided of DataArts Studio.

    Log in to the DataArts Studio console, access an instance, and click the Resources tab.

    Figure 5 Creating a network connection

    On the Real-Time Network Connections tab page, click Create. In the displayed Create Network Connection dialog box, set required parameters.

    Table 2 Parameters for creating a network connection

    Parameter

    Description

    Connection Name

    Name of the network connection

    Only letters, digits, and underscores (_) are allowed.

    Resource Group

    Resource group that can communicate with the specified VPC.

    If you do not select a resource group, you can bind resource groups to the connection after the connection is created by clicking More in the Operation column and selecting Bind Resource Group.

    VPC

    VPC that can communicate with the resource group

    In this solution, the resource group network segment and the transit VPC are connected through a VPC peering connection. Therefore, you must select a transit VPC (for example, 10.186.0.0/19).

    Subnet

    Subnet of the transit VPC, for example, 10.186.0.0/24

    Routing Table

    Routing table associated with the subnet. When the connection is bound to a resource group, routing information of the resource group is added to the routing table. You do not need to set this parameter.

    When the connection is bound to a resource group, a route to the resource group VPC network segment is added to the routing table. The route connects the resource group network segment to the transit VPC.

  5. Add a route to the data source network segment for the real-time network connection (VPC peering connection).

    Locate the real-time network connection created in step 4, click More in the Operation column and select Add Route. In the displayed dialog box, enter the private network address of the database of the on-premises IDC, for example, 192.168.0.0/24.

    Figure 6 Adding route 1
    Figure 7 Adding route 2

  6. (Optional) For MRS data sources, perform the following extra operations to enable network communications:

    After creating a real-time network connection and binding it to a resource group, click More in the Operation column and select Modify Host Information. In the displayed dialog box, enter the IP addresses and domain names of all nodes in the MRS cluster as prompted.

    Figure 8 Modifying host information
    NOTE:

    To obtain the IP addresses and domain names of the nodes in an MRS cluster, perform the following steps:

    • Open the MRS page, access the MRS cluster, click the Nodes tab, and expand all node groups to view the IP address and name (domain name) of each node.

      Add the IP addresses (1 in the figure) and domain names (2 in the figure) of all nodes and separate them by pressing Enter.

      Figure 9 Obtaining the IP addresses and domain names of the nodes in the MRS cluster
    • Log in to an MRS cluster node by referring to Logging In to an MRS Cluster Node and run the cat /etc/hosts command to list the IP addresses and domain names of all nodes.

  7. Test the network connectivity.

    In a DataArts Studio workspace, create a data connection and a real-time migration job, and select the corresponding data connection and resource group to test the connectivity. For details, see Creating a Real-Time Migration Job.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback