In this video, Nickolay Ihalainen, a Senior Scaling Specialist at Percona Global Services, explains how to set up replication with standby clusters for Kubernetes databases using Percona’s open-source tools, including the Percona Operator for PostgreSQL

A Standby Cluster is a backup version of your main database. It’s there to keep your data safe and make sure your database can keep running even if something goes wrong with the main one.

For this demo, we use Percona Operators for PostgreSQL to create the clusters, which facilitates high availability setups and database management by automating deployment, scaling, and management tasks within Kubernetes environments.

Nickolay created a primary node and the configuration of replication to standby clusters for PostgreSQL, ensuring data redundancy and availability. This primary node has two standby databases in the same primary node.

Then, we have the object storage (S3) for backups, highlighting the importance of having offsite backups in different geographical locations to safeguard against data loss. This is where the primary node will access to make a data replication.

This demo also includes using Patroni to manage this process, enabling replication and failover between primary and standby servers, and PgBouncer, a tool that manages how applications are aligned to communicate with a PostgreSQL database.

Watch our complete hands on in this YouTube video:

You can find more instructions on how to deploy a standby cluster for Disaster Recovery, and also you can Create a Standby Cluster With the Percona Operator for PostgreSQL.

Is you have questions o feedback, write to us in our Percona Comunity Forum ∎