MIME-Version: 1.0
References: 
 <CAN6TVjnoZo9p+SKTEUBhe+QGsf2tbwUEJ21fXfd3s9W-TJ5wRg@mail.gmail.com>
In-Reply-To: 
 <CAN6TVjnoZo9p+SKTEUBhe+QGsf2tbwUEJ21fXfd3s9W-TJ5wRg@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Tue, 28 Oct 2025 13:52:08 -0400
Message-ID: 
 <CANzqJaChB76pu0g9W0taQ9p0fX1Zyr++B70uexmMZZfRMiQZ3w@mail.gmail.com>
Subject: Re: pg_basebackup --incremental
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000005be08806423bad37"
Archived-At: 
 <https://www.postgresql.org/message-id/CANzqJaChB76pu0g9W0taQ9p0fX1Zyr%2B%2BB70uexmMZZfRMiQZ3w%40mail.gmail.com>
Precedence: bulk

--0000000000005be08806423bad37
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 28, 2025 at 1:43=E2=80=AFPM Sam Stearns <sam.stearns@dat.com> w=
rote:

> 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_basebacku=
p
> 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=3Dfull; pgbackrest backup --stanza=3Dnfs --type=3D$Type =
&>
logs/pgbackrest_$(date +"\%F_\%T")_${Type}.log
15 01 * * 1-6 Type=3Dincr; pgbackrest backup --stanza=3Dnfs --type=3D$Type =
&>
logs/pgbackrest_$(date +"\%F_\%T")_${Type}.log

And this is my /etc/pgbackrest.conf:
[global]
repo1-path=3D/Database/backups/pgbackrest
repo1-cipher-type=3Daes-256-cbc
repo1-cipher-pass=3D<redacted>
repo1-bundle=3Dy
repo1-bundle-limit=3D20MiB
repo1-bundle-size=3D200MiB
[nfs]
pg1-path=3D/Database/17/data
resume=3Dn
start-fast=3Dy
stop-auto=3Dy
compress-type=3Dzst
log-level-console=3Ddetail
log-level-file=3Dinfo
log-path=3D/var/lib/pgsql/logs/pgbackrest
retention-full=3D4
process-max=3D<nproc * 3/4>
[nfs:archive-push]
compress-type=3Dzst

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

--0000000000005be08806423bad37
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Oct 28, 2025 at 1:43=E2=80=AFPM S=
am Stearns &lt;<a href=3D"mailto:sam.stearns@dat.com">sam.stearns@dat.com</=
a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Howdy,</di=
v><div><br></div><div>We&#39;re running version=C2=A017.6.=C2=A0 Would=C2=
=A0anyone be able to point me to, or provide, some sample use cases / scrip=
ts / usage to deploy a pg_basebackup full=C2=A0+ --incremental strategy as =
a backup solution, please?</div></div></blockquote><div></div></div><div><b=
r></div><div>The question confuses me a bit (though maybe because weekly &q=
uot;full&quot;, and remainder &quot;incremental&quot; is pretty standard).=
=C2=A0 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).</div><div><b=
r></div><div>This is in the &quot;postgres&quot; crontab:</div><div><font f=
ace=3D"monospace">15 01 * * Sun Type=3Dfull; pgbackrest backup --stanza=3Dn=
fs --type=3D$Type &amp;&gt; logs/pgbackrest_$(date +&quot;\%F_\%T&quot;)_${=
Type}.log<br>15 01 * * 1-6 Type=3Dincr; pgbackrest backup --stanza=3Dnfs --=
type=3D$Type &amp;&gt; logs/pgbackrest_$(date +&quot;\%F_\%T&quot;)_${Type}=
.log</font><br></div><div><br></div><div>And this is my /etc/pgbackrest.con=
f:</div><div><font face=3D"monospace">[global]<br>repo1-path=3D/Database/ba=
ckups/pgbackrest<br>repo1-cipher-type=3Daes-256-cbc<br>repo1-cipher-pass=3D=
&lt;redacted&gt;<br>repo1-bundle=3Dy<br>repo1-bundle-limit=3D20MiB<br>repo1=
-bundle-size=3D200MiB<br>[nfs]<br>pg1-path=3D/Database/17/data<br>resume=3D=
n<br>start-fast=3Dy<br>stop-auto=3Dy<br>compress-type=3Dzst<br>log-level-co=
nsole=3Ddetail<br>log-level-file=3Dinfo<br>log-path=3D/var/lib/pgsql/logs/p=
gbackrest<br>retention-full=3D4<br>process-max=3D&lt;nproc * 3/4&gt;<br>[nf=
s:archive-push]<br>compress-type=3Dzst</font></div><div><br></div><span cla=
ss=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail=
_signature"><div dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<d=
iv>Don&#39;t boil me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lo=
bster!</div></div></div></div></div></div>

--0000000000005be08806423bad37--