MIME-Version: 1.0
References: <CAKgGyB8_o_uBApZjefiebyJjh19roKpK7=rCsuHXiL_OoxqNVw@mail.gmail.com>
In-Reply-To: <CAKgGyB8_o_uBApZjefiebyJjh19roKpK7=rCsuHXiL_OoxqNVw@mail.gmail.com>
From: Abdul Sayeed <abdulsayeed24@gmail.com>
Date: Thu, 1 May 2025 18:38:07 +0530
Message-ID: <CAHb=FFxVqia=yxO8vTMnohZHYWhhWvDA6CfMOJRW5vW8WDTLmw@mail.gmail.com>
Subject: Re: Pgbackrest : Resumable backup of same type exists
To: KK CHN <kkchn.in@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000001e9f07063412bac3"
Archived-At: <https://www.postgresql.org/message-id/CAHb%3DFFxVqia%3DyxO8vTMnohZHYWhhWvDA6CfMOJRW5vW8WDTLmw%40mail.gmail.com>
Precedence: bulk

--0000000000001e9f07063412bac3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=99t ne=
ed 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=E2=80=AFPM 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=3D/var/lib/postgres/16/data
> pg1-port=3D5444
> pg1-user=3Dpostgres
> pg-version-force=3D16
>
> [global]
> repo1-host=3D10.x.x.x
> repo1-host-user=3Dpostgres
>
> archive-async=3Dy
> spool-path=3D/var/spool/pgbackrest
>
> log-level-console=3Dinfo
> log-level-file=3Ddebug
> #log-level-file=3Dwarn
> log-level-stderr=3Dinfo
> delta=3Dy
>
> [global:archive-get]
> process-max=3D2
>
> [global:archive-push]
> process-max=3D4
>
> Regards,
> Krishane
>
>

--

--0000000000001e9f07063412bac3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hello,<div><p class=3D"gmail-">This warni=
ng message indicates that a <strong>resumable backup</strong>, labeled <cod=
e>20250425-115723F</code>, already exists from a previous attempt. The back=
up system has detected it and will do the following:</p>
<ul>
<li class=3D"gmail-">
<p class=3D"gmail-"><strong>Remove any invalid or corrupted files</strong> =
from that existing backup attempt.</p>
</li>
<li class=3D"gmail-">
<p class=3D"gmail-"><strong>Resume</strong> the backup from where it left o=
ff, rather than starting over.</p>
</li>
</ul>
<p class=3D"gmail-">This is a <strong>normal and expected message</strong> =
if a previous backup was interrupted (due to system shutdown, network error=
, etc.). It helps avoid wasting time and resources by reusing valid parts o=
f the incomplete backup.</p>
<p class=3D"gmail-">If you&#39;re concerned or just reviewing logs, you gen=
erally <strong>don=E2=80=99t need to take action</strong> unless:</p>
<ul>
<li class=3D"gmail-">
<p class=3D"gmail-">The resume process fails.</p>
</li>
<li class=3D"gmail-">
<p class=3D"gmail-">The backup system repeatedly logs this message without =
completing.</p>
</li>
<li class=3D"gmail-">
<p class=3D"gmail-">You&#39;re unsure if the resumed backup will be reliabl=
e (e.g., after a crash).</p>
</li>
</ul>
<p class=3D"gmail-">Would you like help verifying the integrity of the resu=
med backup once it finishes?<br><br>Else, DELETE the failed backup and take=
/run fresh backup.<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0rm -rf /var/lib/pgbackrest=
/backup/your_stanza_name/20250425-115723F<br></p></div></div><div>Thanks &a=
mp; Regards,</div><div>Abdul Sayeed</div><div><br></div><div class=3D"gmail=
_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Thu,=
 May 1, 2025 at 1:20=E2=80=AFPM KK CHN &lt;<a href=3D"mailto:kkchn.in@gmail=
.com">kkchn.in@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr"><div>Hi,</div><div>Due to a backup=
 failure in my Reposerver, the storage disk ran out of space, fixed later.=
=C2=A0 =C2=A0I reschedule=C2=A0the cron job to take a full backup but it sh=
ow for the last 3 hours=C2=A0</div><div><br></div><div>025-05-01 09:30:16.3=
77 P00 =C2=A0 WARN: resumable backup 20250425-115723F of same type exists -=
- invalid files will be removed then the backup will resume</div><div><br><=
/div><div>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 backu=
p again ?=C2=A0 =C2=A0Or something wrong ?</div><div><br></div><div>root@db=
1 ~]# cat /etc/pgbackrest/pgbackrest.conf<br>[My_Repo]<br>pg1-path=3D/var/l=
ib/postgres/16/data<br>pg1-port=3D5444<br>pg1-user=3Dpostgres<br>pg-version=
-force=3D16<br><br>[global]<br>repo1-host=3D10.x.x.x<br>repo1-host-user=3Dp=
ostgres<br><br>archive-async=3Dy<br>spool-path=3D/var/spool/pgbackrest<br><=
br>log-level-console=3Dinfo<br>log-level-file=3Ddebug<br>#log-level-file=3D=
warn<br>log-level-stderr=3Dinfo<br>delta=3Dy<br><br>[global:archive-get]<br=
>process-max=3D2<br><br>[global:archive-push]</div><div>process-max=3D4</di=
v><div><br></div><div>Regards,</div><div>Krishane</div><div><br></div></div=
>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature"><div dir=3D"ltr"><div dir=3D"ltr"><br></div></div></div></div>

--0000000000001e9f07063412bac3--