public inbox for [email protected]
help / color / mirror / Atom feedFrom: Greg Sabino Mullane <[email protected]>
To: KK CHN <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Pgbackrest fails due after an ISP change
Date: Mon, 21 Apr 2025 12:18:27 -0400
Message-ID: <CAKAnmm+dNvyFjRGAoVa954TCygxeoOMLma8qBFaWME9rRpoBcg@mail.gmail.com> (raw)
In-Reply-To: <CAKgGyB-JTZ3ShAyQNMqmc-y0u4=0PzbqCyoCgsJq=EZpSC3-ug@mail.gmail.com>
References: <CAKgGyB-JTZ3ShAyQNMqmc-y0u4=0PzbqCyoCgsJq=EZpSC3-ug@mail.gmail.com>
On Mon, Apr 21, 2025 at 9:03 AM KK CHN <[email protected]> wrote:
>
> ERROR: [082]: WAL segment 000000010000022000000038 was not archived before
> 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
view thread (2+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Pgbackrest fails due after an ISP change
In-Reply-To: <CAKAnmm+dNvyFjRGAoVa954TCygxeoOMLma8qBFaWME9rRpoBcg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox