Create a similar task - Data Transmission Service - Alibaba Cloud Documentation Center

Manually creating multiple data transmission tasks with similar configurations can be time-consuming and error-prone. The create similar task feature in Data Transmission Service (DTS) lets you create a new task by copying most of the configurations from an existing one. This improves efficiency and reduces the risk of manual errors.

Important

This feature is a shortcut and does not create a full clone. The following key information is not copied and must be reconfigured. If you use this feature incorrectly, the new task may behave differently than expected. Before you use this feature in a production environment, carefully read the configuration details and risk warnings in this document.

Source and destination:
- You can change the source and destination. However, this does not automatically adjust sync objects or other copied parameters. You must check these settings carefully.
- Database password: For security reasons, you must re-enter the password.
Task configuration: Instance parameters in the advanced configuration are reset to their default state.
DTS task instance: You must purchase a new instance for the new task.

Applicable scope

You can see and use the create similar task feature in the Actions column of the task list only if all the following conditions are met.

Supported task types: Data migration, data synchronization, and data validation tasks.
Supported task statuses: The task configuration must be complete. You cannot create a similar task for a task that is in the Not Configured or Staging state.
Other limitations: ApsaraDB RDS does not support Global Active Database (GAD) tasks.

Procedure

This section describes how to use the create similar task feature to quickly create a new task from an existing one.

Go to the Data Transmission Service (DTS) console. In the navigation pane on the left, select Data Synchronization, Data Migration, or Data Verification based on your task type.
On the task list page, find the task that you want to use as a template. In the Actions column, click Duplicate Task.
The system redirects you to the task configuration page and prefills most of the settings. Carefully check and reconfigure the following key information:
- Configure source and destination databases: Re-enter the passwords for the source and destination databases.
- Configure task objects: Check and reset all configuration items. For example, instance parameters in the advanced configuration are reset to their default state.
- Purchase instance: Purchase a new DTS instance.
After you complete all configurations, run a precheck and start the task.

Configuration copy details

When you use the create similar task feature, the system copies and resets related configuration items. The following table describes the rules.

Configuration Category	Copied Configuration Items	Reset Configuration Items
Task Name	The name defaults to the original task's name. Change it to a meaningful name for easier identification. The name does not need to be unique.	-
Configure Source and Destination Databases	The Database Type, Access Method, Instance Region, Replicate Data Across Alibaba Cloud Accounts, Domain Name or IP and Port Number, Database Name, and SSL-encrypted for the source/destination database. Note Although these settings are copied, the connection information for the source and destination databases or the authorization information for cross-account access may have expired. Check them again. Also, confirm that the Database Account has sufficient permissions. When the source database is ApsaraDB RDS for SQL Server, the Database Account defaults to the built-in account `rdsdt_dtsacct` created by DTS. You must change it to the database account of the source ApsaraDB RDS for SQL Server instance.	Database Password for the source/destination database: For security, this is cleared and must be re-entered. Database Account: If the original task used an RDS system account, the username is cleared.
Configure Objects	The list of selected database and table objects, including any configured data filtering conditions or schema and column name mappings. Note The system only copies the list of object names. It does not check if these objects still exist. When the destination is Kafka or RocketMQ, the topic renaming configuration is cleared. Task type (full/incremental). DML/DDL operation types.	-
Advanced Settings	The dedicated cluster of the original task.	Instance parameters: Such as Retry Time for Failed Connections and Retry Time for Other Issues.
Data Verification	All data validation configuration items from the original task. Note The system only copies the list of object names. It does not check if these objects still exist.	-
DTS task instance	The DU configuration items of the original Serverless instance.	You must purchase a new instance for the new task.

Best practices and risks for production environments

Risk warnings

Inconsistent behavior due to lost task object configuration
This feature retains only basic settings such as the task type (full or incremental), the list of database and table objects, DML or DDL operation types, and data validation settings. Critical configurations that affect performance and data correctness, such as instance parameters in the advanced configuration, are reset to their default state. If you do not reconfigure these parameters, the new task's performance and the scope of data synchronized or migrated may differ significantly from the original task, which can lead to unexpected results.
Precheck failure due to changed database objects
This feature copies only the list of database and table names from the original task's configuration. It does not check whether these objects still exist in the source database during the copy process. If some databases or tables were deleted or renamed after the original task was created, the new task fails the precheck because it cannot find the objects.

Best practices

Treat the copied configuration as a template: Always treat a task created with this feature as a prefilled template, not a final product ready for launch.
Thoroughly review configurations: Before you start the task, completely review every configuration step. Pay special attention to the database object selection and task object configuration steps to ensure that all information meets the new task's business requirements.
Monitor performance and load: Creating multiple similar tasks increases the load on the source and destination databases and the pressure on network bandwidth. Ensure that your database resources are sufficient to avoid business disruptions from resource bottlenecks.

FAQ

Can I create a similar task from a released task (instance)?

No, you cannot. After a task (instance) is released, it is deleted from the task list and you can no longer perform operations on it.

Can I create a similar task using an API?

This is not supported.

Can I create an identical instance with one click?

This is not supported.

Why does the precheck report that a database object does not exist after I use the create similar task feature?

This happens because the create similar task feature copies only the list of database and table names from the original task. It does not check in real time whether these objects still exist. If the databases or tables were deleted or renamed after the original task was created, this issue occurs.

Solution: In the object configuration step, manually check and remove the objects that do not exist, or reselect the correct objects.

Why is the new task's performance or behavior completely different from the original task?

This may be because task configuration information was reset to its default state. This feature retains only basic settings such as the task type (full or incremental), the list of database and table objects, DML or DDL operation types, and data validation settings. Other configurations that are critical for performance and data correctness, such as instance parameters in the advanced configuration, are not copied.

Solution: In the task configuration step, carefully check and reset all necessary advanced configuration parameters to match your business requirements.

I have a new synchronization requirement. Should I use this feature to create a new task or modify an existing one?

This depends on your needs. A DTS task typically handles a data stream between one source and one destination.

If the new requirement is to add new databases or tables between the existing source and destination, you can edit the original task directly. Add the new sync objects in the object configuration step.
If the new requirement involves a new source or destination, and the sync logic is similar to an existing task, you should create a new DTS task. The create similar task feature is ideal for this scenario. It helps you quickly complete the basic configuration for the new task.

Does creating a similar task affect the original task?

No, it does not. This feature creates a new task that is completely separate and isolated from the original task. It does not affect the operation or configuration of the original task.