Restoring a downloaded RDS backup to a new ApsaraDB RDS instance is a two-stage process: restore the backup to a self-managed database, then migrate that database to the new instance. The exact steps depend on your database engine.
Limitations
Before you start, note the following engine-specific constraints:
| Engine | Constraint |
|---|---|
| ApsaraDB RDS for PostgreSQL | Physical backup files cannot be restored directly to an ApsaraDB RDS instance. Perform a logical backup using pg_dump before releasing the instance, then use pg_restore to restore to the new instance. See Migrate data from a self-managed PostgreSQL database to an ApsaraDB RDS for PostgreSQL instance by using pg_dump and pg_restore. |
| ApsaraDB RDS for MariaDB | Downloading backup files is not supported. |
Restore data in an ApsaraDB RDS for MySQL instance
Restoring a MySQL backup to a new RDS instance requires two steps:
Restore the backup file to a self-managed MySQL database. Choose the method that matches your backup type:
Use Data Transmission Service (DTS) to migrate the self-managed database to the new ApsaraDB RDS instance. See Migrate data from a self-managed MySQL database to an ApsaraDB RDS for MySQL instance.
Restore data in an ApsaraDB RDS for SQL Server instance
Upload the downloaded backup file to Object Storage Service (OSS), then migrate it to the new ApsaraDB RDS instance using the full backup migration method. Choose the guide that matches your SQL Server version: