From: Scott Ribe <scott_ribe@elevated-dev.com>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: pgBackRest configuration with DDBoost
Date: Mon, 3 Jun 2024 21:21:56 -0600
References: <1353402555.1511878.1717467795288.ref@mail.yahoo.com>
 <1353402555.1511878.1717467795288@mail.yahoo.com>
 <CANzqJaAaCpDCV8Puw5w1803mbQtn=XHSy7VTYzSYeFTF5VLUNQ@mail.gmail.com>
To: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
In-Reply-To: 
 <CANzqJaAaCpDCV8Puw5w1803mbQtn=XHSy7VTYzSYeFTF5VLUNQ@mail.gmail.com>
Message-Id: <96F639B3-D9FC-49D2-9FAC-5799010C314E@elevated-dev.com>
Archived-At: 
 <https://www.postgresql.org/message-id/96F639B3-D9FC-49D2-9FAC-5799010C314E%40elevated-dev.com>
Precedence: bulk

> On Jun 3, 2024, at 9:06=E2=80=AFPM, Ron Johnson =
<ronljohnsonjr@gmail.com> wrote:
>=20
> Takes 2 hr 45 min for us to do a weekly full backup of the 6.1TB =
instance using integrated gzip compression (it's an old RHEL6 system, so =
nothing better) and 24 threads.  Size 3.3T after compression, which is =
surprising based on how much already-compressed bytea data there is.

FYI, Naveed, there's a tradeoff available in current versions of =
pgbackrest. It can be configured to use lz4 compression. For us, that =
means close to 50% larger backups than gzip, but many times faster. =
3.2TB in 30 minutes, using 8 processes, 725GB backup size--no already =
compressed bytea, but a good bit of incompressible UUID columns.

Good enough that I stopped doing daily incrementals, and just take full =
backups daily.=