Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nIDf6-0001Fa-2s for pgsql-admin@arkaria.postgresql.org; Thu, 10 Feb 2022 17:55:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nIDf5-000126-2k for pgsql-admin@arkaria.postgresql.org; Thu, 10 Feb 2022 17:55:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nIDf4-00011Q-OH for pgsql-admin@lists.postgresql.org; Thu, 10 Feb 2022 17:55:18 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nIDf2-0004o9-H1 for pgsql-admin@lists.postgresql.org; Thu, 10 Feb 2022 17:55:17 +0000 Received: by mail-oi1-x22d.google.com with SMTP id r27so6770446oiw.4 for ; Thu, 10 Feb 2022 09:55:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=tvQM5Gfxmp1Y9Wh1FeAdBomuMNFeqDTBdWKV1VSAelU=; b=WNdatd6Zjx/u4JCSE0QwBBY988tSjn81G/PGdT1rLjhUPiNqUuwAO/70c7hcKpW/ci Gre4si2NZ2PzI4rKj//imRSnRNYVEe3uGvufD4DZM5ldvtZ9zX/yml4H5yDsQX67DGFS 9FIMgALCeZg4tQbnd82lIvIaGUAZh9K3bKFB5+rXJMHdCs0BmufrtEt3ElRKQTc/Fi4c UlyE4pdW9+83z+glRwac1OK8wO+gH0SdrhbDrCpC31SDj5p264zqAC6tM2T2VDBg2YqD N2yLkWv+1/rG9O/HSlbmZC5i6dF+PZoUPqhKGnD2rzhbwc5MbogmzmGP7T0iwRhjMNTT Ilxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=tvQM5Gfxmp1Y9Wh1FeAdBomuMNFeqDTBdWKV1VSAelU=; b=kXRtJnzRGQyaedOxa3/OueNh5+gKj29hC/JybcYAL7mXF7VG78Sh8d/WBYBz4TVuwo NwiikdVCF7lIW2+ci9/ogH+qOhgvPd4iBpNRVFV3bB/xv1cG15ROoTbehQm9FLYkxXgo HPdf9b8QpbTWwVF/I8yTxRvfC6J7x6FHgTW5ZQjq9Wkv4kLETnl89R0ikUcsqUslgtDl wQNVXycD0aH67VfVUs1fLx26yVABgW0CBcmA5q52sg/K8BvWm65FzpE2drjMxnaZBG+R IH3BPwafc4eCUhrIju3e9r4i3sLQxU1AFSd1mUw+gfVjVn7HUSpTGm2UE4ASMdtEuZBe sFpQ== X-Gm-Message-State: AOAM531+UXFkvZEIGNvKrBWdeNvnObEPOmXgEQcuJARwUru+bLe9GbgI jJ4eOxvWiUCLmeVRxgbYIemkHXlgTjY= X-Google-Smtp-Source: ABdhPJwfh09A5lTepWdaupVq507oNrumt5bn421Jg0x1z9kZIwJTN/jAw3aYCBdI5GYN1AJ+tHh+bw== X-Received: by 2002:a54:4583:: with SMTP id z3mr1594995oib.103.1644515715649; Thu, 10 Feb 2022 09:55:15 -0800 (PST) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id b3sm2504532oae.12.2022.02.10.09.55.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Feb 2022 09:55:15 -0800 (PST) Subject: Re: PG_Base Backup take 8 to 9Hrs To: pgsql-admin@lists.postgresql.org References: <91f9d08c-fb4b-5847-4663-e96994c1f460@gmail.com> <627d342b-6054-bb08-86d0-15c0a8e58887@sqlexec.com> From: Ron Message-ID: Date: Thu, 10 Feb 2022 11:55:13 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------4F0A1739DAD6EFFEE755B8DD" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------4F0A1739DAD6EFFEE755B8DD Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Please don't hijack threads. On 2/10/22 11:08 AM, Avihai Shoham wrote: > 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 > 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. > > > -- Angular momentum makes the world go 'round. --------------4F0A1739DAD6EFFEE755B8DD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Please don't hijack threads.

On 2/10/22 11:08 AM, Avihai Shoham wrote:
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@sqlexec.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.




--
Angular momentum makes the world go 'round.
--------------4F0A1739DAD6EFFEE755B8DD--