Request a Demo
Home   >   mailing lists

Re: pgbackrest after a network outage unable to perform backup [fails always] - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: pgbackrest after a network outage unable to perform backup [fails always]
Date
Msg-id CAKAnmmLMG74OpVK0TTCr0dpK_LzJPRXTKOqs-yObJ-w3cUufvQ@mail.gmail.com
Whole thread Raw
In response to pgbackrest after a network outage unable to perform backup [fails always]  (KK CHN <kkchn.in@gmail.com>)
Responses Re: pgbackrest after a network outage unable to perform backup [fails always]
List pgsql-general
Tree view
On Tue, Feb 24, 2026 at 5:18 AM KK CHN <kkchn.in@gmail.com> 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

--
Enterprise Postgres Software Products & Tech Support

pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Recovery Verification
Next
From: Adrian Klaver
Date:
Subject: Re: Recovery Verification