Data Management (DMS) is now independently deployed in the United States. Non-US DMS sites no longer support managing US-region instances. Use the US Instance Migration feature to move your US-region instances from a non-US DMS site to the DMS US site in a single operation.
This migration is one-way. Migrating instances back from the US site to the original site is not supported. Review this change carefully before you proceed.
How it works
The migration transfers your US-region instances and their associated configuration to the DMS US site in a single operation.
After migration, the migrated instances are set to Disabled on the non-US site. All management must be done from the US site.
The following data is migrated:
| What gets migrated | Details |
|---|---|
| Instances and physical databases | US-region instances and the physical databases within them |
| User information | All users and roles within the tenant |
| Approval flows | All custom approval templates and approval nodes in Security and Disaster Recovery > Approval Flow |
| Security rules | All security rule configurations in Security and Disaster Recovery > Security Rules |
| User permissions | Permissions for all users under the tenant, database owner information, and access policy configurations |
| Sensitivity level labels | All existing sensitivity level labels for fields on US-region instances |
Prerequisites
Before you begin, make sure that:
Data processing region: Your data processing region is set to China (Hangzhou).
Permissions: The Alibaba Cloud account you use to log in has DMS administrator or DBA role permissions.
US site initialized: Log in to the DMS US site at dms-us-west-1.alibabacloud.com at least once before migrating. This creates a tenant space on the US site. The migration fails if you skip this step.
No active tasks on US instances: Stop or pause any running or scheduled DMS tasks (such as historical data cleanup or task orchestration) on the US-region instances you plan to migrate. The migration disables the instance entry point on the current site, which causes any dependent tasks to fail.
Migrate instances to the US site
Log in to the DMS console V5.0.
In the top navigation bar, choose Data Assets > Instance Management.
On the Instance Management page, click US Instance Migration in the upper-right corner.
In the Important Notification window, click Acknowledge and Start One-Click Migration. The migration task is created. The task status is one of the following: Succeeded, Running, Queued, or Failed.
If the task status is Failed, click Retry Task.
Verify the migration
After the migration task succeeds, verify the results on both sites.
On the non-US site:
Refresh the Instance List page on the DMS non-US site.
Confirm that the migrated instance status is Disabled. Database operations on US-region instances are no longer available from the non-US site.
On the US site:
Log in to the DMS US site.
Open the Instance List page and locate the migrated instance.
Run a SQL query to confirm the instance is accessible and working.
Reconfigure tasks (if needed):
If the original instances had recurring tasks, recreate and configure them on the US site.
FAQ
After the migration, what happens to my US instances on the non-US site?
They are automatically set to Disabled and become read-only. All subsequent management must be done on the US site.
I forgot to pause recurring tasks before migrating. What should I do?
Scheduled runs of those tasks will fail because the instance entry point they relied on is now disabled. Log in to the DMS US site, recreate the tasks, and associate them with the new instance entry point.
Is the migration reversible?
No. This is a one-way operation. Migrating instances back from the US site to the original site is not supported.