Greenplum Physical Backups with WAL-G
Nebius
About speaker
Daniil is a software engineer at the Data platform department of Yandex Cloud. He is also participating as a mentor in Google Summer of Code at the PostgreSQL Global Development Group. Daniil is one of the core maintainers of the WAL-G project ― an archival restoration tool for PostgreSQL, MySQL/MariaDB, MS SQL Server, GreenplumDB, and other databases.
About speakers's company
We are a startup with offices in the Netherlands, Serbia, and Israel. Our ambition is to create a world-class ecosystem of full-fledged cloud and ML-driven solutions for the B2B market. Our team has experience in building data centers and supercomputers, developing ML-technologies with millions of daily users and launching full-stack public cloud platforms.
4 July, 18:10, «Hall 3»
Abstracts
In 2022, we released the Yandex Managed Service for Greenplum® to the public. One of its features is physical backups via WAL-G instead of logical ones (gpbackup/pg_dump). I’ll tell you about how we made cluster-wide consistent physical backup, PITR, delta-backups, and other nice features that are now available in WAL-G.
From a quick look, Greenplum itself is multiple Postgres instances wrapped together. Since we already have WAL-G for Postgres physical backups, it should be easy to create a physical backup of Greenplum instances, right? However, there were no implemented solutions for Greenplum physical backups, so we decided to invent our own.
I’ll go over the following topics:
• how we were the first in the world to implement physical backups for Greenplum;
• what challenges we’ve faced and how we solved them;
• what benefits we’ve received as a result;
• and, of course, I’ll tell you how to begin using physical backups with WAL-G right now!
The talk was accepted to the conference program
