You can create a migration task using DMS 2.0 Semi\-managed mode to migrate local data to Volcano Engine TOS. After the task is created, the Agent will perform data migration according to the task configuration. This article describes the prerequisites and steps for creating a migration task. ## Prerequisites * The proxy group has been created, and its status is running normally. For detailed instructions, see [Create a Proxy Group](https://www.volcengine.com/docs/6500/1683633). * The Agent has been installed on the local server. For detailed instructions, see [Deploy Agent](https://www.volcengine.com/docs/6500/1683635). * The migration address has been created. For detailed instructions, see [Create Migration Address](https://www.volcengine.com/docs/6500/1683632). ## Notes Each account can create up to 100 migration tasks per region. ## Use cases DMS 2.0 semi\-managed mode supports migrating local files to Volcengine TOS. It is suitable for enterprises transferring data from localFS file systems to the cloud. ## Create migration task 1. Log in to the [DMS Console](https://console.volcengine.com/dms). 2. In the left navigation pane, select **DMS2.0** \> **Migration Tasks**. 3. At the top navigation bar of the **Migration Tasks** page, select a region.

tip

DMS does not currently support cross\-region migration; the migration task and target bucket must be in the same region. To ensure proper execution of the migration task, create the migration task in the region where the target bucket is located.

4. Click **Create Task**. 5. In the **Select Service Type** configuration wizard, set the following proxy parameters. |**Parameter** |**Description** | |---|---| |Task name |Set the migration task name using the following naming rules:

* Be between 3 and 32 characters long.

* Contain only lowercase letters, numbers, or hyphens (\-).

* The name cannot begin or end with a hyphen (\-). | |Service type |The default is **Semi\-managed**. | |Agent group |Select a proxy group. | 6. Click **Next** and select the **Source Address** and **Destination Address**. 7. Click **Next** and configure the following task parameters. |**Parameter** |**Description** | |---|---| |Overwrite policy |Specify the overwrite policy for files with the same name at the source and destination. Description:

* **Do not overwrite**: For files with the same name, no judgment is made; they are skipped directly.

* **Overwrite**: For files with the same name, no judgment is made; the source overwrites the destination directly.

* **Overwrite based on last modified time**: When files with the same name appear at both the source and destination, the decision to overwrite is based on the file’s `lastmodify` field (last modified time). Overwriting occurs only if the source file’s last modified time is later than the destination file’s. | |File storage method |Set the storage class for files migrated to TOS. You can choose **Standard Storage**, **Keep Original Storage Class**, **Infrequent Access Storage**, **Archive Flashback Storage**, **Intelligent Tiering Storage**, **Archive Storage**, **Cold Archive Storage**, or **Deep Cold Archive Storage**. For detailed information about TOS storage classes, see [Storage Classes](https://www.volcengine.com/docs/6349/104493). Below are the parameters for **Keep Original Storage Class** and **Intelligent Tiering Storage**:

* **Keep Original Storage Class**: When migrating to TOS, files will inherit the storage class of the bucket by default.

* **Intelligent Tiering Storage**: When migrating to TOS, files will be stored in the intelligent tiering high\-frequency access layer. | |Soft link migration policy |Migration policy for symbolic link files: You can choose not to migrate symbolic link files or migrate them as independent files to TOS. | |Push migration report |Choose whether to generate a migration report after the data migration is complete and store it in the target storage bucket. | |Target prefix |Set the storage path for data in the bucket.

tip

The storage path must end with a slash (/), for example: test/.

Only DMS Agent version v1.0.9 and above support the target prefix feature. You can run the ./dms_agent -v command to check the current DMS Agent version. If your version is below v1.0.9, updating your DMS Agent is recommended. For details, see Stop, Uninstall, and Upgrade.

| |Filter method |Specify the file migration scope. You can select files to migrate using the following methods:

* **Prefix**: Specify the file migration scope by using file prefixes. After setting the file name prefix, only files with the specified prefix will be migrated. You can set multiple prefixes, with support for up to 10 file prefixes. For example, to migrate all files in the user/data directory, set the file **prefix** to **user/data/** .

* **List file**: Record the names of the files or directories to be migrated in a list file, then upload this list file to object storage. After choosing the filter method for **list file**, you need to enter the storage bucket's Access Key ID and Secret Access Key, then select the list file bucket and the list file itself. Once configuration is complete, only files specified in the list file will be migrated. List file constraints are as follows:

* The list file must be in `txt` format.

* Each line in the list file represents a file; enter multiple files on separate lines.

* The file names in the list file must comply with UTF\-8 encoding rules. | |Migrate files within a specified time range |Filter files for migration based on last modified time. By default, **Migrate All** is selected. Parameter details are as follows:

* **Migrate All**: Migrate all files.

* **Specify time range**: Filter files to be migrated. Three selection methods are available, as described below:

* Specify start date: Only set the start date, leave the end date blank. Only files with the latest modification date after this date will be migrated.

* Specify end date: Only set the end date, leave the start date blank. Only files with the latest modification date before this date will be migrated.

* Specify time range: Set both start and end dates. Only files with the latest modification date within this range will be migrated.

tip

File prefix, list file, and file last modification time use an AND relationship. If you set both filter options (file prefix or list file) and file last modification time, the system will migrate files that meet both conditions: specified files whose last modification time falls within the specified range.

| 8. Click **Next** to review the parameters of the migration task. 9. After verifying the parameters, read and check **Storage Product and Service Terms**, then click **Submit**. ## View migration results Once the task is created, the Agent executes data migration according to the task configuration When the task status changes from Running to Completed, the migration is finished You can view migrated data in the root directory of the target bucket, as well as check statistics for the migration task and details of migrated files as follows: * View migration task statistics On the **Migration Task** page, click the name of the target task to view **Migrated Storage Volume**, **Number of Migrated Files**, **Estimated Remaining Migration Time**, and other details. * View details of migrated files If you enable migration report push when creating a migration task, DMS will generate a migration report after the data migration is complete and store it in the destination bucket. For details, see [View migration report](https://www.volcengine.com/docs/6500/1683631). ## Related operations * Copy tasks On the **Migration Tasks** page, click **Actions** in the target task column and select **...** . **Copy,** on the **Create Task** page, confirm the information is correct and follow the instructions to create the new task. * Edit proxy group On the **Migration Tasks** page, click **Edit proxy group** under **Actions** for the target task, select the proxy group in the **Edit Proxy Group** dialog, and click **OK**.

tip

Only migration tasks in the Queued, Preparing, Paused, or Failed status support editing proxy groups.

* Delete tasks On the **Migration Task** page, click **Delete** in the **Actions** column for the target task. In the dialog box that appears, click **Delete**. * Pause task On the **Migration Task** page, click **Pause** in the **Actions** column for the target task. In the dialog box that appears, click **OK**.

Data Migration Service