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 1v14GJ-004Edm-UJ for pgsql-admin@arkaria.postgresql.org; Tue, 23 Sep 2025 14:44:59 +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 1v14GI-006HkI-Jb for pgsql-admin@arkaria.postgresql.org; Tue, 23 Sep 2025 14:44:58 +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 1v14GI-006Hk9-7w for pgsql-admin@lists.postgresql.org; Tue, 23 Sep 2025 14:44:58 +0000 Received: from mail-lf1-x136.google.com ([2a00:1450:4864:20::136]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v14GF-001xNg-0l for pgsql-admin@postgresql.org; Tue, 23 Sep 2025 14:44:57 +0000 Received: by mail-lf1-x136.google.com with SMTP id 2adb3069b0e04-57db15eeb11so3003851e87.2 for ; Tue, 23 Sep 2025 07:44:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1758638694; x=1759243494; 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=rg7PeL60PcYwocl0jVbOtjrANahm7+qL8t8euuKyyko=; b=gbyQmgFegnrRPUjdP9g1QaCaTm7bKUq5DhoJ4rBXwu+5aZ5Rln7S2uA2rHjHv81k1R E3ufljCKhiazTlKJlNOMiyf3rGcjxK8+Jm3OA8B3GAIk+4N8qGjNyqRKP1pwe7jp90cl hrvML5ZzCVy7X29sYg9kcTfZG3r969OcDfk7+iFzaRtuASr4bbtPSudUsm6NbL0p4tPG O6Wscs3DdsBRkiCcVOoBW+ZueZFwaAYU9gWZJuSOa4ZsotE+NxrnwkK2VFiXnkH2aNn7 rNskRDz1xYxATpO2V/d0qkiI/LpURIESPc/Ca40/5GI5/7Y5UhBTeJ9R/LGsv+pO32zR aIQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758638694; x=1759243494; 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=rg7PeL60PcYwocl0jVbOtjrANahm7+qL8t8euuKyyko=; b=e5RpfFA7rhzOUg1XtgD4qarDFEx6/KgHOTf2ULifgPEfdGYVzAFRlf8w2gZ6c9Xu8Y TCJfLROceCBw+7/xTXZtd0Kfh11jv+5avIWKrASBEixMeoySuEzHua6liU9zWM10/r0k QWcEMwUZAHaohYYipR5o9EtU7ag0lFq41d2bePrMtMRrdflpgk8Yw/hQTQ24Qh6h4LOH MvGUu/nihs5gz2xWIUovm/+NJ/tQqSjmEMFWni1E91PrUAqGotyI9f/FFYKmBDWN5JcG Fx0gX0duxneh5USQnO5AjdOBbyEdQGKCSF5vEacxxqTsCdK3TMHFZuMGQ1LK15ObnCMa wumg== X-Gm-Message-State: AOJu0YwMk2zGSGtSO1+BWKkSJ6U3/St/KD405dEplAtQZWZ5hjPI8Qgd y9SKoMvDMApuQmL5a8X/O7oZGFuneMr9SxN6azKe9+OFZTJyffGfYtDJdCrpEnEbmzy2Mtp5m7W 1H6g1QklnN8IcHjZHpfJEkxcoBQ8emOI= X-Gm-Gg: ASbGncvplgtI+SvJk2Xd7K0Nxe3UeGcUCMlrnADTV9RVBNCGLbUIhH7zrVXgTKAs4dX NJAmMlTUpmPVMnoRoENNhMFiYQbu6keg7UBpGb80kLxYLJqXRukYFi15LgTR6Jr6vRBYjmwrK2h 9eALUuHBXIqhAO1FjIY0zF6So/Ew2IHeFZwj53CV68cGxlJhQ/fQ2b1KyZFTSa8TdRAFnQ4+LPc 5KZIkuc X-Google-Smtp-Source: AGHT+IFMfJiBFQ0UKz0XcXpVzSHKRfbiZae9ctsH/oBkBRft6hIO3CM/AYj9UqMglkdAAg3DMbREk9q/HsLF1D5B3mY= X-Received: by 2002:a05:6512:6414:b0:560:885b:2c86 with SMTP id 2adb3069b0e04-580731fa8damr811865e87.37.1758638693587; Tue, 23 Sep 2025 07:44:53 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tim Gerber Date: Tue, 23 Sep 2025 09:44:42 -0500 X-Gm-Features: AS18NWBnbHKgERFzCCyTqmCaK_aHumLTAybQdGNdIqITBw6Bwyb0pYDFb7-6fFc Message-ID: Subject: Re: pgbackrest wiht arcchive mode off /no PITR configuration To: "Ghiurea, Isabella" Cc: PGSQL ADMIN Content-Type: multipart/alternative; boundary="0000000000009e9f33063f78fa88" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009e9f33063f78fa88 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If you aren't going to have archive_mode on, why not just use pg_basebackup? Not backing up archivelogs kind of defeats the purpose of using pgbackrest in my opinion. Best Regards, Tim On Tue, Sep 23, 2025 at 9:34=E2=80=AFAM Ghiurea, Isabella < Isabella.Ghiurea@nrc-cnrc.gc.ca> wrote: > Hi List. > I have a requirement to use pgabackrest to run ONLY full backups with no > need need for PITR in PG cluster 17.5 > > I tried several configuration options seems that archive_mode can not be > set to "off" for pgbackrest to run, is this correct ? > > > I tried unsuccessfully : archive_mode =3D on with > archive_command =3D '/bin/true' > > Second unsuccessfully configuration : archive_mode =3Don with > archive_command=3D'cp %p /tmp/pgbackrest-archive/%f' > > > Can you suggest a working solution for my requirements ? > > --0000000000009e9f33063f78fa88 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If you aren't going to have archive_mode on, why not j= ust use=C2=A0pg_basebackup?=C2=A0 Not backing up archivelogs=C2=A0kind of d= efeats the purpose of using pgbackrest in my opinion.=C2=A0

<= div>Best Regards,
Tim

On Tue, Sep 23, = 2025 at 9:34=E2=80=AFAM Ghiurea, Isabella <Isabella.Ghiurea@nrc-cnrc.gc.ca> wrote:

Hi List.
I have a requirement to use pgabackrest to run ONLY full backups with no ne= ed need for PITR in PG cluster 17.5

I tried several configuration options seems that archive_mo= de can not be set to "off" for pgbackrest to run,=C2=A0 is this c= orrect ?


I tried unsuccessfully : archive_mode =3D on with
archive_command =3D '/bin/true'

Second unsuccessfully configuration : archive_mode =3Don wi= th
archive_command=3D'cp %p /tmp/pgbackrest-archive/%f'


Can you suggest a working solution for my requirements ?


--0000000000009e9f33063f78fa88--