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 1nHxXz-0004iJ-Iu for pgsql-admin@arkaria.postgresql.org; Thu, 10 Feb 2022 00:42:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nHxXy-00073r-GZ for pgsql-admin@arkaria.postgresql.org; Thu, 10 Feb 2022 00:42:54 +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 1nHxXy-00073e-6J for pgsql-admin@lists.postgresql.org; Thu, 10 Feb 2022 00:42:54 +0000 Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nHxXv-00056Q-OI for pgsql-admin@lists.postgresql.org; Thu, 10 Feb 2022 00:42:53 +0000 Received: by mail-qt1-x835.google.com with SMTP id t1so3571097qtq.13 for ; Wed, 09 Feb 2022 16:42:51 -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 :references:from:in-reply-to; bh=cbOOD6qDTPvrap5nx6KuuKRq16q0NJ0u5AKXA3YjMU4=; b=XM3hP0bW398A3hv7b3HAuHlOjMtEM/yLiGOsAX9b0HEp5L+eoEycFbsgmvrOBtN2Kl /uchs5TwOsSLQkK6zBTDYPs7nYigl0FmnGxC9bqpAKRD8SnkWnqKSIBql+hsGKCxMLiQ YL8Y+RVs0ei/uhozjTEY232x0q18a1NG6Y+Ygmxzm7mVI37r7OGPiugos2eCYet04IXq H6d5VuSf4pVAUCcQUQxol29Z1ACJLQPIjMg7xJGw+nMHj6PxMEOQFoIIgI9MFshjPzeq ZUhrKzJUxYLk+XCSY/TxqUlcdMfA5jvuCEyS0L+gftSHE3HHLN5CMPT3gUAVJmglIhND r7+A== 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:references:from:in-reply-to; bh=cbOOD6qDTPvrap5nx6KuuKRq16q0NJ0u5AKXA3YjMU4=; b=l+4Ly3KuG9dMynDiVKmdg0t2oas9yBNSRXug2FAscXLMJS2KyddTTDBCED90gDu/z/ 9dUi/pDwJ2QwX8FDzwquhQi/eLbaTB4xcwXqkLrQuRMSey0jNYr+wk1E8UM24uprcey+ sWpq7OMg0rskmcDaGBqhnqg6tC/Wk5KM15ViSi2yoA+Ci4PJIQDn83kv7cB4Bvefp3MU IZXr99kattVStDC/R7g0zTJ0E3RgtJehACInzMhMU6nngSXAC8+Wi4ruHwFnrKah71b8 wSFz2pgF8w6mfPD282/p/cGr3zyCS3qcMsKpeP83iLsZsGso/JBDC/4gisyFG9WYWTF3 uQlA== X-Gm-Message-State: AOAM5316B6Ygjg/45KynJswBy0kxUEpKsUHosZdtPTN8Oq2KqOg+eR86 d7mtYTqXnrUm2y0AiV6e7OSUJq6Lqydd3w== X-Google-Smtp-Source: ABdhPJyAtm7eUFuRsfEcuSGDZQeDjZnKocXeFoVzy3EYqlJ+KukKL6a2quZCAhgOJ0oy4J5lBvf9Tg== X-Received: by 2002:a05:622a:1011:: with SMTP id d17mr3338037qte.377.1644453770148; Wed, 09 Feb 2022 16:42:50 -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 a186sm8774795qkf.102.2022.02.09.16.42.49 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 09 Feb 2022 16:42:49 -0800 (PST) Content-Type: multipart/alternative; boundary="------------BHnmEdrdYE0vPoa3nRWIF1uw" Message-ID: <91f9d08c-fb4b-5847-4663-e96994c1f460@gmail.com> Date: Wed, 9 Feb 2022 19:42:48 -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: pgsql-admin@lists.postgresql.org References: From: Mladen Gogala In-Reply-To: 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. --------------BHnmEdrdYE0vPoa3nRWIF1uw Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 --------------BHnmEdrdYE0vPoa3nRWIF1uw Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
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
--------------BHnmEdrdYE0vPoa3nRWIF1uw--