This topic describes how to migrate an ApsaraDB RDS for MySQL instance across zones in the same region. After the migration is completed, all the attributes, configuration, and endpoints of your RDS instance remain unchanged. The time that is required to complete the migration varies based on the volume of data that needs to be migrated. The migration can take a few hours.
Prerequisites
- Your RDS instance runs one of the following MySQL versions and RDS editions:
- MySQL 8.0 on RDS High-availability Edition (with local SSDs)
- MySQL 5.7 on RDS High-availability Edition (with local SSDs)
- MySQL 5.6 on RDS High-availability Edition (with local SSDs)
- MySQL 5.5
- The region where your RDS instance resides consists of multiple zones. For more information about regions and zones, see Regions and zones.
- The network connection mode of your RDS instance is upgraded. For more information, see [Important] RDS network link upgrade.
For more information about how to migrate RDS instances that run other database engines, see the following topics:
Billing
The migration is provided free of charge. This applies even if you migrate your RDS instance from one zone to multiple zones.
Precautions
- During the migration, a transient connection error of about 30 seconds occurs. Make sure that your application is configured to automatically reconnect to your RDS instance.
- After the migration, your RDS instance switches to a new VPC and a new vSwitch. In this case, the virtual IP addresses (VIPs) of your RDS instance change. Therefore, we recommend that you connect your application to your RDS instance by using an internal or public endpoint. Do not establish a connection by using an IP address.
- The VIP changes temporarily interrupt the availability of DRDS . After the migration is completed, you must immediately update and view endpoints in the DRDS console.
- If your RDS instance has an ongoing DTS task, you must restart the task after the migration is completed.
Migration scenarios
Migration scenario | Description |
---|---|
Migration from one zone to another zone | The original zone where your RDS instance resides cannot ensure service performance due to issues such as heavy loads. |
Migration from one zone to multiple zones | You want to implement disaster recovery across data centers for your RDS instance.
After the migration is completed, your RDS instance and its secondary instance reside
in different zones.
Multi-zone deployment delivers higher disaster recovery capabilities than single-zone deployment. If your RDS instance is deployed in a single zone, it can withstand server and rack failures. However, if your RDS instance is deployed in multiple zones, it can withstand data center failures. |
Migration from multiple zones to one zone | You want your RDS instance to provide specific features that are supported only for single-zone deployment. |
Procedure
Related operations
Operation | Description |
---|---|
Migration zone | Migrates an ApsaraDB RDS instance across zones in the same region. |