ApsaraDB RDS provides various disaster recovery solutions to protect your data.

Data backup and restoration

  • By default, ApsaraDB RDS provides the data backup feature. Automatic backup and manual backup are supported. You can specify a cycle for automatic backups and initiate backup tasks at any point in time based on your business requirements. For more information, see Backup and restoration.
  • By default, ApsaraDB RDS allows you to restore data from backup files or restore data to a specific point in time. In most cases, you can restore data to any point in time within seven days to a temporary or cloned RDS instance. After the data is verified, you can migrate the data back to the primary RDS instance to complete data backtracking. For more information, see Backup and restoration..

Zone-disaster recovery

Edition Description
RDS Basic Edition
  • Data backups are stored in Object Storage Service (OSS) buckets or distributed cloud disks. Multi-replica redundancy is used to ensure data reliability. This backup mechanism is used for all RDS instances.
  • Your database system consists of only one primary RDS instance. No secondary RDS instances are provided for hot standby. When a fault occurs on your RDS instance, a long period of time is required to recover the RDS instance from the fault. This edition is suitable for scenarios that do not require high availability.
RDS High-availability Edition Your database system consists of a primary RDS instance and a secondary RDS instance. The RDS instances work in active-active mode to ensure high availability. This edition is suitable for more than 80% of business scenarios. When the primary RDS instance fails, the workloads are switched over to the secondary RDS instance within seconds. The switchover process is transparent to the application. When the secondary RDS instance fails, ApsaraDB RDS automatically creates another secondary RDS instance to ensure the high availability of your database system.
  • Single-zone RDS instances: The primary RDS instance and the secondary RDS instance reside in the same zone. The primary RDS instance and the secondary RDS instance are deployed on different physical servers. Redundant racks, heating, ventilation and air conditioning (HVAC) systems, circuits, and networks are available in the zone to ensure the high availability of your database system.
  • Multi-zone RDS instances: These instances are also called local dual-data center or local disaster recovery instances. The primary RDS instance and the secondary RDS instance reside in different zones of the same region. Cross-zone disaster recovery is supported without additional fees.
Note
RDS Cluster Edition Your database system consists of a primary RDS instance and a secondary RDS instance. You can create up to seven read-only RDS instances for the primary RDS instance to scale out the read capability of the cluster. The data of the secondary RDS instance and the data of all read-only RDS instances are synchronized from the primary RDS instance. RDS Cluster Edition provides the same high availability as RDS High-availability Edition. Read-only RDS instances can be deployed in zones other than the zones of the primary RDS instance and the secondary RDS instance.
Note
RDS Enterprise Edition
  • RDS Enterprise Edition is available for ApsaraDB RDS instances that run MySQL 5.7 and MySQL 8.0. For more information, see Enterprise Edition.
  • Your database system consists of a primary RDS instance, a secondary RDS instance, and a logger RDS instance. This architecture ensures strong data consistency by synchronizing data among multiple replicas and provides financial-level data reliability. This edition is suitable for the core production databases of large enterprises in all industries.
  • The three RDS instances are always deployed in three different zones of the same region.

Get started with ApsaraDB RDS