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 1uCzDg-004wpg-Sm for pgsql-general@arkaria.postgresql.org; Thu, 08 May 2025 11:15:17 +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 1uCzCh-002dgo-M6 for pgsql-general@arkaria.postgresql.org; Thu, 08 May 2025 11:14:15 +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 1uCzCh-002dgg-9f for pgsql-general@lists.postgresql.org; Thu, 08 May 2025 11:14:15 +0000 Received: from mail-yb1-xb2d.google.com ([2607:f8b0:4864:20::b2d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uCzCe-000kps-2b for pgsql-general@lists.postgresql.org; Thu, 08 May 2025 11:14:14 +0000 Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-e78effa4b34so594027276.0 for ; Thu, 08 May 2025 04:14:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1746702852; x=1747307652; darn=lists.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=lFpH+jMkw0j5+4E7VKWEWTS4msqQWGcWHVsTAfj8v5w=; b=TkOUlozQJ9KyTotSHrBq7p9gqQoBmBaUYj138oUpTD2+lfoTwcPAkis0UhXi3ehDVE AffT80cS0e6SdSPFniNhpSpQebJn4hUICPGfISBVTF4pSyDWH1c428HmNB4zNskWMKgX L0LV4k99qXhepOAnRR19PpfRLsMKwdU8WWWiYqPGGMVyWR3DitVwh9DwHDRVoPi+r1jd jG0vu7DhOsW7Wv1G4YiKesvG5q5PGHMx5AJatg2yUahybb+tNgeoPc5JTayKgfCRfyif 7Txri9AXd86vIJBfNI8vqoIKw8P0oCEkOdNuHeqM2RWSY4wksoC3HtE2NVZtb0MQx+S4 RzBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1746702852; x=1747307652; 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=lFpH+jMkw0j5+4E7VKWEWTS4msqQWGcWHVsTAfj8v5w=; b=DXq/qOUEUpxpnbDdydLIL+R1osVeysvkKoNdqlvEGcBee8C2qWIk6zPLrOnhCS5q1p iu3vw/FR6cNcNXiM+P6srxLBws8A9xlnXWqidLm+m5E+FHm+92xgnrX3g4TrvvORG+HB BQkNFMzOL36Jf9rvUkduxY1D6h4fpc9KsQ4HdC2mTu4+XfO4dm5wisp27Vzo4rbgcW+l roX6a8ni3uE6GpsdLNjyNOUR0w7mGvboOXkCqTq6wGiNfIBCY2YrAHAWXSUqgsIEigQ2 dvmcCx2EziZTlT4EVhBwbtDcSjARRumrZg4EWHWYz8Ny4EEI6NL6i9I20svSD7IZFaYV pzOQ== X-Gm-Message-State: AOJu0YxKCZUJR3s6ysiZLlqspwHDuI1s8gUXSL02vvd/trtbOYyexyc0 O73HfjGxHKJ5Hr9ykMRRG2GQtGTwm81aVjHnOirnCF6qSVFKqJcyewpN4v0H7MiL8Lc7/8iWkfi V92fStmTLtHjImUSX/IovPcWtXDw= X-Gm-Gg: ASbGnct4p/6Nf0fanC8rQOmAUXDSjkG2OPsgC2R9rLSBEGjDL5jC7GHUs6nXmXsXOid zoC1LHdaBWp3ZFtjFsL/21w/VeVrZGZqj0kJ2jYUjoHAiGp+i0m/il7W2WIaUXABhEUiCyMDsYP PbdWT9W9mE36PxNUuCD9JzlIk= X-Google-Smtp-Source: AGHT+IFQB355XuKJMzMluVAXRvbemgpx9zEsRDcEtQn70zFu4Dd+KwFH3APUM/60S31skqCCX1oHQlL/jCu7Qg5wiV4= X-Received: by 2002:a25:d010:0:b0:e78:e9be:2069 with SMTP id 3f1490d57ef6-e78ee0e22a9mr3055704276.20.1746702852182; Thu, 08 May 2025 04:14:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: KK CHN Date: Thu, 8 May 2025 16:46:13 +0530 X-Gm-Features: ATxdqUEUFCOsX-V33_26vvI7e5zmFlnx2YBvADPx9Rq0gq4EFiPHjvhSjd7EC4U Message-ID: Subject: Re: Pgbackrest failure for INCR and DIFF but not FULL backup To: Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000000872c706349df306" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000872c706349df306 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, May 7, 2025 at 6:46=E2=80=AFPM Greg Sabino Mullane wrote: > On Wed, May 7, 2025 at 7:15=E2=80=AFAM KK CHN wrote: > >> *archive_command =3D 'pgbackrest --stanza=3DMy_Repo archive-push %p && c= p %p >> /data/archive/%f' * >> > > Don't do this. You are archiving twice, and worse, the first part is usin= g > async archiving. Remove that whole "cp" part. Once that is fixed, run: > I'm going to see if putting *archive_command =3D 'pgbackrest --stanza=3DMy_Repo archive-push %p' *fix the problem. This was haunting = me for more than a week. Thanks for the suggestion. > pgbackrest --stanza=3DMy_Repo check > > to verify that WAL is being archived quickly and properly. Then test your > backups, checking the file > /var/log/pgbackrest/My_Repo-archive-push-async.log and your postgres log = if > any problems arise. > > Thanks . Krishane Cheers, > Greg > > -- > Crunchy Data - https://www.crunchydata.com > Enterprise Postgres Software Products & Tech Support > > --0000000000000872c706349df306 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, May 7, = 2025 at 6:46=E2=80=AFPM Greg Sabino Mullane <htamfids@gmail.com> wrote:
On Wed, May = 7, 2025 at 7:15=E2=80=AFAM KK CHN <kkchn.in@gmail.com> wrote:
archive_command =3D 'pgbackrest --stanza=3DMy_Repo archive-pu= sh %p && cp %p /data/archive/%f'=C2=A0

Don't do this. You are archiving twice, and wor= se, the first part is using async archiving. Remove that whole "cp&quo= t; part. Once that is fixed, run:

I'm going to see if putting=C2=A0 =C2=A0archive_command =3D '= ;pgbackrest --stanza=3DMy_Repo archive-push %p'=C2=A0 =C2=A0fix the= problem.=C2=A0 This was haunting me for more than a week.

Thanks for the s= uggestion.=C2=A0


pgbackrest --stanza=3DMy_Repo check

to verify tha= t WAL is being archived quickly and properly. Then test your backups, check= ing the file /var/log/pgbackrest/My_Repo-archive-push-async.log and your po= stgres log if any problems arise.

Thanks .=C2=A0=C2=A0
Krishane

<= br>
Cheers,
Greg

--
Enterprise Pos= tgres Software Products & Tech Support

=
--0000000000000872c706349df306--