Smoothly migrate legacy RDS for PostgreSQL instances to the new architecture
For historical reasons, some ApsaraDB RDS for PostgreSQL instances are still managed in the legacy console. You can migrate these instances to the new console to benefit from lower prices and better services.
Prerequisites
The source ApsaraDB RDS for PostgreSQL instance is a legacy instance.
You can determine if your ApsaraDB RDS for PostgreSQL instance is a legacy instance by its ID prefix.
Legacy instance: The instance ID is prefixed with
pg-cn-.New-architecture instance: The instance ID is prefixed with
pgm-.
Comparison of legacy and new-architecture instances
For historical reasons, ApsaraDB RDS for PostgreSQL previously used a legacy console. The user interface (UI) and features of the legacy console differ from those of the new ApsaraDB RDS for PostgreSQL console. New-architecture instances offer significant advantages in terms of price and services. Therefore, we recommend that you migrate instances from the legacy console to the new console.
Comparison Item | Legacy architecture | New architecture |
Fees | ❌High fees. | ✔️Fees are reduced by more than 20%. |
Functionality | ❌Only a few features are available, and no new features are being iteratively developed. | ✔️Supports new feature iterations and provides the following additional features: |
Stability | ❌Relatively low stability. | ✔️Significantly more stable than legacy ApsaraDB RDS for PostgreSQL instances. |
Migration impact
After a successful migration, your services will switch to the new instance during the specified maintenance window. The original instance will become read-only, and a transient disconnection that lasts for several minutes will occur. We recommend that you perform the upgrade during off-peak hours.
Precautions
After your services are switched to the new instance, the connection string remains the same, but the IP address associated with it changes. Ensure that your application uses the connection string. For more information, see View or change endpoints and port numbers.
Migration procedure
Submit a ticket and provide the instance ID of the legacy ApsaraDB RDS for PostgreSQL instance to be migrated.
NoteYou can log on to the temporary PostgreSQL console to view the ID of the legacy ApsaraDB RDS for PostgreSQL instance.
Create a new-architecture ApsaraDB RDS for PostgreSQL instance based on the information provided by the customer service representative in the ticket. For more information, see Create an ApsaraDB RDS for PostgreSQL instance.
NoteCreate the new instance using the following information provided by the customer service representative:
Region
Zone
Instance version
Instance type
Storage capacity
VPC ID
vSwitch ID
After the new instance is created, set a maintenance window for it during off-peak hours.
NoteAll your services will switch to the new instance during this maintenance window.
On the new instance, configure an automatic backup policy as needed.
Provide the new instance ID to the customer service representative to start the smooth migration task.
NoteAfter the migration task is complete, the system switches your services during the maintenance window set in Step 3. This causes a transient disconnection that lasts for several minutes.
After the service switchover is successful, verify the availability of your service. After you confirm that there are no issues, submit a ticket to release the legacy ApsaraDB RDS for PostgreSQL instance.
NoteAlibaba Cloud recommends that you do not release the legacy ApsaraDB RDS for PostgreSQL instance for 72 hours. This provides enough time to test the availability of your services on the new instance.
Rollback plan
If you encounter any issues and need to perform a rollback, submit a ticket before you release the legacy ApsaraDB RDS for PostgreSQL instance. In the ticket, provide the instance IDs of both the legacy and new instances. Alibaba Cloud will then help you switch your services back to the legacy ApsaraDB RDS for PostgreSQL instance.
After a rollback, all incremental data on the new instance is lost and cannot be recovered.