From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgBackRest configuration with DDBoost |
Date: | 2024-06-04 04:09:45 |
Message-ID: | CANzqJaCUBdzLas3jvYgkGMTvVtpdKeJjnefShYQpxdwg-A_wNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Jun 3, 2024 at 11:22 PM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> > On Jun 3, 2024, at 9:06 PM, Ron Johnson <ronljohnsonjr(at)gmail(dot)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.
>
How big were the incrementals? (I'm thinking more weeks of backup set
retention when using full+incr.)
From | Date | Subject | |
---|---|---|---|
Next Message | Amitpal Singh | 2024-06-04 04:36:10 | Re: pgBackRest configuration with DDBoost |
Previous Message | Scott Ribe | 2024-06-04 03:21:56 | Re: pgBackRest configuration with DDBoost |