Sergey Pronin: Disaster Recovery for PostgreSQL on Kubernetes

Disaster recovery is not optional for businesses operating in the digital age. With the ever-increasing reliance on data, system outages or data loss can be catastrophic, causing significant business disruptions and financial losses. With multi-cloud or multi-regional PostgreSQL deployments, the complexity of managing disaster recovery only amplifies. This is where the Percona Operators come in, providing a solution to streamline disaster recovery for PostgreSQL clusters running on Kubernetes. With the Percona Operators, businesses can manage multi-cloud or hybrid-cloud PostgreSQL deployments with ease, ensuring that critical data is always available and secure, no matter what happens. In this article, you will learn how to set up disaster recovery with Percona Operator for PostgreSQL version 2. Overview of the solution Operators automate routine tasks and remove toil. For standby, Operator provides the following options: pgBackrest repo-based standby Streaming replication Combination of (1) and (2) We will review the repo-based standby as the simplest one: 1. Two Kubernetes clusters in different regions, clouds, or running in hybrid mode (on-prem + cloud). One is Main, and the other is Disaster Recovery (DR). 2. In each cluster, there are the following components: Percona Operator PostgreSQL cluster pgBackrest pgBouncer 3. pgBackrest on the Main site streams backups and Write Ahead Logs (WALs) to the object storage. 4. pgBackrest on the DR site takes these backups and streams them to the standby cluster. Configure main site Use your favorite method to deploy the Operator from our documentation. Once installed, configure the Custom Resource manifest so that pgBackrest starts using the Object Storage of your choice. Skip this step if you already have it configured. Configure the backups.pgbackrest.repos section by adding the necessary configuration. The below example is for Google Cloud Storage (GCS): spec: backups: c[...]