Physical Cluster Replication in CockroachDB Explained

Description

While CockroachDB is a distributed SQL database designed for resilience across three or more regions, many organizations only have two regions in their environment, which can limit the functionality of our signature resilience features. As of CockroachDB 23.2, organizations can now take advantage of Physical Cluster Replication (PCR) functionality in CockroachDB. With PCR functionality, you can now survive full cluster failures with RPO (Recovery Point Objective) and RTO (Recovery Time Objective) measured in seconds rather than minutes. Physical Cluster Replication in CockroachDB works by creating an exact, constantly updating replica of a primary cluster, while providing granular observability and control over data replication and cutover times. Data integrity checks ensure your recovery will support your business continuity goals. Physical Cluster Replication in CockroachDB Explained 00:00 What is Physical Cluster Replication (PCR) and why would you want to use it? 01:21 Creating a primary and secondary cluster 02:09 Running an application and connecting to CockroachDB 03:25 Explaining Physical Cluster Replication with diagrams 05:05 Initializing the secondary cluster for replication 06:11 What would happen if the primary cluster were to go away? 07:43 How do you use CockroachDB MOLT Verify? 09:09 Physical Cluster Replication explained via whiteboard 11:01 Shutting down the secondary cluster and backfilling the primary cluster 11:58 Closing notes A few questions Cockroach Labs Technical Evanglist Rob Reid answers in this video: - How does Physical Cluster Replication work in CockroachDB? - Physical cluster replication vs backup and restore? - How can you achieve lower RTO and RPO times? #distributedsql #disasterrecovery