Re: Pgbackrest fails due after an ISP change

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: KK CHN <kkchn(dot)in(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Pgbackrest fails due after an ISP change
Date: 2025-04-21 16:18:27
Message-ID: CAKAnmm+dNvyFjRGAoVa954TCygxeoOMLma8qBFaWME9rRpoBcg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Apr 21, 2025 at 9:03 AM KK CHN <kkchn(dot)in(at)gmail(dot)com> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Anton Shepelev 2025-04-21 16:26:55 Re: Cannot turn track_counts on
Previous Message Thiemo Kellner 2025-04-21 16:12:13 Re: Order of update