MIME-Version: 1.0
From: KK CHN <kkchn.in@gmail.com>
Date: Mon, 21 Apr 2025 18:35:58 +0530
Message-ID: <CAKgGyB-JTZ3ShAyQNMqmc-y0u4=0PzbqCyoCgsJq=EZpSC3-ug@mail.gmail.com>
Subject: Pgbackrest fails due after an ISP change
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000060f60b0633497f06"
Archived-At: <https://www.postgresql.org/message-id/CAKgGyB-JTZ3ShAyQNMqmc-y0u4%3D0PzbqCyoCgsJq%3DEZpSC3-ug%40mail.gmail.com>
Precedence: bulk

--00000000000060f60b0633497f06
Content-Type: text/plain; charset="UTF-8"

List,

I am running  a pgbackrest(2.52.1) backup setup for a postgres(16)
server(RHEL9.4)  to a repo server RHEL 9.4..

The pgbackrest was working fine and the remote repo server got regular
backups through cron scheduler.

Suddenly there was an ISP change at our  end,  the VPN tunnel  between DB
server and Repo server was lost for  24 hours due to VPN tunnel crash.
later I restored the VPN tunnel

After that  the cron scheduler does not perform the pgbackrest backup. It
fails!!!

So I performed a full backup to overcome this ..  But it fails  with the
cron command (  38 14 * * 1 pgbackrest --type=full  --stanza=My_Repo
backup)


ERROR: [082]: WAL segment 000000010000022000000038 was not archived before
the 60000ms timeout
                                    HINT: check the archive_command to
ensure that all options are correct (especially --stanza).
                                    HINT: check the PostgreSQL server log
for errors.
                                    HINT: run the 'start' command if the
stanza was previously stopped.

--------------------------------------------------------------------
                                    If SUBMITTING AN ISSUE please provide
the following information:

                                    version: 2.52.1
                                    command: backup
                                    options: --delta
--exec-id=492671-6f2068fc --log-level-console=info --log-level-file=debug
--pg1-host=10.x.y.202 --pg1-host-user=enterprisedb
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=5
--repo1-block --repo1-bundle --repo1-cipher-pass=<redacted>
--repo1-cipher-type=aes-256-cbc --repo1-path=/DBBACKUP
--repo1-retention-diff=3 --repo1-retention-full=3 --stanza=KTA_Repo
--start-fast --type=full
2025-04-21 14:39:07.335 P00   INFO: backup command end: aborted with
exception [082]
2025-04-21 14:39:07.335 P00  DEBUG:     command/exit::exitSafe: => 82
2025-04-21 14:39:07.936 P00  DEBUG:     main::main: => 82

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

Any hint  appreciated ..

Thanks
Krishane

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

<div dir=3D"ltr">List,<div><br></div><div>I am running=C2=A0 a pgbackrest(2=
.52.1) backup setup for a postgres(16) server(RHEL9.4)=C2=A0 to a repo serv=
er RHEL 9.4..=C2=A0 =C2=A0</div><div><br></div><div>The pgbackrest was work=
ing fine and the remote repo server got regular backups through cron schedu=
ler.=C2=A0</div><div><br></div><div>Suddenly=C2=A0there was an ISP change a=
t our=C2=A0 end,=C2=A0 the VPN tunnel=C2=A0 between DB server and Repo serv=
er was lost for=C2=A0 24 hours due to VPN tunnel crash.=C2=A0 later I resto=
red=C2=A0the VPN tunnel</div><div><br></div><div>After that=C2=A0 the cron =
scheduler does not perform the pgbackrest backup. It fails!!!</div><div><br=
></div><div>So I performed a full backup to overcome this ..=C2=A0 But it f=
ails=C2=A0 with the cron command (=C2=A0=C2=A038 14 * * 1 pgbackrest --type=
=3Dfull =C2=A0--stanza=3DMy_Repo backup)=C2=A0</div><div><br></div><div><br=
></div><div>ERROR: [082]: WAL segment 000000010000022000000038 was not arch=
ived before the 60000ms timeout<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 HINT: check the archive_command to ensure that all options ar=
e correct (especially --stanza).<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 HINT: check the PostgreSQL server log for errors.<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 HINT: run the &#39;start&#39;=
 command if the stanza was previously stopped.<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -----------------------------------------------=
---------------------<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 If SUBMITTING AN ISSUE please provide the following information:<br><br=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 version: 2.52.1<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 command: backup<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 options: --delta --exec-id=3D=
492671-6f2068fc --log-level-console=3Dinfo --log-level-file=3Ddebug --pg1-h=
ost=3D10.x.y.202 --pg1-host-user=3Denterprisedb --pg1-path=3D/data/edb/as16=
/data --pg-version-force=3D16 --process-max=3D5 --repo1-block --repo1-bundl=
e --repo1-cipher-pass=3D&lt;redacted&gt; --repo1-cipher-type=3Daes-256-cbc =
--repo1-path=3D/DBBACKUP --repo1-retention-diff=3D3 --repo1-retention-full=
=3D3 --stanza=3DKTA_Repo --start-fast --type=3Dfull<br></div><div>2025-04-2=
1 14:39:07.335 P00 =C2=A0 INFO: backup command end: aborted with exception =
[082]<br>2025-04-21 14:39:07.335 P00 =C2=A0DEBUG: =C2=A0 =C2=A0 command/exi=
t::exitSafe: =3D&gt; 82<br>2025-04-21 14:39:07.936 P00 =C2=A0DEBUG: =C2=A0 =
=C2=A0 main::main: =3D&gt; 82</div><div><br></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><br></div><div>Any hint=C2=A0 =
appreciated ..=C2=A0</div><div><br></div><div>Thanks</div><div>Krishane</di=
v><div><br></div><div><br></div></div>

--00000000000060f60b0633497f06--