MIME-Version: 1.0
References: <CAKgGyB-8ap3-zna_gkpEQNfzgWzu4QwO5Y6U_-2q1JcjK=UTvw@mail.gmail.com>
In-Reply-To: <CAKgGyB-8ap3-zna_gkpEQNfzgWzu4QwO5Y6U_-2q1JcjK=UTvw@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 7 May 2025 09:16:01 -0400
Message-ID: <CAKAnmm+ToUhZPGrzDssn2S4ie+znw0hVH_xKXe=6XRMSYjQS5Q@mail.gmail.com>
Subject: Re: Pgbackrest failure for INCR and DIFF but not FULL backup
To: KK CHN <kkchn.in@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000042edc06348b8b54"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BToUhZPGrzDssn2S4ie%2Bznw0hVH_xKXe%3D6XRMSYjQS5Q%40mail.gmail.com>
Precedence: bulk

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

On Wed, May 7, 2025 at 7:15=E2=80=AFAM KK CHN <kkchn.in@gmail.com> wrote:

> *archive_command =3D 'pgbackrest --stanza=3DMy_Repo archive-push %p && cp=
 %p
> /data/archive/%f' *
>

Don't do this. You are archiving twice, and worse, the first part is using
async archiving. Remove that whole "cp" part. Once that is fixed, run:

pgbackrest --stanza=3DMy_Repo check

to verify that WAL is being archived quickly and properly. Then test your
backups, checking the file
/var/log/pgbackrest/My_Repo-archive-push-async.log and your postgres log if
any problems arise.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

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

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, May 7, 2025 at 7:15=E2=80=AFAM KK=
 CHN &lt;<a href=3D"mailto:kkchn.in@gmail.com">kkchn.in@gmail.com</a>&gt; w=
rote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><b>archive_command=
 =3D &#39;pgbackrest --stanza=3DMy_Repo archive-push %p &amp;&amp; cp %p /d=
ata/archive/%f&#39;=C2=A0</b></div></div></blockquote><div><br></div><div>D=
on&#39;t do this. You are archiving twice, and worse, the first part is usi=
ng async archiving. Remove that whole &quot;cp&quot; part. Once that is fix=
ed, run:</div><div><br></div><div>pgbackrest --stanza=3DMy_Repo check</div>=
<div><br></div><div>to verify that WAL is being archived quickly and proper=
ly. Then test your backups, checking the file /var/log/pgbackrest/My_Repo-a=
rchive-push-async.log and your postgres log if any problems arise.</div><di=
v><br></div><div>Cheers,</div></div><div dir=3D"ltr" class=3D"gmail_signatu=
re"><div dir=3D"ltr"><div>Greg</div><div><br></div><div>--</div><div>Crunch=
y Data - <a href=3D"https://www.crunchydata.com" target=3D"_blank">https://=
www.crunchydata.com</a></div><div>Enterprise Postgres Software Products &am=
p; Tech Support</div><div><br></div></div></div></div>

--000000000000042edc06348b8b54--