Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uAOh7-00EmKo-C9 for pgsql-general@arkaria.postgresql.org; Thu, 01 May 2025 07:50:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uAOh4-001XUs-IX for pgsql-general@arkaria.postgresql.org; Thu, 01 May 2025 07:50:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uAOh4-001XUk-4p for pgsql-general@lists.postgresql.org; Thu, 01 May 2025 07:50:55 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uAOh3-000UJk-0l for pgsql-general@postgresql.org; Thu, 01 May 2025 07:50:54 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-700b17551cdso6223277b3.0 for ; Thu, 01 May 2025 00:50:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1746085852; x=1746690652; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=DoMuM4+d+DUgwGQ+1BMiXT/hal8AuwIt2oQ81+igQVM=; b=BNJ0eDuHZ5qbGPFbYvjz0D/ph2TLHwreoepvWaW2RbH6ll0ZeMan3f3chbD2tfEi3j 6SzSLfi4OqSUi7iYRJWgQgnCspq+w6eWDeK6dLkgaKAbCxi6IBEufwQCgRzhqUdKnCH3 miqNRc4pBW12mX6H59ru6EQRFsY3rlmSp1d1s34vfl7jwPdj123RTCCB4HHmAq5PJtKA IzZAOB31UDDIpv3kHazv43mhkmsJxZ6Is2f/YQT/8ICSoN/fEErK7qWsWgIxBf4V0OE+ fml2XywwEUpRzRCBNIkuiwBdimLP+XRqf1o+Gn6zexvu58YzwOq61AdCKydCeVOA3Q10 0XpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1746085852; x=1746690652; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=DoMuM4+d+DUgwGQ+1BMiXT/hal8AuwIt2oQ81+igQVM=; b=Suw3fbGbZflBWtJurIvSkwMQ0bSuvYiT7Z5AOCqVnGdQmI+NsD1r3Iwr3X9k6qugLf IPqMDjinLV7flYR7/3m9WHvmfXR3FD0T6t3Pc8NjMrC6B3uWv9tnFHFDiX+/1yc6gKgv EyNYAz5VYO9BfH5wCPRJnRIT/TTmuoYFYLNUasYej21VXyOXkog4kCULs1OXM1O9MBJs e0FYjjTv8rBu3UcVIAULzPrCrgvcVc3oLoZoHs7ocTBxQfzANMWSrovXVF8SFTEF8F76 ua9g0OLXh+deor/J9FvJNWY57ZLyEmx3dIWStdR9jrAFI9paxRTX0Hvk56pzuWLUyzbM Aavw== X-Gm-Message-State: AOJu0YyOOBBgxpN4eSbbTMVxwd8e9Fbr5Q2Q4Mab8ahVdL8OC8QTMeDG 1ud5UjsibWHPoqul3lEjPbeb0A/dvE2TPW9zXA4SoA078l0IpmbIiImOW7V9uLgu9ARgDF3FIJS TQq2/Wh+PfPAwR6TbpCtC18UUB9RLbJwo X-Gm-Gg: ASbGncsbKHbvE+9/pZDxBuJI2BOhpF/onaz29LDy356NC76+xmw39c6GrOX4I2CZxK2 z1/BPtE5+NdDpCR18huDNSqGwyTAqpveYXah2nhKjle25rzwFaB7Tvo/hutcGhY8Ii+IUVso6py sgIGuamljzVy+9zdR0VY77idM= X-Google-Smtp-Source: AGHT+IFD8aKwiZDj0zsK/+hddobZU+Z9M5I16IW7C1lc1IRHLEUUKyTrhrIPpnnu5R7jmorTE35fL/Zov1mEy4odgyk= X-Received: by 2002:a05:690c:6483:b0:6fd:4900:bae1 with SMTP id 00721157ae682-708ad5c4b06mr85628617b3.1.1746085852354; Thu, 01 May 2025 00:50:52 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Thu, 1 May 2025 13:23:00 +0530 X-Gm-Features: ATxdqUGqNhwV8zRQyVhNkLReWSr_GI_QH-zJstBAYMhQSmP92XU2wEuS-PuF-aw Message-ID: Subject: Pgbackrest : Resumable backup of same type exists To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000fa241d06340e4ab8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fa241d06340e4ab8 Content-Type: text/plain; charset="UTF-8" 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 --000000000000fa241d06340e4ab8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
Due to a backup failure in my Reposerve= r, 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 show for the last 3 hours= =C2=A0

025-05-01 09:30:16.377 P00 =C2=A0 WARN: res= umable 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 norma= l ? How much time does it take to start actual backup again ?=C2=A0 =C2=A0O= r something wrong ?

root@db1 ~]# cat /etc/pgbackre= st/pgbackrest.conf
[My_Repo]
pg1-path=3D/var/lib/postgres/16/data
= pg1-port=3D5444
pg1-user=3Dpostgres
pg-version-force=3D16

[glo= bal]
repo1-host=3D10.x.x.x
repo1-host-user=3Dpostgres

archive-= async=3Dy
spool-path=3D/var/spool/pgbackrest

log-level-console=3D= info
log-level-file=3Ddebug
#log-level-file=3Dwarn
log-level-stder= r=3Dinfo
delta=3Dy

[global:archive-get]
process-max=3D2
[global:archive-push]
process-max=3D4

R= egards,
Krishane

--000000000000fa241d06340e4ab8--