MIME-Version: 1.0
References: <CAKgGyB-JTZ3ShAyQNMqmc-y0u4=0PzbqCyoCgsJq=EZpSC3-ug@mail.gmail.com>
In-Reply-To: <CAKgGyB-JTZ3ShAyQNMqmc-y0u4=0PzbqCyoCgsJq=EZpSC3-ug@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Mon, 21 Apr 2025 12:18:27 -0400
Message-ID: <CAKAnmm+dNvyFjRGAoVa954TCygxeoOMLma8qBFaWME9rRpoBcg@mail.gmail.com>
Subject: Re: Pgbackrest fails due after an ISP change
To: KK CHN <kkchn.in@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000fbd1e606334c39fc"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BdNvyFjRGAoVa954TCygxeoOMLma8qBFaWME9rRpoBcg%40mail.gmail.com>
Precedence: bulk

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

On Mon, Apr 21, 2025 at 9:03=E2=80=AFAM KK CHN <kkchn.in@gmail.com> wrote:

>
> ERROR: [082]: WAL segment 000000010000022000000038 was not archived befor=
e
> the 60000ms timeout
>
...

> How can I make the full backup command not to check the  WAL was archived
> or not  to the repo server for atleast once ?
>

You cannot. WAL is an integral part of the backups. You should run the
pgbackrest "check" command and look at your Postgres logs to figure out why
WAL files are not being archived. Once that is solved, try the backup again=
.

https://pgbackrest.org/command.html#command-check


Cheers,
Greg

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

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Apr 21,=
 2025 at 9:03=E2=80=AFAM KK CHN &lt;<a href=3D"mailto:kkchn.in@gmail.com">k=
kchn.in@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div><br></div><div>ERROR: [082]: WAL seg=
ment 000000010000022000000038 was not archived before the 60000ms timeout<b=
r></div></div></blockquote><div>...=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr"><div></div><div>How can I make the f=
ull backup command not to check the=C2=A0 WAL was archived or not=C2=A0 to =
the repo server for atleast once ?</div></div></blockquote><div><br></div><=
div>You cannot. WAL is an integral part of the backups. You should run the =
pgbackrest &quot;check&quot; command and look at your Postgres logs to figu=
re out why WAL files are not being archived. Once that is solved, try the b=
ackup again.</div><div><br></div><div><a href=3D"https://pgbackrest.org/com=
mand.html#command-check">https://pgbackrest.org/command.html#command-check<=
/a></div><div><br></div><div><br></div><div>Cheers,</div></div><div dir=3D"=
ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div>Greg</div><div><br></d=
iv><div>--</div><div>Crunchy Data - <a href=3D"https://www.crunchydata.com"=
 target=3D"_blank">https://www.crunchydata.com</a></div><div>Enterprise Pos=
tgres Software Products &amp; Tech Support</div><div><br></div></div></div>=
</div>

--000000000000fbd1e606334c39fc--