Pgbackrest : Resumable backup of same type exists

Hello,

This warning message indicates that a *resumable backup*, labeled
20250425-115723F, already exists from a previous attempt. The backup system
has detected it and will do the following:

-

*Remove any invalid or corrupted files* from that existing backup
attempt.
-

*Resume* the backup from where it left off, rather than starting over.

This is a *normal and expected message* if a previous backup was
interrupted (due to system shutdown, network error, etc.). It helps avoid
wasting time and resources by reusing valid parts of the incomplete backup.

If you're concerned or just reviewing logs, you generally *don’t need to
take action* unless:

-

The resume process fails.
-

The backup system repeatedly logs this message without completing.
-

You're unsure if the resumed backup will be reliable (e.g., after a
crash).

Would you like help verifying the integrity of the resumed backup once it
finishes?

Else, DELETE the failed backup and take/run fresh backup.
rm -rf /var/lib/pgbackrest/backup/your_stanza_name/20250425-115723F
Thanks & Regards,
Abdul Sayeed

On Thu, May 1, 2025 at 1:20 PM KK CHN <kkchn.in@gmail.com> wrote:

Hi,
Due to a backup failure in my Reposerver, the storage disk ran out of
space, fixed later. I reschedule the cron job to take a full backup but
it show for the last 3 hours

025-05-01 09:30:16.377 P00 WARN: resumable backup 20250425-115723F of
same type exists -- invalid files will be removed then the backup will
resume

This message only I am seeing when looking at the backup log for my repo ,
is this normal ? How much time does it take to start actual backup again ?
Or something wrong ?

root@db1 ~]# cat /etc/pgbackrest/pgbackrest.conf
[My_Repo]
pg1-path=/var/lib/postgres/16/data
pg1-port=5444
pg1-user=postgres
pg-version-force=16

[global]
repo1-host=10.x.x.x
repo1-host-user=postgres

archive-async=y
spool-path=/var/spool/pgbackrest

log-level-console=info
log-level-file=debug
#log-level-file=warn
log-level-stderr=info
delta=y

[global:archive-get]
process-max=2

[global:archive-push]
process-max=4

Regards,
Krishane

--

On Thu, May 1, 2025 at 9:08 AM Abdul Sayeed <abdulsayeed24@gmail.com> wrote:

Hello,

This warning message indicates that a *resumable backup*,

(plus lots more ChatGPT crap)

Please do not use LLMs to answer questions here. If the original poster
wanted that, they could have done it themselves. Further, you are polluting
the pgsql-general archives with computer-generated answers which will in
turn get slurped in again, leading to degradation. People posting here
deserve real answers from real people.

/rant

Original poster, I wouldn't expect it to take three+ hours, but we don't
know how large your backups are. Check /var/log/pgbackrest and see the
latest log entry - it looks like you have "debug" level enabled, so it
should be quite verbose. If the process is running but not writing anything
to the logs, you might want to use strace against its PID to verify what it
is doing (if anything).

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

Hi Greg,

My apologies but the above answer which i gave was not from chatgpt, I had
face similar situation in one of our env. Deleting failed backup helped me.

To be honest I did use chathpt to paraphrase my sentences before posting in
general mail list.

Thanks & Regards,
Abdul Sayeed

On Thu, 1 May, 2025, 11:13 pm Greg Sabino Mullane, <htamfids@gmail.com>
wrote:

Thanks for the helpful hints. The backup finished successfully :
20250425-115723F
timestamp start/stop: 2025-05-01 09:31:36+05:30 / 2025-05-01
14:13:08+

The log doesn't show anything other than (025-05-01 09:30:16.377 P00
WARN: resumable backup 20250425-115723F of same type exists -- invalid
files will be removed then the backup will resume) is due to my Repo
Server configuration was log-level-file = warn in pgbackrest.conf, Its
my mistake, I have enabled log-level-file=debug only in DB cluster
initially.

Now I hv changed in Repo_Server the log reports as expected.
log-level-file=debug
#log-level-file=warn

Thank you,
Krishane

On Thu, May 1, 2025 at 11:13 PM Greg Sabino Mullane <htamfids@gmail.com>
wrote: