This topic describes the methods that you can use to migrate data among self-managed data centers, third-party clouds, and ApsaraDB RDS with no downtime.
Scenarios
The following table provides links to the documentation that may help you migrate data in different scenarios.
Scenario | References |
Scenario | References |
Migrate data from a PostgreSQL database in a self-managed data center to an ApsaraDB RDS for PostgreSQL instance | |
Migrate data from a PostgreSQL database on a third-party cloud to an ApsaraDB RDS for PostgreSQL instance | |
Migrate data between ApsaraDB RDS for PostgreSQL instances | |
Migrate data from an ApsaraDB RDS for PostgreSQL instance to an on-premises PostgreSQL database |
Usage notes
Compatibility issues may occur when you migrate data between RDS instances that run different versions of PostgreSQL. Therefore, we recommend that you test your business on the destination RDS for PostgreSQL instance and make sure that your business can normally run on the destination instance before you migrate data.
Elastic Compute Service (ECS) instances in the classic network will reach end of life (EoL) on February 28, 2025. If your database is deployed on an ECS instance in the classic network, we recommend that you migrate the ECS instance from the classic network to a VPC. For more information about the EoL of ECS instances in the classic network, see EOL notice for Alibaba Cloud ECS instances in the classic network. For more information about how to migrate the ECS instance, see Migrate ECS instances from the classic network to a VPC.
