ApsaraDB for RDS supports multiple disaster tolerance plans to protect you from data loss.

Backup and recovery

  • RDS supports automatic and manual backups. You can set the automatic backup frequency or manually create backups at any time. For more information, see Backup and recovery.
  • RDS supports data recovery by time or backup set. You can restore data of any point in time within the log retention period to a new instance, verify the data, and then transfer the data to the original instance. For more information, see Backup and recovery.

Disaster tolerance

Series Disaster tolerance
Basic Edition
  • Data backups are stored as multiple copies on OSS or distributed cloud disks to prevent data loss. This applies to all RDS series.
  • The Basic Edition consists of a single node without a slave node as hot backup. Therefore, if fault occurs, the restoration time is long. Choose Basic Edition if you do not require high availability.
High-availability Edition The High-availability Edition adopts the high-availability architecture with one master node and one slave node. It is applicable to over 80% of scenarios. If the master node fails, a switchover occurs within seconds without affecting your applications. If the slave node fails, a new slave node is automatically generated to ensure high availability.
  • Single-zone instance: The master and slave nodes are in the same zone but on different physical servers. All cabinets, air conditioners, electricity, and networks in the zone are redundant to ensure high availability.
  • Multi-zone instance: The master and slave nodes are in different zones of an area, providing area-level disaster tolerance ability.
Note
  • You can switch between single-zone instances and multi-zone instances. For details, see Migrate an ApsaraDB RDS MySQL instance across zones.
  • When the slave node malfunctions, RDS instantly backs up the master node. When the backup process is about to finish, a global lock is generated and the master node runs in the read-only status for 5 seconds or less.
Cluster Edition Based on the AlwaysOn technology, it provides one master node, one slave node, and up to seven read-only nodes that horizontally scale read capabilities. The slave and read-only nodes synchronize data from the master node. The Cluster Edition provides the same availability as the High-availability Edition. Besides, the read-only nodes can be deployed in zones different from those of the master and slave nodes.
Note
Enterprise Edition
  • RDS MySQL 5.7 supports the Enterprise Edition.
  • In the Enterprise Edition, your DB system has one master instance and two slave instances. Data is replicated between the master and slave instances through multiple replicas to guarantee data consistency and finance-level reliability. The Enterprise Edition can be used by large-sized enterprises to build core production databases.
  • In the Enterprise Edition, the master and slave instances are located in three different zones in the same region.

Get started

Related topics