Re: pgBackRest configuration with DDBoost - Mailing list pgsql-admin

From Ron Johnson
Subject Re: pgBackRest configuration with DDBoost
Date
Msg-id CANzqJaDQ=Ow6vMGQPcThvP7bM2e5BzMRbNU7Rz1U4D1GO2Rhjg@mail.gmail.com
Whole thread Raw
In response to Re: pgBackRest configuration with DDBoost  (Naveed Iftikhar <naveed27c@yahoo.com>)
List pgsql-admin
On Tue, Jun 4, 2024 at 10:44 AM Naveed Iftikhar <naveed27c@yahoo.com> wrote:
Thanks Scott for your input, Our database is keep growing and application owner want to have incremental backups daily. Can you share how you have configured the lz4 compression with pgbackrest.

It's all in the Fine Manuals, of which a lot of effort was placed in writing.
 
  Any special storage requirements?

What do you mean (other than that lz4 is tuned for speed, rather than high compression)?  PGBR supports zstd and bz2, as well as lz4 and gzip.
 

On Monday, June 3, 2024 at 10:22:28 PM CDT, Scott Ribe <scott_ribe@elevated-dev.com> wrote:


> On Jun 3, 2024, at 9:06 PM, Ron Johnson <ronljohnsonjr@gmail.com> wrote:

>
> 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.


pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Minimize checkpointer and walwriter io during pg_restore
Next
From: Scott Ribe
Date:
Subject: Re: pgBackRest configuration with DDBoost