Re: Pgbackrest : Resumable backup of same type exists

From: Abdul Sayeed <abdulsayeed24(at)gmail(dot)com>
To: KK CHN <kkchn(dot)in(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Pgbackrest : Resumable backup of same type exists
Date: 2025-05-01 13:08:07
Message-ID: CAHb=FFxVqia=yxO8vTMnohZHYWhhWvDA6CfMOJRW5vW8WDTLmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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(dot)in(at)gmail(dot)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(at)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
>
>

--

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2025-05-01 13:19:25 Re: Upgrading PG11 to PG17 without dump/restore
Previous Message Durumdara 2025-05-01 13:06:22 Upgrading PG11 to PG17 without dump/restore