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.

Local disaster recovery

Series Description
Basic edition
  • Data backup is stored on an OSS instance or a distributed cloud disk. Multi-replica redundancy is used to ensure that no data is lost. (This is applicable to all ApsaraDB for RDS instances.)
  • Only one node is available. No node is provided for hot backup. When a fault occurs, it takes a long time to restore service. This edition is applicable to scenarios with less demanding availability requirements.
High-availability edition This solution adopts a dual-host hot architecture consisting of a primary node and a secondary node. It is applicable to more than 80% of scenarios. When the primary node fails, the traffic is switched to the secondary node within seconds. The failover process is transparent to the application. When the secondary node fails, ApsaraDB for RDS automatically creates a new secondary node to ensure the high availability of the service.
  • Single-zone instances: The primary and secondary nodes are in the same zone. The primary and secondary nodes are deployed on different physical servers. Redundant racks, air HVAC systems, circuits, and networks are available in the zone. In this way, the high availability of the service is ensured.
  • Multi-zone instances (local dual-IDC or local disaster recovery instances): The primary and secondary nodes are deployed in different zones of the same region. Cross-zone disaster recovery is supported without any additional charge.
Note Single-zone instances can be converted to multi-zone instances and vice versa. For more information, see Migrate zones.
Cluster edition The cluster edition provides a primary-secondary high-availability architecture and seven read-only nodes, allowing you to scale out the read capability of the cluster. The data of the secondary node and all read-only nodes is synchronized from the primary node. The cluster edition has the same high availability as the high-availability edition. The read-only nodes can be deployed in zones other than those of the primary and secondary nodes.
Note
  • The cluster edition is only available for ApsaraDB RDS for SQL Server 2017. For more information, see Cluster edition.
  • For more information about the read-only Apsara RDS for MySQL instances, see Read-only instances.
  • For more information about the read-only nodes of the POLARDB cluster, see POLARDB clusters.
Enterprise edition
  • This edition consists of one primary node and two secondary nodes, ensures strong data consistency through the synchronization of multiple replicas, and provides financial-level data reliability. It is applicable to the core production databases of large enterprises in all industries.
  • The three nodes in the finance edition are always deployed in three different zones of the same region.
Note
  • Currently, enterprise edition is only available for MySQL 5.6. For more information, see Enterprise Edition.
  • Enterprise edition is only available for ApsaraDB for RDS instances deployed in the China (Beijing), China (Hangzhou), China (Shanghai), and China (Shenzhen) regions.

Remote disaster recovery

  • You can synchronize data from a database in an on-premises data center or a user-created database on an ECS instance to an ApsaraDB for RDS instance in any region in real time. Even if the data center is damaged, a data backup is always stored on the ApsaraDB for RDS instance. For more information about the operation, see Create real-time synchronization jobs.