Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rzbla-005Gr8-M9 for pgsql-general@arkaria.postgresql.org; Wed, 24 Apr 2024 12:30:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rzblY-00Ena9-Jt for pgsql-general@arkaria.postgresql.org; Wed, 24 Apr 2024 12:30:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rzblY-00Ena0-5W for pgsql-general@lists.postgresql.org; Wed, 24 Apr 2024 12:30:24 +0000 Received: from mail-lf1-x135.google.com ([2a00:1450:4864:20::135]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rzblS-002hfv-TV for pgsql-general@postgresql.org; Wed, 24 Apr 2024 12:30:23 +0000 Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-51bab51e963so2204174e87.1 for ; Wed, 24 Apr 2024 05:30:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713961816; x=1714566616; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mmaxH7yDfdPrUnVraUxZc2PuSJDg0+q+ku8w8cKKYxs=; b=PyAOp8gm5clllJN6yh6kvVul40D5792aVRbLUa+zi9KwXkHF5p0F69TgpurR+s5LE2 UuHthVfuHukUgXVq4Gl2bRSlCv0Oc4dGIsKFLy8+AA0MRQWr/0E6DCExRwBdlTwpBbOG B6p8BEr77Pr9+xbd+P9mkurjNxO0eLmouJn8E/LLGNFdnt1e3h9izXK63kxDguGpdtyF ezWv9HPnI98W3PTXAOeG5C0TKqpLtVWF/eWiGWuLnqFWGhYJMq1tNGgB81XW/9jl8Wi3 7t8+HnLNWVhZMX3/vhJtlie8zcsL93KS5vEu/eMUE2CT+peO7xLsVCWC40B6q/COxaZh +eQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713961816; x=1714566616; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mmaxH7yDfdPrUnVraUxZc2PuSJDg0+q+ku8w8cKKYxs=; b=QLtXPvy8nPw+NvNwzOU2IBsc4kbvt7iVpca2ONGbn7V1LSLcxMxuZtFLMyMn024g7y dKjCo2f+duuqnfhin5UD+JVnKgBQWwevtldpitYczE02W0CXkLUZeWne5s53TmIRZTJh YUl9IBhCpBEMokpjFQgwWb9itxJeXXOG4f1IULmNLcKhZ2k8TyuQeq73KaCtUHaUpRcr oUEKWF7UFUrv93C2FWeP+eGfR7GzqNlIqNV31isAtjWmtsedXqG5ay7bsdDQ30BVFNDj FYOggdxodt+K45wDkDNyiDn+Y89eeszJlzW/IMPlTWGe6/l//BmP09UcL8LievcHbJgH 04Bw== X-Gm-Message-State: AOJu0Yz+SLVEA1mYKMExo+xv8Z/u3+nf2RPFtYAw9xchWQf1OefY3fHp aAu+n/7jWFEI0oSX+Z8N5HvdiOJ1CKjVRaUOfsJ99RnYT6gcM36NO6FevFuC6zYcy9SzQXmvC1f 7JvUSbenURa2qe2W0TPvceEvm9Nhi7LNh X-Google-Smtp-Source: AGHT+IErSYpVlUacJOgeCA1RUIMeyUKpL+L4SJjrS89P7lK07AWAtbwmxFruVJM0XGjeuuGTp9++7+zIck5CrCYseCI= X-Received: by 2002:a05:6512:2e3:b0:519:7585:9f66 with SMTP id m3-20020a05651202e300b0051975859f66mr1623405lfq.50.1713961816075; Wed, 24 Apr 2024 05:30:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: jaya kumar Date: Wed, 24 Apr 2024 18:00:03 +0530 Message-ID: Subject: Re: Backup_Long Running To: Vijaykumar Jain Cc: pgsql-general Content-Type: multipart/alternative; boundary="00000000000034b7dd0616d6d5f6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000034b7dd0616d6d5f6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for your update. Can you have any link or document to configure L0 & L1 backup using pgbackrest tool. Also share the pgbackrest installation method. On Wed, Apr 24, 2024 at 2:50=E2=80=AFPM Vijaykumar Jain < vijaykumarjain.github@gmail.com> wrote: > > On Wed, Apr 24, 2024, 12:33=E2=80=AFPM jaya kumar = wrote: > >> Hi Team, >> >> >> >> Production database Backup is running very long hours. Any option to >> reduce backup time? Kindly advise me. >> >> >> >> DB size: 793 GB >> >> >> >> We are taking pg_basebackup backup. >> >> > do you see network saturation, io saturation ? > generally faster hardware i.e striped and or nvme disks along with a > robust network link and capacity should help get the backup done quickly. > where are you taking the backup from? is the server busy doing other work > or it is a dedicated machine for backups ? > basically monitor for resource saturation, if all looks good, we could > take basebackup of a 10tb db in 8 hours, and in another case on a slow > remote storage, backup of 2tb took 1 day. > > now, pgbackrest can speedup backup processes by spawning more workers for > archiving and stuff. we have taken backup on nvme disks striped of 28tb i= n > 3 hours, bare metals servers with powerful cpu. > > so , it's hardware .... else switch to pgbackrest which can take > incremental/differential/full backups. > there are other tools too, I used only these two. > >> >> --=20 Thanks & Regards, Jayakumar.S +91-9840864439. --00000000000034b7dd0616d6d5f6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for your update. Can you have any link or document to configure L0 & L1 backup using pgbackrest<= /span> tool. Also share the pgbackrest installation method.=C2=A0 =C2=A0=C2=A0
=

= On Wed, Apr 24, 2024 at 2:50=E2=80=AFPM Vijaykumar Jain <vijaykumarjain.github@gmail.com>= wrote:

basically monitor for resource saturation, if all looks goo= d, we could take basebackup of a 10tb db in 8 hours, and in another case on= a slow remote storage, backup of 2tb took 1 day.
now, pgbackrest can speedup backup processes by s= pawning more workers for archiving and stuff. we have taken backup on nvme = disks striped of 28tb in 3 hours, bare metals servers with powerful cpu.

so , it's hardware ...= . else switch to pgbackrest which can take incremental/differential/full ba= ckups.
there are other tools too, I used only these = two.




--
Thanks & Regards,
Ja= yakumar.S
+91-9840864439.
--00000000000034b7dd0616d6d5f6--