On Tue, Mar 3, 2026 at 9:19 AM loganathan P <[email protected]> wrote:
> Dear Team,
>
> We have PostgreSQL 15 and PostgreSQL 17 databases running in separate
> environments on different servers. Each database is approximately 1.5 TB in
> size and highly active, generating around 500 GB of archive logs per day.
>
How many days (or weeks) of PITR backups do you need to retain.
> We have VM SRM replication configured.
>
That's probably not wise, given the size and volume. Physical replication
via pg_basebackup is quite easy to set up.
This is the command I use:
pg_basebackup \
--pgdata=$PGDATA \
--dbname=service=basebackup \
--verbose --progress \
--checkpoint=fast \
--write-recovery-conf \
--wal-method=stream \
--create-slot --slot=$SlotName \
--compress=server-lz4
> The archive log partition reaches 95–100% utilization before backups are
> taken. After the backups are completed, we must manually remove the
> archived log files to free up space.
>
> Could you please advise whether PostgreSQL has any built-in parameters or
> mechanisms to automatically delete archived log files
>
Lauren Albe is right: pgbackrest is probably the tool for you. Besides
doing regular database backups, it manages WAL archives, encryption,
compression and can be configured to automatically purge the oldest saveset
(a full backup and its associated incremental backups plus archived WAL
files) after a certain number of days.
For example, I've got multiple 3-4TB databases and use pgbackrest to retain
28-35 days of PITR backups. After the full backup on that 35th day,
pgbackrest automatically "expires" the oldest saveset and then we're back
down to 28 days of PITR backups.
It really is a wonderful do-everything tool.
> once they have been successfully backed up?
>
Where do you back them up to?
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
