DTS instances that use the classic network will be phased out - Data Transmission Service

Data Transmission Service (DTS) will no longer support the classic network, and DTS instances that use the classic network will be phased out.

Background information

Since the Alibaba Cloud public cloud was released in 2011, the classic network architecture has been used to host Elastic Compute Service (ECS) instances and serve numerous users in the cloud. In 2014, Alibaba Cloud released Virtual Private Cloud (VPC)-based cloud services, which are more secure, consistent, flexible, and performant than classic network-based cloud services. After years of development, the VPC architecture has become the default choice of cloud service users. Therefore, Alibaba Cloud decided to officially phase out DTS instances that use the classic network.

Check affected instances

In September 2024, DTS will notify you of the affected DTS instances by internal message, email, and text message. We recommend that you check the affected instances in the notifications and take measures at the earliest opportunity.

Dates and impacts

End of sale from 00:00:00 on September 24, 2024
- You can no longer purchase data synchronization or migration instances whose source or destination database is deployed in the classic network.
- You can no longer purchase change tracking instances that use the classic network.
  Note
  Change tracking instances that use the classic network can be purchased only in the previous version of the DTS console.
End of renewal and configuration change from 00:00:00 on October 30, 2024
You can no longer renew data synchronization or migration instances whose source or destination database is deployed in the classic network and change tracking instances whose Network Type is set to Classic. You can no longer change the configurations of these instances.
End of service from 00:00:00 on February 28, 2025
- You can no longer use DTS to access databases that are deployed in the classic network, and data synchronization or migration instances whose source or destination database is deployed in the classic network will be abnormal.
- You can no longer configure Classic Network Endpoint for change tracking instances, and clients that consume tracked data from classic network endpoints will be abnormal.

Solutions

Scenario 1: A data synchronization or migration instance whose source or destination database is deployed in the classic network

Migrate the database from the classic network to a VPC and set the Access Method parameter to Express Connect, VPN Gateway, or Smart Access Gateway for the database. Then, add the CIDR blocks of DTS servers to the security settings of the database and restart the DTS instance.

Note

For more information about how to migrate Alibaba Cloud resources from the classic network to VPCs, see EOL notice for Alibaba Cloud resources in the classic network.
For more information about the CIDR blocks of DTS servers, see Add the CIDR blocks of DTS servers.

Scenario 2: A change tracking instance that uses the classic network

Purchase a change tracking instance whose Network Type is VPC, consume the tracked data from the VPC Endpoint, and then release the change tracking instance that uses the classic network. For more information, see Overview of change tracking scenarios and Release DTS instances.

Scenario 3: A DTS instance that runs on a machine in the classic network

If you have a DTS instance that runs on a machine in the classic network, such as an instance whose source database is a PolarDB-X V1.0 instance, contact DTS technical support.