Re: PgBackRest fails due to filesystem full

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: KK CHN <kkchn(dot)in(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: PgBackRest fails due to filesystem full
Date: 2025-04-08 16:58:10
Message-ID: CAKAnmmK4MDw3RzbnndMvyK6OjbTkv+8koq2FTyZsDBvX7_WW7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Apr 7, 2025 at 5:32 AM KK CHN <kkchn(dot)in(at)gmail(dot)com> wrote:

> *ERROR: [082]: WAL segment 00000001000001EB000000*4B was not archived
> before the 60000ms timeout
>

This is the part you need to focus on. Look at your Postgres logs and find
out why the archiver is failing. You can also test this without trying a
whole backup by using the "check" command:
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 Amitabh Kant 2025-04-08 17:37:32 Re: timescaledb vs NULL vs pg_timeseries vs partman + pgcron + pg_ivm
Previous Message Achilleas Mantzios - cloud 2025-04-08 16:10:15 timescaledb vs NULL vs pg_timeseries vs partman + pgcron + pg_ivm