You need to enable JavaScript to run this app.
Data Migration Service

Data Migration Service

Copy page
Download PDF
Quick Start
DMS 2.0 Quick Start
Copy page
Download PDF
DMS 2.0 Quick Start
DMS 2.0 is planned to support fully managed and semi-managed modes. Currently, only the semi-managed mode is available. This mode offers a hybrid service between fully managed and self-hosted deployment With this mode, you need to deploy the proxy on your server. Use the proxy to execute migration tasks from the console to migrate data to Volcano Engine TOS This article describes the prerequisites and migration process for transferring data using DMS 2.0 semi-managed mode to help you get started quickly with DMS.​
Prerequisites​
Before using the DMS, ensure that you have registered a Volcano Engine account and completed enterprise verification. For detailed steps, refer to Account Registration and Real-name Authentication.​
Use cases​
Under the semi-managed mode of DMS 2.0, you can migrate local files and data based on the S3 protocol to Volcano Engine TOS. This is suitable for enterprises migrating data from local file systems (localFS) to the cloud, moving S3-compatible cloud storage data to TOS, and transferring data between TOS buckets For more details, see DMS Evolution Plan.​
Workflow​
​
Steps​
Description​
  1. Create migration address​
You must create source and destination addresses in the DMS console to specify the starting location for data migration and the storage bucket for migrated data. For detailed instructions, see Create migration address.​
  1. Create proxy group​
You need to create an agent group in the DMS console for agent management and scheduling. For details, see Create agent group.​
  1. Deploy agent​
Before migrating data, you need to deploy the agent on your server. The deployment includes the following two steps:​
  1. Create an agent in the DMS console.​
  1. Install and start DMS Agent on your local server.​
For detailed instructions, see Deploy agent.​
  1. Create migration task​
When creating a migration task, you need to select a proxy group, migration address, and other details After the task is created, the Agent will perform data migration based on the migration task configuration. For detailed instructions, see Create Migration Task.​
  1. View migration results​
When the migration task status changes from Running to Completed, the migration is finished. You can view the migrated data in the target bucket, check migration statistics, or see details for migrated files. For specific steps, see View migration results.​
​
Last updated: 2026.02.02 11:05:22