FAQ
This topic answers common questions about migrating from ApsaraDB RDS for MySQL to PolarDB-X 2.0 Standard Edition.
Before migration
Do I need to purchase a PolarDB-X 2.0 Standard Edition instance before starting the migration?
No. Purchase and create the destination instance as part of the migration process — you can provision it with the same data as the source instance during migration, rather than in advance.
Do the destination instance node specifications need to match the source instance?
No. Select node specifications based on your business requirements. For best performance, choose specifications equal to or higher than those of the source ApsaraDB RDS for MySQL instance.
Migration impact
Does the migration interrupt the source ApsaraDB RDS for MySQL instance?
No. The source instance continues running normally throughout the migration. Data synchronization does involve query operations, which may have a minor impact on query performance of the source instance.
What is the downtime for a smooth migration?
No data is lost and service downtime is less than 10 minutes during a smooth migration. During this window, the service is suspended and no incremental data is generated, but the database itself continues to run. You can also roll back the migration if needed.
Canceling migration
What happens if I cancel the migration?
When you cancel the migration:
The data synchronization link between the source and destination instances is disconnected.
The source instance is no longer associated with the destination instance.
The destination instance becomes readable and writable.
The destination instance is not automatically released. Release the instance promptly if you no longer need it, to avoid additional charges.
Switching over
Do I need to update my application's endpoint configuration after switching over?
It depends on which switchover option you selected:
| Switchover option | Application change required? |
|---|---|
| Switch with Endpoints (Connection Changes Not Required) | No. The system automatically swaps endpoints between the source and destination instances. |
| Other switchover options | Yes. Update your application configuration to point to the new PolarDB-X 2.0 Standard Edition endpoint. |
I selected "Switch with Endpoints (Connection Changes Not Required)." Why does the PolarDB-X 2.0 Standard Edition instance show a new endpoint after migration?
Only endpoints that exist on both the source and destination instances are swapped. By default, only the primary private endpoints are swapped. To swap other endpoint types (such as public endpoints), create those endpoints on both instances before the switchover.
To add a public endpoint to PolarDB-X 2.0 Standard Edition, see Apply for or release a public endpoint.
To add a public endpoint to ApsaraDB RDS for MySQL, see Apply for or release a public endpoint.
Are read-only instance endpoints swapped when I use the "Switch with Endpoints" option?
No. The Switch with Endpoints (Connection Changes Not Required) option does not swap endpoints for read-only instances.
After switching over, I can't connect to PolarDB-X 2.0 Standard Edition — or I can connect but can only read, not write. Why?
After endpoints are swapped, old endpoint information may remain cached in the Domain Name System (DNS) until the cache expires. Flush the DNS cache on your server to resolve the issue.
The "Complete Migration" button has disappeared from the PolarDB-X console. What happened?
Once you complete the Complete Migration step, the button is hidden to prevent the action from being repeated. No further action is needed.
Post-migration
Do I need to re-create accounts, passwords, or whitelists on the destination instance?
No. The destination instance automatically inherits the same accounts, passwords, databases, IP address whitelists, and required parameters from the source instance.
Encryption and compatibility
Can I migrate from a source instance with Secure Sockets Layer (SSL) encryption enabled?
Yes. If SSL encryption is enabled on the source instance endpoints and you use the Switch with Endpoints (Connection Changes Not Required) option, make sure that SSL encryption is enabled on the destination PolarDB-X 2.0 Standard Edition endpoints.
Can I migrate from a source instance with transparent data encryption (TDE) enabled?
Yes. Migration from a TDE-enabled ApsaraDB RDS for MySQL instance is supported.
Can I migrate across MySQL versions (for example, from RDS MySQL 5.6 to PolarDB-X 2.0 Standard Edition 5.7)?
Yes, using the logical migration method (DTS).
DTS tasks
I have an existing Data Transmission Service (DTS) task using the source instance as the data source. Does migration affect it?
No. During migration, full data is copied to the destination instance and incremental data is synchronized in real time — all while the source instance continues to serve as the DTS data source.
However, after migration is complete, if you switch your business to the destination instance and stop the source instance, the DTS task's data source does not automatically update. Re-create the DTS task with PolarDB-X 2.0 Standard Edition as the new data source.