public inbox for [email protected]
help / color / mirror / Atom feedPostgres DB backup is taking too much time
6+ messages / 5 participants
[nested] [flat]
* Postgres DB backup is taking too much time
@ 2026-05-03 09:42 masheed ullah <[email protected]>
0 siblings, 3 replies; 6+ messages in thread
From: masheed ullah @ 2026-05-03 09:42 UTC (permalink / raw)
To: [email protected]
Hi,
We have a database of 20TB, and it's taking almost 24 hours to complete.
While full restore takes 28 hours. Although we have HA enabled with primary
and multiple replica's.
*So we need a solution/tool to reduce the RTO, incase of disk failure/
Human error for data/tables deletion.*
We are using Barman for backup.
My question is "Are there any tools like ZDLRA appliances for Oracle" to
reduce the RTO to less than 10 hours".
Best Regards,
Khattak
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgres DB backup is taking too much time
@ 2026-05-03 17:16 manish yadav <[email protected]>
parent: masheed ullah <[email protected]>
2 siblings, 0 replies; 6+ messages in thread
From: manish yadav @ 2026-05-03 17:16 UTC (permalink / raw)
To: [email protected] <[email protected]>; masheed ullah <[email protected]>
You may try barman with rsync option and adding parallelism i.e. parallel_jobs =6 (based on the CPU core available on the barman machine)
Thanks and Regards,
Manish Yadav
On Sunday 3 May, 2026 at 03:12:45 PM IST, masheed ullah <[email protected]> wrote:
Hi,
We have a database of 20TB, and it's taking almost 24 hours to complete. While full restore takes 28 hours. Although we have HA enabled with primary and multiple replica's.
So we need a solution/tool to reduce the RTO, incase of disk failure/ Human error for data/tables deletion.
We are using Barman for backup.
My question is "Are there any tools like ZDLRA appliances for Oracle" to reduce the RTO to less than 10 hours".
Best Regards,
Khattak
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgres DB backup is taking too much time
@ 2026-05-04 00:20 Greg Sabino Mullane <[email protected]>
parent: masheed ullah <[email protected]>
2 siblings, 0 replies; 6+ messages in thread
From: Greg Sabino Mullane @ 2026-05-04 00:20 UTC (permalink / raw)
To: masheed ullah <[email protected]>; +Cc: [email protected]
(This is more suitable for the pgsql-general list, you may get more/better
replies there)
There is nothing equivalent to ZDLRA in the Postgres world, but there are
certainly ways to reduce RTO. You are using replicas, and a tool that saves
WALs, so that really gets you 99% of the way there. Tools like pgBackrest
can do incremental backups, and parallel, delta-only restores, which can
wildly reduce both backup and restore times. RTO for Postgres can be
measured in seconds (e.g. Patroni handling a disk failure) to minutes (e.g.
someone dropped a table). Also see the recovery_min_apply_delay parameter.
If you give us a more specific use case / disaster scenario, we can give
more options and advice.
Cheers,
Greg
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgres DB backup is taking too much time
@ 2026-05-04 09:29 Ilya Anfimov <[email protected]>
parent: masheed ullah <[email protected]>
2 siblings, 1 reply; 6+ messages in thread
From: Ilya Anfimov @ 2026-05-04 09:29 UTC (permalink / raw)
To: [email protected]
On Sun, May 03, 2026 at 12:42:21PM +0300, masheed ullah wrote:
> Hi,
> We have a database of 20TB, and it's taking almost 24 hours to complete.
> While full restore takes 28 hours. Although we have HA enabled with
> primary and multiple replica's.
> So we need a solution/tool to reduce the RTO, incase of disk failure/
> Human error for data/tables deletion.
>
> We are using Barman for backup.
First, you'd need engineers to measure -- what's going on.
Who is the slowest part? The network (most probable)? The post-
gres replication process? The disk that postgres reads? The bar-
man itself? Receiver disks/S3 daemon/etc? TLS of one of the
above?
Measures is the key. Then the solutions may be searched.
btw, a modern postgres can definitely supply 1GB/s to barman on a
modern system. This is not a much, and probably could be im-
proved by special tricks like rsync or manual prefetch or incre-
mental copies -- however, it's less than 6 hours estimate and
therefore is fine for you.
> My question is "Are there any tools like ZDLRA appliances for Oracle" to
> reduce the RTO to less than 10 hours".
> Best Regards,
> Khattak
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgres DB backup is taking too much time
@ 2026-05-04 09:58 masheed ullah <[email protected]>
parent: Ilya Anfimov <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: masheed ullah @ 2026-05-04 09:58 UTC (permalink / raw)
To: Ilya Anfimov <[email protected]>; [email protected]
Thank you every one for your output.
Although pgBeckRest has no more support.
Should I suggest starting testing backup and restore with pgBectRest?
I did not find any 3rd Party tool.
On Mon, May 4, 2026 at 12:29 PM Ilya Anfimov <[email protected]> wrote:
> On Sun, May 03, 2026 at 12:42:21PM +0300, masheed ullah wrote:
> > Hi,
> > We have a database of 20TB, and it's taking almost 24 hours to
> complete.
> > While full restore takes 28 hours. Although we have HA enabled with
> > primary and multiple replica's.
> > So we need a solution/tool to reduce the RTO, incase of disk failure/
> > Human error for data/tables deletion.
> >
> > We are using Barman for backup.
>
> First, you'd need engineers to measure -- what's going on.
> Who is the slowest part? The network (most probable)? The post-
> gres replication process? The disk that postgres reads? The bar-
> man itself? Receiver disks/S3 daemon/etc? TLS of one of the
> above?
> Measures is the key. Then the solutions may be searched.
>
> btw, a modern postgres can definitely supply 1GB/s to barman on a
> modern system. This is not a much, and probably could be im-
> proved by special tricks like rsync or manual prefetch or incre-
> mental copies -- however, it's less than 6 hours estimate and
> therefore is fine for you.
>
> > My question is "Are there any tools like ZDLRA appliances for Oracle"
> to
> > reduce the RTO to less than 10 hours".
> > Best Regards,
> > Khattak
>
>
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgres DB backup is taking too much time
@ 2026-05-04 10:10 Gerald Drouillard <[email protected]>
parent: masheed ullah <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Gerald Drouillard @ 2026-05-04 10:10 UTC (permalink / raw)
To: masheed ullah <[email protected]>; +Cc: Ilya Anfimov <[email protected]>; [email protected]
You could setup a replication to another PG server that is setup on a COW
file system like zfs.
Then you can take snapshots on the replica.
On Mon, May 4, 2026 at 5:59 AM masheed ullah <[email protected]> wrote:
> Thank you every one for your output.
>
> Although pgBeckRest has no more support.
> Should I suggest starting testing backup and restore with pgBectRest?
> I did not find any 3rd Party tool.
>
> On Mon, May 4, 2026 at 12:29 PM Ilya Anfimov <[email protected]> wrote:
>
>> On Sun, May 03, 2026 at 12:42:21PM +0300, masheed ullah wrote:
>> > Hi,
>> > We have a database of 20TB, and it's taking almost 24 hours to
>> complete.
>> > While full restore takes 28 hours. Although we have HA enabled with
>> > primary and multiple replica's.
>> > So we need a solution/tool to reduce the RTO, incase of disk failure/
>> > Human error for data/tables deletion.
>> >
>> > We are using Barman for backup.
>>
>> First, you'd need engineers to measure -- what's going on.
>> Who is the slowest part? The network (most probable)? The post-
>> gres replication process? The disk that postgres reads? The bar-
>> man itself? Receiver disks/S3 daemon/etc? TLS of one of the
>> above?
>> Measures is the key. Then the solutions may be searched.
>>
>> btw, a modern postgres can definitely supply 1GB/s to barman on a
>> modern system. This is not a much, and probably could be im-
>> proved by special tricks like rsync or manual prefetch or incre-
>> mental copies -- however, it's less than 6 hours estimate and
>> therefore is fine for you.
>>
>> > My question is "Are there any tools like ZDLRA appliances for
>> Oracle" to
>> > reduce the RTO to less than 10 hours".
>> > Best Regards,
>> > Khattak
>>
>>
>>
>
>
>
>
Attachments:
[application/x-shellscript] pg-zfs-snapshot.sh (14.8K, 3-pg-zfs-snapshot.sh)
download
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2026-05-04 10:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-05-03 09:42 Postgres DB backup is taking too much time masheed ullah <[email protected]>
2026-05-03 17:16 ` manish yadav <[email protected]>
2026-05-04 00:20 ` Greg Sabino Mullane <[email protected]>
2026-05-04 09:29 ` Ilya Anfimov <[email protected]>
2026-05-04 09:58 ` masheed ullah <[email protected]>
2026-05-04 10:10 ` Gerald Drouillard <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox