Re: pg_basebackup --incremental

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_basebackup --incremental
Date: 2025-10-28 17:52:08
Message-ID: CANzqJaChB76pu0g9W0taQ9p0fX1Zyr++B70uexmMZZfRMiQZ3w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Oct 28, 2025 at 1:43 PM Sam Stearns <sam(dot)stearns(at)dat(dot)com> wrote:

> Howdy,
>
> We're running version 17.6. Would anyone be able to point me to, or
> provide, some sample use cases / scripts / usage to deploy a pg_basebackup
> full + --incremental strategy as a backup solution, please?
>

The question confuses me a bit (though maybe because weekly "full", and
remainder "incremental" is pretty standard). PgBackRest really is quite
simple and easy to configure if you back up to a local mount point (even
when that mount point is NFS).

This is in the "postgres" crontab:
15 01 * * Sun Type=full; pgbackrest backup --stanza=nfs --type=$Type &>
logs/pgbackrest_$(date +"\%F_\%T")_${Type}.log
15 01 * * 1-6 Type=incr; pgbackrest backup --stanza=nfs --type=$Type &>
logs/pgbackrest_$(date +"\%F_\%T")_${Type}.log

And this is my /etc/pgbackrest.conf:
[global]
repo1-path=/Database/backups/pgbackrest
repo1-cipher-type=aes-256-cbc
repo1-cipher-pass=<redacted>
repo1-bundle=y
repo1-bundle-limit=20MiB
repo1-bundle-size=200MiB
[nfs]
pg1-path=/Database/17/data
resume=n
start-fast=y
stop-auto=y
compress-type=zst
log-level-console=detail
log-level-file=info
log-path=/var/lib/pgsql/logs/pgbackrest
retention-full=4
process-max=<nproc * 3/4>
[nfs:archive-push]
compress-type=zst

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Sam Stearns 2025-10-28 22:21:01 Re: pg_basebackup --incremental
Previous Message Sam Stearns 2025-10-28 17:42:45 pg_basebackup --incremental