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

From Scott Ribe
Subject Re: pgBackRest configuration with DDBoost
Date
Msg-id 96F639B3-D9FC-49D2-9FAC-5799010C314E@elevated-dev.com
Whole thread Raw
In response to Re: pgBackRest configuration with DDBoost  (Ron Johnson <ronljohnsonjr@gmail.com>)
Responses Re: pgBackRest configuration with DDBoost
Re: pgBackRest configuration with DDBoost
List pgsql-admin
> 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
oldRHEL6 system, so nothing better) and 24 threads.  Size 3.3T after compression, which is surprising based on how much
already-compressedbytea 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
8processes, 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: Ron Johnson
Date:
Subject: Re: pgBackRest configuration with DDBoost
Next
From: Ron Johnson
Date:
Subject: Re: pgBackRest configuration with DDBoost