Reliability Functions

Cluster HA

TaurusDB supports an HA architecture with a primary node and read replicas. If the primary node fails, a read replica is automatically promoted to the primary node to provide services, and the original primary node is demoted to a read replica.

TaurusDB also supports heterogeneous DR instances (MySQL nodes) to ensure HA. If your DB instance is unavailable due to unknown community bugs, misoperations, or AZ faults, the heterogeneous DR instance can take over the services.

Data Backup and Restoration

TaurusDB supports automated and manual backups. You can periodically back up databases. If a database is faulty or data is damaged, you can restore the database using backups to ensure data reliability.

TaurusDB supports same-region and cross-region backups. Cross-region backups mean that if an instance in a region is faulty, you can use the backups in another region to restore data to a new instance.

For details, see Backup Principles.

Auto Scaling

TaurusDB supports auto scaling, which can automatically adjust the instance specifications or the number of read replicas.

For details, see Configuring Auto Scaling Policies for a DB Instance.

Cross-AZ DR

TaurusDB instances can have nodes deployed in multiple AZs.

TaurusDB also supports cross-AZ active-active DR within a region using DRS, which is similar to cross-region DR.

Cross-Region DR

You can create a DR instance on the DRS console. If a natural disaster occurs in the region hosting the primary DB instance and both the primary and standby DB instances are unavailable, the DR instance is promoted to the primary DB instance. Then, change the connection address on your applications to the address of the DR instance for service recovery. DRS allows you to perform cross-region single-active or dual-active DR between a primary DB instance and a DR instance during disaster recovery.

For details, see From TaurusDB to TaurusDB (Single-Active DR) and From TaurusDB to TaurusDB (Dual-Active DR).