- HA features ensure continuous access to data without interruption even in the presence of or disruptions to maximize uptime.
-
DR tools allow for recovery from major incidents to minimize downtime and data loss.
- Recovery Point Objective (RPO): The maximum amount of data loss (measured by time) that an organization can tolerate.
- Recovery Time Objective (RTO): The maximum length of time it should take to restore normal operations following an outage.
High availability
- : CockroachDB’s built-in stores data safely and consistently on multiple nodes to ensure no downtime even during a temporary node outage. allow you to configure the number and location of to suit a deployment.
- For more detail on planning for single-region or multi-region recovery, refer to or .
- : Capabilities built in to CockroachDB to perform routine maintenance operations with minimal impact to foreground performance. For example, , , and .
- (Preview): A cross-cluster replication tool between active CockroachDB clusters, which supports a range of topologies. LDR provides eventually consistent, table-level replication between the clusters. Individually, each active cluster uses CockroachDB multi-active availability to achieve low, single-region write latency with transactionally consistent writes using Raft replication.
Choose an HA strategy
For details on designing your cluster topology for HA with replication, refer to the page.
Disaster recovery
- : Point-in-time backup and restore allows you to roll back to a specific point in time. Multiple supported providers means that you can store backups in your chosen provider. allow you to configure backup frequency for lower .
- : A cross-cluster replication tool between an active primary CockroachDB cluster and a passive standby CockroachDB cluster. PCR provides transactionally consistent full-cluster replication.

