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 after a network outage unable to perform backup [fails always]
Date: Tue, 24 Feb 2026 10:49:30 -0500
Message-ID: <CAKAnmmLMG74OpVK0TTCr0dpK_LzJPRXTKOqs-yObJ-w3cUufvQ@mail.gmail.com> (raw)
In-Reply-To: <CAKgGyB_4kn5Sec8jtY4MfvKcaeXTPdsVQd5m8TU3GF4mGcnBMA@mail.gmail.com>
References: <CAKgGyB_4kn5Sec8jtY4MfvKcaeXTPdsVQd5m8TU3GF4mGcnBMA@mail.gmail.com>
On Tue, Feb 24, 2026 at 5:18 AM KK CHN <[email protected]> wrote:
> This goes for hours now, not yet finished. Is this normal behaviour ?
>
Yes, if there is a lot of WAL
My goal is to initiate a full backup afresh on the reposerver , so it
> doesn't matter all the old piled up WAL files
>
You will need to (carefully!) disable pgbackrest archiving, clean up the
old WAL, then start it up again. Basic sequence:
1. Set archive_command to '/bin/true'
2. Kill any existing pgbackrest processes, empty out the spool directory
3. Wait for Postgres to cleanup / recycle the WAL (speed up with a manual
CHECKPOINT)
4. Restore your archive_command to the pgbackrest version
5. Run pgbackrest check to verify WALs are being archived again
6. Run a full backup
Ideally, test these steps on a dev system, and understand why each step and
why in that order. :)
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 after a network outage unable to perform backup [fails always]
In-Reply-To: <CAKAnmmLMG74OpVK0TTCr0dpK_LzJPRXTKOqs-yObJ-w3cUufvQ@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