Message-ID: <65d30861.5d0a0220.ef3a3.0214@mx.google.com>
Sender: Michael Banck <mbanck@gmail.com>
Date: Mon, 19 Feb 2024 08:50:57 +0100
From: Michael Banck <mbanck@gmx.net>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
	Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Full backup failed
References: 
 <CAJk5AtY5GwkDuygEnnyHpKxUpMv6PLTHtaPp8v_7wbTmb3pfNA@mail.gmail.com>
 <4a8ed0487aada47fe5d0263055862494a52216ea.camel@cybertec.at>
 <CAJk5AtYvQf42EdHT30sFJtLoTkOiHJj8kWsaworLafyM1Wquvw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAJk5AtYvQf42EdHT30sFJtLoTkOiHJj8kWsaworLafyM1Wquvw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/65d30861.5d0a0220.ef3a3.0214%40mx.google.com>
Precedence: bulk

Hi,

On Mon, Feb 19, 2024 at 01:13:36PM +0530, Rajesh Kumar wrote:
> Archive command is set to pgbackrest --stanza=db archive-push "%p"

That looks right.
 
> There were no such issue since last year.
> 
> In postgres logs, don't see anything related to archive. But I see,
> WARNING,0100, aborting backup due to backend exiting before pg_backup_stop
> was called....pgbackrest[backup] client backend, 58568621736954596

This error is due to the timeout that pgbackrest backend suffered.

I think one reason pgbackrest backup could time out after 60s is WAL
pileup, i.e. it tries to check whether the current WAL archive was
successfully archived in 60s but if there is a huge lag in archiving
(for whatever reason) the current WAL segment might not get archived for
another 60 seconds and the backup fails.

So if you have that data in monitoring, check whether archiving was
maybe lagging behind, or otherwise, check whether there are a lot of
.ready files in the pg_wal/archive_status sub-directory right now and/or
possibly just try the backup again.


Michael