Migrating a DRS Task to DataArts Migration

Prerequisites

• A real-time synchronization task has been created in DRS. For details, see
• A real-time data integration environment has been prepared based on Check Before Use.

Preparations

• Assess required DataArts Migration resources.

  Assess the DataArts Migration resources required to run the DRS task. If resources are insufficient, purchase a new migration resource group.

  Consider the following factors during the assessment:

  • Check the number of tables in the DRS task.

    Click the DRS task name to view its details. Choose Synchronization Mapping and view the number of tables. A job in DataArts Migration provides an optimal performance when the number of tables in the job is less than 50.

    Figure 1 Checking the number of tables in a DRS task
    
  • View the maximum amount data that can be synchronized concurrently.

    Go to the DRS task monitoring page and view the monitoring metrics, mainly the Rows Written into Destination Database per Second metric. In addition, check whether the DRS task has a latency.

    A job with 8 CUs in DataArts Migration can synchronize 8,000 records per second. You are advised to configure an independent job for a table with a large amount of data.

    Figure 2 Viewing monitoring metrics
    
    Figure 3 Viewing metric details
    
  • Create jobs based on the customer's requirements.
• Enable network communications.

  Enable communications between the migration resource group and the data source. In the basic information of the DRS task, view the data source configuration. Enable the communications by following corresponding instructions

  Figure 4 Viewing the data source configuration
  

Creating and Starting a Migration Job

1. Create a job.

   Create a migration job based on the prepared job splitting solution. Do not start the job.

2. Obtain the DRS security location.

   Migration jobs need to be started based on the DRS synchronization location to ensure that data transmission is not interrupted and that no data is missing.

   Contact DRS O&M personnel to obtain the security location (a Binlog file name) for DRS task synchronization. Contact MySQL database O&M personnel to query the timestamp of the synchronized DRS Binlog based on the security location and start the migration job based on the timestamp.

3. Before starting a migration job, suspend the DRS job to avoid write conflicts.

   Start the migration job based on the obtained security location. You can set the start time of the migration job to a time earlier (30 minutes recommended) than the security location to avoid data loss.

   For example, if the obtained DRS security location timestamp is 2024-11-29 12:00:00, you can set the time for starting the migration job to 2024-11-29 11:30:00.

   Figure 5 Setting the time for starting the migration job
   

   After the migration job is started and is running stably, you can stop the DRS task.