Migrate legacy exclusive Data Integration resource groups to Serverless resource groups

Phase 1: Initiate the migration

1. Migration entry point

   1. Log on to the DataWorks console and go to the resource group list page. Switch to the desired region.

   2. In the Resource Groups list, find the exclusive resource group that you want to migrate. Click the icon in the Actions column and select Migrate to Serverless Resource Group to open the migration panel.

2. Confirm migration information and select a new configuration
   In the Migrate to Serverless Resource Group panel, confirm and configure the following information:
   
   
   
   

   • Current resource group: The system displays the type, region, specifications, and fees of the current exclusive resource group. Verify that the information is correct.

   • Serverless resource group: This is the core configuration section for the migration. The system estimates the billing amount for the new resource group based on the usage of the original resource group over the past 30 days.

     Important

     The estimated billing amount is based on the list price on the official website and does not factor in discounts. It is for reference only.

     1. Select a billing method: You can select Subscription or Pay-as-you-go. Choose a billing method based on the resource usage and frequency of the resource group. For more information about Serverless resource group billing, see Serverless resource group billing.

        • Subscription: Suitable for scenarios with stable and frequent resource usage. You must specify the resource group specifications. The minimum specification is 2 CU.

        • Pay-as-you-go: Suitable for scenarios with fluctuating resource usage. After activation, you are billed based on actual usage. You do not need to select specifications in advance.

          Note

          Serverless resource groups also charge a task scheduling fee based on the number of instances that are successfully run each day. For more information, see Billing of Serverless resource groups.

     2. Confirm specifications and fees:
        Based on your original resource specifications, the system recommends a suitable number of Serverless CUs (1 CU = 1 vCPU + 4 GiB memory) and estimates the post-migration fees. Fee changes (savings or additional costs) are highlighted. Pay close attention to these changes.
        
        
        
        

     3. Confirm network configuration:
        Set the default VPC and vSwitch for the Serverless resource group.
        
        
        
        

        Note

        • A Serverless resource group does not have built-in network capabilities. You must attach a VPC to provide network access. For information about network connectivity configuration, see Network connectivity configuration.

        • If the original resource group uses the host binding feature, the Privatezone service is automatically activated on the selected default VPC after migration, and DNS resolution records are created.

        • If the original legacy resource group already has a VPC attached, you can select one of the attached VPCs as the default VPC.

        • If the original legacy resource group does not have a VPC attached, you can select a VPC under your Alibaba Cloud account as the default VPC.

   • View affected tasks:
     The bottom of the panel lists all tasks that will be affected by this migration. Review the list carefully.
     
     
     
     

     Important

     A task appears in this list only on the next day (T+1) after it has been successfully run on the selected resource group.

3. Start the migration

   Click Confirm Migration. The system starts the migration process.

Phase 2: Execute the migration and track the status

After you click Confirm Migration, the resource group goes through the following changes:

1. Create a Serverless resource group

   • The system first creates a new Serverless resource group. This process takes a few minutes. You can close the dialog without affecting the background process.

   • After the Serverless resource group is created, the status of the resource group changes to Pending start.

2. Data source connectivity test

   In the Data Sources section of the migration panel, run a Connectivity test between each data source and the Serverless resource group. You can start the canary release only after all data sources pass the connectivity test. If a data source fails the connectivity test, use the connectivity diagnostics tool for self-service troubleshooting. For information about network configuration between data sources and resource groups, see Network connectivity configuration.

3. Enter the canary period

   • After all data sources pass the connectivity test, click the Start Canary Now button to start the four-day Canary Period. After a few minutes of preparation, the status changes to Migrating (canary) 20%.

   • The canary period lasts four days. During the canary period, tasks are proportionally distributed between the legacy resource group and the Serverless resource group based on the following percentages. The status changes according to the canary percentage.

     Canary phase	Day 1	Day 2	Day 3	Day 4
     Canary percentage	20%	50%	100%	100% (silent)

     During this period, closely monitor the task status and check whether tasks are running successfully.

Phase 3: Manage the migration (canary period operations)

During the canary period, you can manage the migration process at any time.

1. Open the migration management panel

   On the resource group list page, find the resource group that is in the canary migration state. Click the icon in the Actions column and select Serverless Resource Group Migration Management to open the migration panel.

2. Make a decision in the management panel
   The management panel displays detailed migration information and provides the following two core operations:
   
   
   
   

   • Option 1: Complete the switch

     • Description: Click the Stop Canary & Migrate Now button. The system starts switching all tasks from the legacy resource group to the new Serverless resource group. This operation is irreversible.

     • Impact: The switch process may cause real-time tasks that are running to be interrupted for several minutes.

     • Timing: We recommend that you perform this operation during off-peak hours.

   • Option 2: Abort the migration

     • Description: If you encounter any issues during the canary period and need to roll back, go to the Serverless Resource Group Migration Management panel and click Stop & Roll Back.

     • Impact: The system deletes the newly created Serverless resource group and restores everything to the pre-migration state. The original legacy exclusive resource group returns to the Running status, and you can initiate the migration again.

If you do not take any action during the four-day canary period, the system automatically performs the final switch. After the switch is complete, the original exclusive resource group is released, and the Purpose of the resource group in the list is changed to General-purpose.