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 1nICZb-0004AA-Aa for pgsql-admin@arkaria.postgresql.org; Thu, 10 Feb 2022 16:45:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nICZY-0007zI-CG for pgsql-admin@arkaria.postgresql.org; Thu, 10 Feb 2022 16:45:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nICZX-0007z9-VJ for pgsql-admin@lists.postgresql.org; Thu, 10 Feb 2022 16:45:32 +0000 Received: from mail-qk1-x736.google.com ([2607:f8b0:4864:20::736]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nICZV-0005Jd-1A for pgsql-admin@lists.postgresql.org; Thu, 10 Feb 2022 16:45:31 +0000 Received: by mail-qk1-x736.google.com with SMTP id o10so5468027qkg.0 for ; Thu, 10 Feb 2022 08:45:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to; bh=roDgFeClH1krcsBT8cNMsBUI5+3wJXCk1KAgl9kUzR8=; b=lnmX3OacONvgxavmej8EJ2YuGYveZ2uth7VUNE2LF017ZSRsHNnCv2prtpH/wsQ7n7 jkyCbx9Yf/gjnTM1E/7548bU3Whhzy48QhktXhC/HO2nbTjbnaC6hFHFZmo5ZrnSusG7 ABPQEiP7O5yp9J3ol+1aGQQZR/0i0Hpfrx0MU/6Shz+3ybcauUPyZ+XnV9kYrvU6NKV2 oAMNOY137nFbwrv5zni/prte0o25YN/twrRrYdadi+KTRM+NtvuHmq5POLCR/AGOvz4a +vxeCgjpGwYuaY6fguV1wGGj6aog3VOMoLkuuBrjaiq6cbOIjcCrUfa1x1Ugt8b6WRa1 q4mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to; bh=roDgFeClH1krcsBT8cNMsBUI5+3wJXCk1KAgl9kUzR8=; b=hFCxPIEZEb3BAudJlMGeILuwX1Blx9DCOTEFAfTlia0nznD1H5sIv8sep3P8me+HK/ tK3LTuz8hi2mY0g8i+6CTfQ1PieotWPiMZumRrn3x1/JdGC/FBHmq0VzJDcPTgyiQy5f mrxVTtd1Tii6ZRDQcJiAOaN76l4oXZm/lBCQ0cX8aTsczevrwTf9Tu+pywznWcD+9JSK 8exap4kLC4NsyXN5JkjZ15DqEhgxcaKUYTUYV/bKwJtIgKvKOOWmcX/rbKDhQQs6NPiT wfopJ5RJHc6G1KeSFrsLp1gMyWI5OYm3lRWCpUB3TZ9Egtf4/k7gMdT+J9NGDqO6s5DJ rLVw== X-Gm-Message-State: AOAM533Fu7EQKdeIQh6ZDUx/cbhxFq2rhb123PMl5fo3+ca23zeXGCDT kvd0JXmuIy3+cpL0fJzAZLie7Lphp7UUiw== X-Google-Smtp-Source: ABdhPJxzYr5hPJBu7D8Ie9xNe+7i3LMI9mlH1kG/X9XeXqddQ0MuEmVvk+q719Jq4zUo3UYN2nIBsg== X-Received: by 2002:a05:620a:4115:: with SMTP id j21mr4266143qko.680.1644511527134; Thu, 10 Feb 2022 08:45:27 -0800 (PST) Received: from [192.168.2.100] (pool-72-79-19-93.nwrknj.east.verizon.net. [72.79.19.93]) by smtp.gmail.com with ESMTPSA id k9sm9998076qkj.31.2022.02.10.08.45.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Feb 2022 08:45:26 -0800 (PST) Content-Type: multipart/alternative; boundary="------------HE8rj37MDpJyg7qzGK1ZdiBj" Message-ID: <1b297f2c-aef1-084c-b10a-f36154fdd636@gmail.com> Date: Thu, 10 Feb 2022 11:45:25 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: PG_Base Backup take 8 to 9Hrs Content-Language: en-US To: MichaelDBA Cc: pgsql-admin@lists.postgresql.org References: <91f9d08c-fb4b-5847-4663-e96994c1f460@gmail.com> <627d342b-6054-bb08-86d0-15c0a8e58887@sqlexec.com> From: Mladen Gogala In-Reply-To: <627d342b-6054-bb08-86d0-15c0a8e58887@sqlexec.com> 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. --------------HE8rj37MDpJyg7qzGK1ZdiBj Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Please don't top-post. On 2/10/22 09:31, MichaelDBA 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-1217 >> https://dbwhisperer.wordpress.com > I can wholeheartedly recommend Commvault backup suite. It can seamlessly utilize storage snapshot and has built in parallelism, deduplication and compression. Regards -- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com --------------HE8rj37MDpJyg7qzGK1ZdiBj Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Please don't top-post.

On 2/10/22 09:31, MichaelDBA 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-1217
https://dbwhisperer.wordpress.com

I can wholeheartedly recommend Commvault backup suite. It can seamlessly utilize storage snapshot and has built in parallelism, deduplication and compression.

Regards

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
--------------HE8rj37MDpJyg7qzGK1ZdiBj--