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 1uAjXc-001Td4-PT for pgsql-general@arkaria.postgresql.org; Fri, 02 May 2025 06:06:33 +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 1uAjXa-007Ug7-Ct for pgsql-general@arkaria.postgresql.org; Fri, 02 May 2025 06:06:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uAjXa-007Ufz-0n for pgsql-general@lists.postgresql.org; Fri, 02 May 2025 06:06:31 +0000 Received: from mail-yw1-x1129.google.com ([2607:f8b0:4864:20::1129]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uAjXY-000f3X-2t for pgsql-general@postgresql.org; Fri, 02 May 2025 06:06:30 +0000 Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-7082ad1355bso12917067b3.1 for ; Thu, 01 May 2025 23:06:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1746165987; x=1746770787; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8CCdFhL2jAqlpD0NEp7Q+t/1CdJfwIc+TvQ5tV4j/DQ=; b=iRe/No3eMU7ObiuKlhlcLT/LRaNWxxyo7QJMhN8RrHwDe4B4bDRSLjHB3HrgvoDDbc swoPm00dyqK+klr8Za3aqCtBwKjuIXZO75I4Fdxyzg8w1tlelyeuUmYHpqf3uORzIXUy 56Ta4Lr0upTm1XHrZLhvrCJ3i2tUNpFRn8SnvATTe+umqIp/KTTxLXCwTteub74KKBTh nAYOvLhUL3VKPTdBGW5lkRVTzO26e1tBpLeZActwFHR07lalEA1Gu7oiEyqwx23IloRC Ry5jEE+h5B92lkdhBY1pqEuCq3cTX9954E7TaYVhj+JONJTIgTJ4CdOWKh0MDTceAOf6 uIlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1746165987; x=1746770787; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8CCdFhL2jAqlpD0NEp7Q+t/1CdJfwIc+TvQ5tV4j/DQ=; b=E6J5gQkwgl3uRnx6PG4biQR3wvTR+hQewZKZOFxRMQmOS6MsEtKsuyKSFwMrS+gXxj 41mDPpdUJCnkfDIfTewzEMWLag2h9JCBTZqKtpx9ei2Q6VzYw9QGqgoXmtxPu5DjzWnM AH/hHYbI/wtA/Pbc7g2lL7+SLiwkWe9R2UjhE4oNR6CZpVGqUglSBnocW+kn0llXnrt4 ucAppfGbOaD9rri7KDBvCzU+08CXGChxqjE2HojOOgyCIY0I+D/M58hJ/lF9YiOIcGgq tRmnh1jere8LZzRLonAmV/XgxkgEuvCcmtfTZOD0djSr22+ibAuZeX4RcFE5tJln+5v3 DnwQ== X-Forwarded-Encrypted: i=1; AJvYcCV2aU5O9tLUnG4goU0zrmPmT0fHwCZbqOXES9z3oI7uufAGM33WuMT2K+s7Y01xzy2yLBAlYEarMa2oG7CU@postgresql.org X-Gm-Message-State: AOJu0Yw/H5oOQABSNczdd4WtrZadr0cV2BlIonknSo4HYegZjxBDp0PI kNJvXIN+UFmNPnZ3VKAeEateinvnUHEDT8WZbjKrfkrApoKGmTxXy4A5XqvzEBZMgC9OoNk7XuS u+uHOzDDMJ5cNFPiWW/0DXZ6YSGE= X-Gm-Gg: ASbGnctK9Y3GaLM9XYC92Z+aFrKwS2HBXBe1TcBHfdf5ucQz2cSxb4d4ahWXSnhCRiJ A2uDNHa1cO89WmAXmIcuMjXSC7tCKpAV3TpWWYCCqRb/yjJp+uJ9iMN8OP6z1wC0GYvYTyro2rU bRczU+ejYWPC09MPN+ciLnRuk= X-Google-Smtp-Source: AGHT+IFKyI/LctZ6p42Bx+c7yzhRrdNWNJQQkQo41amXyEumsMqy5AIoZzq9sI7ERFiLL9TNUYlXIsUyauVAZ7F259w= X-Received: by 2002:a05:690c:4983:b0:6f7:ac3f:d589 with SMTP id 00721157ae682-708cf261ae6mr25404787b3.36.1746165986901; Thu, 01 May 2025 23:06:26 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: KK CHN Date: Fri, 2 May 2025 11:38:33 +0530 X-Gm-Features: ATxdqUEsL70U-y4wBit4Eg4woeIky7dq7MUHL9lekkJ8Qf6my0ui4w0h7IHoj-Y Message-ID: Subject: Re: Pgbackrest : Resumable backup of same type exists To: Greg Sabino Mullane Cc: Abdul Sayeed , pgsql-general Content-Type: multipart/alternative; boundary="0000000000005e4817063420f382" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005e4817063420f382 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 =3D warn in pgbackrest.conf, It= s my mistake, I have enabled log-level-file=3Ddebug only in DB cluster initially. Now I hv changed in Repo_Server the log reports as expected. log-level-file=3Ddebug #log-level-file=3Dwarn Thank you, Krishane On Thu, May 1, 2025 at 11:13=E2=80=AFPM Greg Sabino Mullane wrote: > On Thu, May 1, 2025 at 9:08=E2=80=AFAM Abdul Sayeed > 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 polluti= ng > 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 anythi= ng > 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 > > --0000000000005e4817063420f382 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for the=C2=A0helpful hints. The ba= ckup finished successfully : 20250425-115723F
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 timestamp start/stop: 2025-05-01 09:31:36+05:30 / 2025-05= -01 14:13:08+

=C2=A0The log doesn't show=C2=A0 = anything=C2=A0 other than (025-05-01 09:30:16.377 P00 =C2=A0 WARN: resumabl= e backup 20250425-115723F of same type exists -- invalid files will be remo= ved then the backup will resume)=C2=A0 =C2=A0is due to my Repo Server confi= guration was=C2=A0 =C2=A0 log-level-file =3D warn in pgbackrest.conf,=C2=A0= Its my mistake, I have enabled=C2=A0 =C2=A0log-level-file=3Ddebug=C2=A0 on= ly in=C2=A0 DB cluster=C2=A0 initially.=C2=A0

Now = I hv changed in Repo_Server=C2=A0 the log reports as expected.=C2=A0
<= div>log-level-file=3Ddebug
#log-level-file=3Dwarn=C2=A0=C2=A0

Thank=C2=A0you,=C2=A0
Krishane









On Thu, May 1, 2025 at 11:13=E2=80=AFPM= Greg Sabino Mullane <htamfids@gma= il.com> wrote:
On Thu, May 1, 2025 at 9:08=E2=80= =AFAM Abdul Sayeed <abdulsayeed24@gmail.com> wrote:
Hello,

This warning message indicates that a r= esumable backup,

(plus lot= s more ChatGPT crap)

Please do not use LLMs to ans= wer questions here. If the original poster wanted that, they could have don= e it themselves. Further, you are polluting the pgsql-general archives with= computer-generated answers which will in turn get slurped in again, leadin= g 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 la= rge your backups are. Check /var/log/pgbackrest and see the latest log entr= y - 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 l= ogs, you might want to use strace against its=C2=A0PID to verify what it is= doing (if anything).

Cheers,
Greg
=

=
--
Enterprise = Postgres Software Products & Tech Support

--0000000000005e4817063420f382--