| From: | Avihai Shoham <avihai(dot)shoham(at)gmail(dot)com> |
|---|---|
| To: | 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 |
| Subject: | Re: PG_Base Backup take 8 to 9Hrs |
| Date: | 2022-02-10 17:08:25 |
| Message-ID: | CA+=0ERebgxLJ5uwb05MT-E9Cri0GZz6citu9fq1HQtHPSryPxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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> 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.
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2022-02-10 17:55:13 | Re: PG_Base Backup take 8 to 9Hrs |
| Previous Message | Mladen Gogala | 2022-02-10 16:45:25 | Re: PG_Base Backup take 8 to 9Hrs |