Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vEAAG-006UP4-VF for pgsql-admin@arkaria.postgresql.org; Wed, 29 Oct 2025 17:40:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vEAAF-002WoO-Ps for pgsql-admin@arkaria.postgresql.org; Wed, 29 Oct 2025 17:40:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vEAAF-002WoE-Be for pgsql-admin@lists.postgresql.org; Wed, 29 Oct 2025 17:40:50 +0000 Received: from mx0a-0039f802.pphosted.com ([205.220.164.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vEAAA-004vBM-2M for pgsql-admin@lists.postgresql.org; Wed, 29 Oct 2025 17:40:49 +0000 Received: from pps.filterd (m0209981.ppops.net [127.0.0.1]) by mx0b-0039f802.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 59TG7GLf1138185 for ; Wed, 29 Oct 2025 10:40:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dat.com; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=ppdk230404; bh=9POgo+wzWMHeYS3Hv8qxhHP GqZ2UgI63lmfkbYmZnyA=; b=ouScv8OJZyage0W3o1prcFRkUA/u2gOZSnv1NTm 9rMbXI1o+UDkp+KVBtlXNoyOVrlXPwXTE44nkxQ9sgRm0QKiPbMpb9L+m/q8RayJ cAYs8gOoOV1fA6z8H4HfcwfTC6q8QtzPw26uUdKNxz4hz1+C9l6doQ5MZ70OmOF+ X0AUV3AugMx7z1n1Hn4Ybt9AQVESX9jIo+ADHYtNLKi+oly+mrT9pwCKYsKN2IQV NDUXgvbPek0QsKQag7Lx1xjB8WmWJyCPkY+0xt51D0hRll55V27szgCYAoj4cokr a48QwLPGyNTK8sm4Fp7OSikvyMQc9M1AUJuQF3NfPYRc3RA== Received: from mail-ej1-f71.google.com (mail-ej1-f71.google.com [209.85.218.71]) by mx0b-0039f802.pphosted.com (PPS) with ESMTPS id 4a349g1p4q-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Wed, 29 Oct 2025 10:40:42 -0700 (PDT) Received: by mail-ej1-f71.google.com with SMTP id a640c23a62f3a-b7043504650so17627566b.0 for ; Wed, 29 Oct 2025 10:40:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761759640; x=1762364440; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9POgo+wzWMHeYS3Hv8qxhHPGqZ2UgI63lmfkbYmZnyA=; b=tT9MUB6xKwp3V6b2uGG3Tf2cASsfcb07n+Pbjdwmg7XsEF8dBdQcSix6mHQ35xYVws a04Zdyxv2asuluCh8ksKyeb9cyOp7o4WesHdnhogoUkAHOQAfGqqG0RQRSMD24FVbTtW /387ySIPoAmWvFb4evl+jRBUSHyMPVIl0S1l9OYg5VndMT2scH8N2xCxl4EL1bAN+PmC AshEaUGYPbuK3J8CX4JsGGzfCFcLxiGKgVOayvN9IC/Efz+RIfGg+W+yqfi8upFPoGlm IMKpJ3yOpOn99NvQMuSrtn0IkwfhsRcYHo7HSjPea01E627gskrREQ6lS4MdncFdM0im bYog== X-Gm-Message-State: AOJu0YzY5cFG+0bGCm67nE7j+Ns9zn4AkU691J/YWTkq+R+j0TGUVrJS zH1xr4jLAGZpZLgddxElnBCS+/LHjEFZS3h39Zun+5IEQAWzvpIO0h1EN3azrpvunMTTnPtEL9B ZN8WRgPSBdVteVXkZ5hc17GSWMgAT3uR4qAfWhCOgRhZ166iJ6tCOymSnwN6nt36XFb7ZyNZkPo 741aBWCfpt3nzC3PIoeIccFbYiTqqHtb1n8Zg2vCTZVnOYqEDKpZxxSsUChT1kRGFcNE4pNlg= X-Gm-Gg: ASbGnctiXdOv2hOdsbdFlHorNMqB7Y3pYgyBnikCS5X1ywalPgaRmrZu4FEzK1CYu3C bTIktpUEEE1s9OLDFH2PDHqZl+yqM71TuhMAHCjMPdEeMVUFa1dIeMcySlST37end9C5a64wJlY 0FmondP96FidZQQ0UY9wQaHnRPSzhbwC9H9Qr9XWqkrfxOGwAqslouXQ== X-Received: by 2002:a17:907:7fa3:b0:afe:159:14b1 with SMTP id a640c23a62f3a-b705207e80fmr44366166b.9.1761759640412; Wed, 29 Oct 2025 10:40:40 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGVST9J9nIe/o8UNx+0Q1xGFX/FXQ1cA5khN3hKqGHFpd04YnrPJmzuBprF8uOMHZTX7m4GTWTfUN7hGjPzSIc= X-Received: by 2002:a17:907:7fa3:b0:afe:159:14b1 with SMTP id a640c23a62f3a-b705207e80fmr44364866b.9.1761759639998; Wed, 29 Oct 2025 10:40:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sam Stearns Date: Wed, 29 Oct 2025 10:40:28 -0700 X-Gm-Features: AWmQ_blGaC2EwiN_PQkXBvmDzGL3LrJSjbaFaYnkBcG6KkEqoK2zxbCb6GJkAy0 Message-ID: Subject: Re: pg_basebackup --incremental To: Ron Johnson Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000085a44706424fa189" X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2025-10-29_07,2025-10-29_03,2025-10-01_01 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000085a44706424fa189 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFPM Sam Stearns w= rote: > Thanks, Ron! We'll take another look at pgBackRest. > > On Tue, Oct 28, 2025 at 10:52=E2=80=AFAM Ron Johnson > wrote: > >> On Tue, Oct 28, 2025 at 1: 43 PM Sam Stearns >> 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=E2=80=AFPM Sam Stearns 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_basebac= kup >>> 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$Ty= pe &> >> logs/pgbackrest_$(date +"\%F_\%T")_${Type}.log >> 15 01 * * 1-6 Type=3Dincr; pgbackrest backup --stanza=3Dnfs --type=3D$Ty= pe &> >> 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 >> 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 >> [nfs:archive-push] >> compress-type=3Dzst >> >> -- >> Death to , and butter sauce. >> Don't boil me, I'm still alive. >> lobster! >> > > > -- > > Samuel Stearns > Team Lead - Database > c: 971 762 6879 | o: 971 762 6879 | DAT.com > > > > --=20 Samuel Stearns Team Lead - Database c: 971 762 6879 | o: 971 762 6879 | DAT.com --00000000000085a44706424fa189 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Ron,

If I may, please.=C2=A0 What ar= e the postgres.conf parameters you set specifically for pgBackRest?

Thanks,

Sam

On Tue, Oct 28, 2025 at 3:21=E2=80=AFPM Sam Stearns <sam.stearns@dat.com> wrote:
Thanks, Ron!= =C2=A0 We'll take another look at pgBackRest.

On Tue, Oct 28, 2025 at 10= :52=E2=80=AFAM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
On Tue, Oct 28, 2025 at 1:=E2=80=8A43 PM Sam Stearns <sam.=E2=80=8Astear= ns@=E2=80=8Adat.=E2=80=8Acom> wrote: Howdy, We're running version 17= .=E2=80=8A6. Would anyone be able to point me to, or provide, some sample u= se 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.
=C2=A0
ZjQcmQRYFpfptBannerEnd
On Tue, Oct 28, 2025 at 1:43=E2=80=AFPM S= am Stearns <sam= .stearns@dat.com> wrote:
Howdy,

We're running version=C2=A017.6.=C2=A0 Would=C2=A0any= one be able to point me to, or provide, some sample use cases / scripts / u= sage to deploy a pg_basebackup full=C2=A0+ --incremental strategy as a back= up solution, please?

The question confuses me a bit (though maybe because weekly "fu= ll", and remainder "incremental" 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).

This is in the "postgres" crontab:
15 01 * * Sun Type=3Dfull; pgbackrest backup --stanza=3Dnfs --ty= pe=3D$Type &> logs/pgbackrest_$(date +"\%F_\%T")_${Type}.l= og
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/p= gbackrest
repo1-cipher-type=3Daes-256-cbc
repo1-cipher-pass=3D<red= acted>
repo1-bundle=3Dy
repo1-bundle-limit=3D20MiB
repo1-bundle= -size=3D200MiB
[nfs]
pg1-path=3D/Database/17/data
resume=3Dn
st= art-fast=3Dy
stop-auto=3Dy
compress-type=3Dzst
log-level-console= =3Ddetail
log-level-file=3Dinfo
log-path=3D/var/lib/pgsql/logs/pgback= rest
retention-full=3D4
process-max=3D<nproc * 3/4>
[nfs:arc= hive-push]
compress-type=3Dzst

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


--

Samuel Stearns
Team Lead - Databas= e
c: 971 76= 2 6879 = | o: 97= 1 762 6879 | D= AT.com




--

Samuel Stearns
Team Lead - Database
= c: 971 762 687= 9 | o: 971 762= 6879 |= DAT.co= m

=


--00000000000085a44706424fa189--