The multi-replica mechanism of OceanBase Database clusters provides rich disaster recovery capabilities. This mechanism supports automatic failover and avoids data loss when failures occur at the server, IDC, or city level. The RPO value is 0.
The high-availability primary/standby database architecture is an important supplement to the high-availability of OceanBase Database. If the primary cluster is unavailable (a majority of replicas failed), the standby cluster takes over the services and provides lossless failover (RPO = 0) and lossy failover (RPO> 0). These two disaster recovery capabilities can minimize service downtime.
OceanBase Database allows you to create, maintain, manage, and monitor one or more standby clusters. The standby cluster is the hot backup of the production database. You can choose to allocate resource-intensive reporting operations to standby clusters, to improve system performance and resource utilization.