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
|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.
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.
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.