This topic describes how to migrate an ApsaraDB RDS for PostgreSQL instance from the ApsaraDB RDS for PostgreSQL console to the ApsaraDB RDS console. After the migration is complete, the RDS instance runs more stably at a lower price.

Prerequisites

Your RDS instance is managed in the ApsaraDB RDS for PostgreSQL console.
Note You can check the prefix of the instance ID to identify the console that is used to manage your RDS instance.
  • In the ApsaraDB RDS for PostgreSQL console, the instance ID is prefixed by pg-cn-.
  • In the ApsaraDB RDS console, the instance ID is prefixed by pgm-.

Comparison between the ApsaraDB RDS for PostgreSQL console and the ApsaraDB RDS console

The ApsaraDB RDS for PostgreSQL console differs from the ApsaraDB RDS console in terms of UI design and functionality. The RDS instances created in the ApsaraDB RDS console deliver better user experience and cost less than those created in the ApsaraDB RDS for PostgreSQL console. We recommend that you migrate your RDS instance from the ApsaraDB RDS for PostgreSQL console to the ApsaraDB RDS console.

Item ApsaraDB RDS for PostgreSQL console ApsaraDB RDS console
Fee ❌ The fee is high. ✔️ The fee is reduced by more than 20%.
Functionality ❌ Only a few features are available, and no new features are being iteratively developed. ✔️ The following features are available, and new features are iteratively developed:
Stability ❌ This console runs less stably than the ApsaraDB RDS console. ✔️ This console runs more stably than the ApsaraDB RDS for PostgreSQL console.

Impact

After the migration is complete, ApsaraDB RDS switches the workloads on your RDS instance over to a new RDS instance within the specified maintenance window. During the switchover, your RDS instance can process only read requests. In addition, a transient connection of a few minutes occurs. We recommend that you migrate your RDS instance during off-peak hours.

Precautions

After the workloads on your RDS instance are switched over to a new RDS instance, the endpoints of your RDS instance are still used to connect to the new RDS instance. However, the IP addresses that are associated with the endpoints change. Make sure that the endpoints are used on your applications to establish connections. For more information about how to view the endpoints of an RDS instance, see View and change the internal and public endpoints and port numbers of an ApsaraDB RDS for PostgreSQL instance.

Procedure

  1. Submit a ticket. In the ticket, you must specify the ID of your RDS instance.
    Note You can log on to the ApsaraDB RDS for PostgreSQL console to view the ID of your RDS instance.
  2. Create an RDS instance in the ApsaraDB RDS console based on the information that is provided by the customer service representative in the ticket . For more information, see Create an ApsaraDB RDS for PostgreSQL instance.
    Note The following information is provided by the customer service representative in the ticket:
    • Region
    • Zone
    • Database engine version
    • Instance type
    • Storage capacity
    • VPC ID
    • VSwitch ID
  3. After you create the RDS instance in the ApsaraDB RDS console, select an off-peak hour as the maintenance window for the new RDS instance. For more information, see Set the maintenance window of an ApsaraDB RDS for PostgreSQL instance.
    Note All of your workloads will be switched over to the new RDS instance within the specified maintenance window.
  4. Configure a backup policy that allows automatic backups on the new RDS instance based on your business requirements. For more information, see Back up an ApsaraDB RDS for PostgreSQL instance.
  5. Provide the ID of the new RDS instance to the customer service representative. Then, the customer service representative can create a task to migrate the data of your RDS instance to the new RDS instance.
    Note After the data is migrated to the new RDS instance, ApsaraDB RDS switches your workloads over to the new RDS instance during the maintenance window that you specified in Step 3. The switchover causes a transient connection that lasts a few minutes.
  6. After your workloads are switched over to the new RDS instance, verify that your workloads run as normal on the new RDS instance. Then, submit a ticket to release your original RDS instance, which is managed in the ApsaraDB RDS for PostgreSQL console.
    Note After your workloads are switched over to the new RDS instance, we recommend that you do not release your original RDS instance within 72 hours. This ensures that you have sufficient time to verify the availability of your database service on the new RDS instance.

Rollback

The new RDS instance may become unavailable due to exceptions. In this case, you may need to roll your workloads back to your original RDS instance. This requires that you submit a ticket before you release your original RDS instance. In the ticket, you must provide the ID of your original RDS instance and the new RDS instance to the customer service representative. Then, the customer service representative can roll your workloads back to your original RDS instance.

Warning After your workloads are rolled back to your original RDS instance, all the incremental data that is generated on the new RDS instance is lost and cannot be restored.