AW: PG_Base Backup take 8 to 9Hrs

Von: Avihai Shoham <avihai(dot)shoham(at)gmail(dot)com>
Gesendet: Donnerstag, 10. Februar 2022 18:08
An: MichaelDBA <MichaelDBA(at)sqlexec(dot)com>
Cc: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>; Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com>; pgsql-admin(at)lists(dot)postgresql(dot)org
Betreff: Re: PG_Base Backup take 8 to 9Hrs

Hi All ,

lately i'm getting this error when open base.tar.
Any idea why pg_basebackup created bad tar file? and how to fix it?

Thanks!
Avihai

tar xOf base.tar > /dev/null
tar: Unexpected EOF in archive
tar: rmtlseek not stopped at a record boundary
tar: Error is not recoverable: exiting now

On Thu, Feb 10, 2022 at 5:16 PM MichaelDBA <MichaelDBA(at)sqlexec(dot)com<mailto:MichaelDBA(at)sqlexec(dot)com>> wrote:
Just keep in mind that logical dumps and loads do not support Point In
Time Recovery (PITR).

Wells Oliver wrote on 2/10/2022 9:36 AM:
> 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.

Hi Avihai

try
--ignore-failed-read
and or
--ignore-zeros

best,

Anton