All Products
Search
Document Center

PolarDB:Roll back an RDS data migration

Last Updated:Jun 20, 2026

This topic describes how to roll back a data migration from an ApsaraDB RDS for MySQL instance to PolarDB.

Roll back migration (Optional)

Before the migration is complete, if you find issues such as data inconsistencies, you can roll back. This operation restores the source RDS instance to a read-write state and the PolarDB cluster to a read-only state.

  1. Log in to the PolarDB console.

  2. Find the target cluster and click the cluster ID.

  3. On the Basic Information page, in the RDS Migration section, click Roll Back Migration.

  4. In the Switch Business Back to Original Database dialog box, select either Switch Back with Endpoints (Connection Changes Not Required) or Switch Back without Endpoints (Connection Changes Required).

    A yellow notification at the top of the dialog box indicates that Data Transmission Service (DTS) does not migrate new databases created on the source instance. After the rollback, reconfigure your SSL settings to use SSL connections. The lower part of the dialog box displays a table that maps the endpoints for the RDS instance and the PolarDB cluster. This table includes mappings for the private endpoint, public endpoint, and classic network endpoint. Endpoint types marked "Not available" are not switched.

    • If you select Switch Back with Endpoints (Connection Changes Not Required), follow these steps:

      1. Select Switch Back with Endpoints (Connection Changes Not Required). The system automatically swaps the endpoints of the RDS instance and the PolarDB cluster. You do not need to modify your application's configuration.

      2. Click OK. The RDS instance becomes read-write, the PolarDB cluster becomes Read-only, and the system synchronizes data from the PolarDB cluster to the RDS instance.

    • If you select Switch Back without Endpoints (Connection Changes Required), follow these steps:

      1. Select Switch Back without Endpoints (Connection Changes Required). After the switchback is complete, you must immediately update the database connection endpoint in your application.

      2. Click OK. The RDS instance becomes read-write, the PolarDB cluster becomes Read-only, and the system synchronizes data from the PolarDB cluster to the RDS instance.

      3. Refresh the page. When the Source RDS Read/Write Status changes to Read/Write, immediately update the database connection endpoint in your application.

Cancel migration (Optional)

  1. Log in to the PolarDB console.

  2. Find the target cluster and click the cluster ID.

  3. On the Basic Information page, in the RDS Migration section, click Cancel Migration.

  4. In the Cancel Migration dialog box, click OK.

    The dialog box includes an optional Disable Binlog on the target instance checkbox. Disabling Binlog can slightly improve write performance but requires a restart of the target instance. You can also disable this option later on the Parameters page.