Re: PG_Base Backup take 8 to 9Hrs

Can you just try good ole pg_dump with --format=directory and --jobs=X
where X is some decent number, e.g. 16? We just packed up a 700GB DB using
16 jobs and it took maybe 80 minutes.

On Thu, Feb 10, 2022 at 6:31 AM MichaelDBA <MichaelDBA(at)sqlexec(dot)com> wrote:

> Please use a third party backup solution that provides faster and more
> flexible backup alternatives than the built in, pg_basebackup(), which is
> not usefult for large databases.
> pgbackrest (full, differential, and incremental)
> barman (full and incremental)
>
> Regards,
> Michael Vitale
>
> Mladen Gogala wrote on 2/9/2022 7:42 PM:
>
> On 2/8/22 06:36, Ram Pratap Maurya wrote:
>
> We are using Postgres -11 version and current *PG DB size is 450 GB* .
>
> Archive log enable in Database and we are running Full *PG_Base backup*
> and it will take 8 to 9 Hrs to complete the backup ,
>
> Please suggest how to reduce the full DB backup time.
>
> Use storage snapshots, faster disks, faster Ethernet adapters and backup
> software that supports deduplication. You are asking the list to architect
> your backup solution. For that, some more information is needed: what kind
> of machine are you using, what OS, how much memory, what kind of storage is
> your cluster running on, what kind of storage are you backing it up to, how
> is the backup storage connected (FC/AL, Ethernet, local SATA drives), is
> there any degree of parallelism and things of that nature. In the absence
> of that information, I can only recommend attempting with the --run-faster
> switch to pg_basebackup. You may also try using the Force.
>
> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217https://dbwhisperer.wordpress.com
>
>
>

--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>