Instance DR

TaurusDB can store backups in a different region from the DB instance for disaster recovery. If a DB instance in a region is faulty, you can use the backups in another region to restore data to a new DB instance.

After you enable cross-region backup, the backups are automatically stored in the region you specify.

An AZ is a physical region where resources have their own independent power supply and networks. AZs are physically isolated but interconnected through an internal network. TaurusDB supports multiple-AZ deployment for cross-AZ DR.

A TaurusDB instance contains one primary node and multiple read replicas. If the primary node becomes unavailable, TaurusDB automatically fails over to a read replica.

A RegionlessDB cluster consists of multiple TaurusDB instances in different regions around the world. Currently, a RegionlessDB cluster consists of one primary instance (in the primary region) and up to five standby instances (in standby regions). Data is synchronized between primary and standby instances, providing nearby access and region-level DR capabilities.

• Remote multi-active: Data is synchronized among instances in a RegionlessDB cluster. For lower network latency and quicker resource access, you can select the instance nearest to your workloads.
• Remote DR: If there is a region-level fault on the primary instance, workloads can be switched to a standby instance for remote DR.

The production center's TaurusDB instance synchronizes data in real time with the DR center's TaurusDB instance by using the Data Replication Service (DRS), keeping data synchronous across the regions.