Subject: Re: PG_Base Backup take 8 to 9Hrs
To: Mladen Gogala <gogala.mladen@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
References: 
 <KL1PR0601MB44331141771E87939CAB3B91F02D9@KL1PR0601MB4433.apcprd06.prod.outlook.com>
 <91f9d08c-fb4b-5847-4663-e96994c1f460@gmail.com>
From: MichaelDBA <MichaelDBA@sqlexec.com>
Message-ID: <627d342b-6054-bb08-86d0-15c0a8e58887@sqlexec.com>
Date: Thu, 10 Feb 2022 09:31:28 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 PostboxApp/7.0.54
MIME-Version: 1.0
In-Reply-To: <91f9d08c-fb4b-5847-4663-e96994c1f460@gmail.com>
Content-Type: multipart/alternative;
 boundary="------------CCB68B8F8A14D65151BF4B17"
Content-Language: en-US
Archived-At: 
 <https://www.postgresql.org/message-id/627d342b-6054-bb08-86d0-15c0a8e58887%40sqlexec.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------CCB68B8F8A14D65151BF4B17
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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-1217
> https://dbwhisperer.wordpress.com


--------------CCB68B8F8A14D65151BF4B17
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html theme="default-light" iconset="color"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body text="#000000">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.<br>
pgbackrest (full, differential, and incremental)<br>
barman (full and incremental)<br>
<br>
Regards,<br>
Michael Vitale<br>
<br>
<span>Mladen Gogala wrote on 2/9/2022 7:42 PM:</span><br>
<blockquote type="cite" 
cite="mid:91f9d08c-fb4b-5847-4663-e96994c1f460@gmail.com">
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

  
  <div class="moz-cite-prefix">On 2/8/22 06:36, Ram Pratap Maurya
      wrote:<br>
    </div>

    
  <blockquote type="cite" 
cite="mid:KL1PR0601MB44331141771E87939CAB3B91F02D9@KL1PR0601MB4433.apcprd06.prod.outlook.com"><p
 class="MsoPlainText"><span style="color:#1F497D">We are using
          Postgres -11 version and current
          <b>PG DB size is 450 GB</b> .<o:p></o:p></span></p>
      <p class="MsoPlainText"><span style="color:#1F497D">Archive log
          enable in Database and we are running Full
          <b>PG_Base backup</b> and it will take 8 to 9 Hrs to complete
          the backup ,<o:p></o:p></span></p>
      <p class="MsoPlainText"><span style="color:#1F497D">Please suggest
           how to reduce the full DB backup time.</span></p></blockquote>

    
  <p>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.<br>
    </p>

    
  <pre class="moz-signature" cols="72">-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
<a class="moz-txt-link-freetext" href="https://dbwhisperer.wordpress.com" moz-do-not-send="true">https://dbwhisperer.wordpress.com</a>
</pre>
</blockquote>
<br>
</body></html>

--------------CCB68B8F8A14D65151BF4B17--