public inbox for [email protected]
help / color / mirror / Atom feedFrom: Sam Stearns <[email protected]>
To: Ron Johnson <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: pg_basebackup --incremental
Date: Wed, 29 Oct 2025 10:40:28 -0700
Message-ID: <CAN6TVjmuechv342AD7cheZDws07K2MZsmN3jnkxvqB3Qfs=wPQ@mail.gmail.com> (raw)
In-Reply-To: <CAN6TVjnbUv+Ths8_4XFxGhodfZzKcN8zNjtak4nAi2ZT21DKiA@mail.gmail.com>
References: <CAN6TVjnoZo9p+SKTEUBhe+QGsf2tbwUEJ21fXfd3s9W-TJ5wRg@mail.gmail.com>
<CANzqJaChB76pu0g9W0taQ9p0fX1Zyr++B70uexmMZZfRMiQZ3w@mail.gmail.com>
<CAN6TVjnbUv+Ths8_4XFxGhodfZzKcN8zNjtak4nAi2ZT21DKiA@mail.gmail.com>
Hi Ron,
If I may, please. What are the postgres.conf parameters you set
specifically for pgBackRest?
Thanks,
Sam
On Tue, Oct 28, 2025 at 3:21 PM Sam Stearns <[email protected]> wrote:
> Thanks, Ron! We'll take another look at pgBackRest.
>
> On Tue, Oct 28, 2025 at 10:52 AM Ron Johnson <[email protected]>
> wrote:
>
>> On Tue, Oct 28, 2025 at 1: 43 PM Sam Stearns <sam. stearns@ dat. 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
>> ZjQcmQRYFpfptBannerStart
>> This Message Is From an External Sender
>> This message came from outside your organization.
>>
>> ZjQcmQRYFpfptBannerEnd
>> On Tue, Oct 28, 2025 at 1:43 PM Sam Stearns <[email protected]> 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!
>>
>
>
> --
>
> Samuel Stearns
> Team Lead - Database
> c: 971 762 6879 | o: 971 762 6879 | DAT.com
>
> <https://www.dat.com/?utm_medium=email&utm_source=DAT_email_signature_link;
>
>
--
Samuel Stearns
Team Lead - Database
c: 971 762 6879 | o: 971 762 6879 | DAT.com
<https://www.dat.com/?utm_medium=email&utm_source=DAT_email_signature_link;
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: pg_basebackup --incremental
In-Reply-To: <CAN6TVjmuechv342AD7cheZDws07K2MZsmN3jnkxvqB3Qfs=wPQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox