All Products
Search
Document Center

ApsaraDB RDS:[Product changes/Feature changes] Migration of ApsaraDB RDS instances to a recommended zone

Last Updated:Jan 05, 2024

Alibaba Cloud upgrades the hardware and networks in some of its ApsaraDB RDS data centers to increase performance and stability. This topic describes how to migrate your RDS instance to another zone by using the ApsaraDB RDS console.

Deadline

We recommend that you complete the migration of your RDS instance by January 24, 2020.

Note

If you cannot complete the migration before this deadline, your workloads are not affected. For more information, see FAQ.

Application scope

If your RDS instance meets the following requirements, we recommend that you migrate it during off-peak hours at the earliest opportunity:

  • Your RDS instance runs one of the following MySQL versions and RDS editions:

    • MySQL 8.0 (with local disks)

    • MySQL 5.7 (with local disks)

    • MySQL 5.6

    • MySQL 5.5

    • SQL Server 2008 R2

    • PostgreSQL 10 on RDS High-availability Edition (with local disks)

    • PostgreSQL 9.4

  • Your RDS instance resides in one of the following source zones.

    Note

    The following table lists source zones and their recommended destination zones. The hardware and networks in the recommended destination zones offer better performance and stability to your RDS instance.

    Source zone

    Recommended destination zone

    Hangzhou Zone C

    Hangzhou Zone I

    Hangzhou Zone D

    Hangzhou Zone I

    Hangzhou Zone B + Hangzhou Zone C

    Hangzhou Zone H + Hangzhou Zone I

    Beijing Zone B

    Beijing Zone H

    Note

    Multi-zone deployment indicates that the primary and secondary instances reside in different zones to provide zone-level disaster tolerance.

Impacts

  • An instance switchover occurs during the migration. Make sure that your application is configured to automatically reconnect to the RDS instance. For more information about the impacts of an instance switchover, see Impacts of an instance switchover.

  • The DNS cache on the client may not be refreshed at the earliest opportunity, and some workloads may be switched over after 10 minutes. An instance switchover occurs during the migration.

  • When you change the VPC and vSwitch of your RDS instance, the virtual IP addresses (VIPs) of your RDS instance also change. We recommend that you connect your application to your RDS instance by using an endpoint. For more information, see Configure endpoints.

  • VIP changes affect the availability of PolarDB-X for a short period of time. Refresh and view the connection information in the PolarDB-X console.

  • VIP changes interrupt the connection between your RDS instance and Data Management (DMS) and the connection between your RDS instance and Data Transmission Service (DTS) for a short period of time. After the VPC and vSwitch of your RDS instance are changed, the connections are automatically resumed.

Procedure

  1. Log on to the ApsaraDB RDS console.

  2. In the top navigation bar, select the region in which your RDS instance resides.

  3. Find the required RDS instance and click the instance ID.

  4. In the Basic Information section, click Change Zone.

  5. In the dialog box that appears, specify the destination zone, vSwitch, and switching time. Then, click OK.

    Note

    If your RDS instance resides in a VPC, take note of the following items:

    • You cannot change its VPC.

    • Make sure that a vSwitch is created in the destination zone. If no vSwitches are created, click please create a new switch first on the VPC console. In the VPC console, create a vSwitch and make sure that you select a recommended destination zone. For more information, see Create and manage a vSwitch.

FAQ

  • What happens if I do not migrate my RDS instance?

    Your business remains available even if you do not migrate your RDS instance. However, for better performance and stability, we recommend that you migrate your RDS instance to a recommended destination zone.

  • If I cannot migrate my RDS instance by January 24, 2020, do I need to migrate it later?

    Yes, you still need to migrate your RDS instance if you cannot migrate it now. If your RDS instance resides in Beijing Zone B, Hangzhou Zone C, or Hangzhou Zone D that requires hardware and network upgrades, Alibaba Cloud notifies you of the current O&M events. You can schedule your migration plan based on these events by using the ApsaraDB RDS console. An instance switchover occurs during the migration. Make sure that your application is configured to automatically reconnect to the RDS instance. For more information, see Impacts.

  • After I migrate my RDS instance, do I need to migrate its peer ECS instance that resides in the same zone?

    Yes, you must migrate both your RDS instance and its peer ECS instance from the same zone. For more information about how to migrate an ECS instance across zones, see Migrate ECS instances from the classic network to a VPC.

  • Can I migrate my RDS instance to another zone that is not specified in the preceding table?

    Yes, you can migrate your RDS instance to another zone that is not specified in the table.

  • Can I migrate my RDS instance back to its source zone after the upgrade is complete?

    Yes, you can migrate your RDS instance back to its source zone after the upgrade is complete.

  • Why am I unable to select the source zone of my RDS instance when I create a vSwitch?

    The source zone of your RDS instance receives hardware and network upgrades. Therefore, you cannot create a vSwitch in it. When you create a vSwitch, select a recommended destination zone.