Before you use DataWorks to synchronize data from an ApsaraDB for OceanBase cluster to an AnalyticDB for MySQL V3.0 cluster, you must refer to the operations in this topic to prepare the configurations such as the network environments, whitelist, and account permissions for data synchronization.

Prerequisites

Before you configure data sources, make sure that the following operations are performed:
  • Prepare data sources: An ApsaraDB for OceanBase cluster and a destination AnalyticDB for MySQL 3.0 cluster are prepared.
  • Plan and prepare resources: An exclusive resource group for data integration is purchased and configured. For more information, see Plan and configure resources.
  • Evaluate and plan the network environment: Before you perform data integration, connect data sources to exclusive resource groups for Data Integration based on your business requirements. After data sources and exclusive resource groups for Data Integration are connected, you can refer to the operations in this topic to configure access settings such as vSwitches and whitelists.
    • If data sources and exclusive resource groups for Data Integration reside in the same region and virtual private cloud (VPC), they are automatically connected.
    • If data sources and exclusive resource groups for Data Integration reside in different network environments, you must connect data sources and resource groups by using methods such as a VPN gateway.

Background information

Before you synchronize data from the source to the destination, make sure that the data sources are connected to an exclusive resource group for Data Integration. In addition, you must create an account and authorize the account to access the data sources.
  • Configure whitelists for the data sources
    If the data sources and exclusive resource group for Data Integration reside in the same VPC, you must add the CIDR block of the exclusive resource group for Data Integration to the whitelists of the data sources. This ensures that the exclusive resource group for Data Integration can be used to access the data sources. VPC connections
  • Create an account and grant permissions the account

    You must create an account that can be used to access the data sources, read data from the source, and write data to the destination during the data synchronization process.

Limits

ApsaraDB for OceanBase is a distributed relational database that can integrate data distributed in multiple physical databases into a unified logical database. However, you can synchronize data of only one physical ApsaraDB for OceanBase database to an AnalyticDB for MySQL cluster in real time.

Procedure

  1. Configure a whitelist for the ApsaraDB for OceanBase cluster.
    Add the CIDR block of the VPC where the exclusive resource group resides to the whitelist of the ApsaraDB for OceanBase cluster.
    1. View and record the elastic IP address (EIP) and CIDR block of the exclusive resource group.
    2. Add the elastic IP address (EIP) and CIDR block of the exclusive resource group for data integration to the whitelist of the ApsaraDB for OceanBase cluster. For more information, see Configure a whitelist for an ApsaraDB for OceanBase cluster.
  2. Create an account and grant the required permissions to the account.
    You must create an account to log on to the database of the ApsaraDB for OceanBase cluster. You must grant the required permissions to the account. For more information, see Create an account.

What to do next

After data sources are configured, the source data source, destination data source, and exclusive resource group for Data Integration are connected. Then, the exclusive resource group for Data Integration can be used to access the data sources. You can add the source data source and destination data source to DataWorks, and associate them with a data synchronization solution when you create the solution.

For more information about how to add a data source, see Add a data source.