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 1sjhgi-0039ej-Id for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 16:07:56 +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 1sjhgg-004EgJ-I3 for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 16:07:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjhgg-004EgB-6P for pgsql-general@lists.postgresql.org; Thu, 29 Aug 2024 16:07:54 +0000 Received: from mail-yw1-x1130.google.com ([2607:f8b0:4864:20::1130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sjhge-0022N5-6U for pgsql-general@postgresql.org; Thu, 29 Aug 2024 16:07:53 +0000 Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-691bb56eb65so8159347b3.0 for ; Thu, 29 Aug 2024 09:07:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724947671; x=1725552471; 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=CLXGhOwutzbGgJ0seCd254Bzb++w6biVOyBEEozTmm0=; b=iCbaoyQ+Ii0ek6UrEI8vpyhPHBzfmBbkQy4zt3CSVzhsv1o2K3H25RIVY2O9LMfxPi 87R2t63v3wx+FScu3aMNRrV0n+w1TNmvrb12Kt15EtnAnMe0EXYWj4+427kT9e0X0q9h cBLtBVWgK4y6yrlry0jdlmo+q7MdHPSJ8GSA18zjuB4VaT7MTU1QVydDkovWOg2lY8fZ Eu5Cg5nHoWv6+3V0jpkfHkpZNMsddYKkOmgJQ1lgBT6G9WokW9r5vUrlemJ8PaYURl4C H3wrHwPw1yYJaEvy0WIqiKQh1PB92ObjJqyf8F3fgA4N8VZRpF9XFT+KTGhw/0QU18Xf fXdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724947671; x=1725552471; 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=CLXGhOwutzbGgJ0seCd254Bzb++w6biVOyBEEozTmm0=; b=ll1MI7rm18pk+6IEgwbXUIrqcYAJutBJ9GaQFfP2csKRVCfZ/TpmP2c8/Zj/cvmyVQ 9FE2pgctcmVUx/1GiYHyssH23gRzwkjiUN4zq9bC5dPbyULAZ4F0duVzkovzt30BKCUS dCKg3O/Xi4en1wVPvnmJ/lPUqTo5SKw+qlB+g31jyiDxud2VPvx11If6xn54I9m/YkTr nqpZuZxzqE5L6o1kFCqGI90UY12IiIp9H7CdLbWspA0hLNl99tcFua9hj0NwEPlQn+yE HYZuGY5SpQGosd4X14y1QPFYULq29KGenJ8HNxl2dCjHVCQFqjP6O9MInU7VyZXukHlL j6kA== X-Gm-Message-State: AOJu0YzlHXJyTxF6Ilnn0T627goIStTYv6N1KeSupMSTa5uSp0vvYy7D 3J/iAXYZ2CY6OsHh2nMtN+Aq8zYRxqLHVx2xmSAnTGDL0txXWnnjDpYSJcW+XboO9FzPEM9IiKt nnKOEWyJh5H8NxR/gNW0wkubRjJM= X-Google-Smtp-Source: AGHT+IG7Kkd+iV+4MvvI9d+h30JYbtYWox5qgKq3iUouWqrsF6VkyBV2DcGNvsLUwWX763l5YTU4LxHt3K7aepjQomc= X-Received: by 2002:a05:690c:f8a:b0:6be:28ab:d87f with SMTP id 00721157ae682-6d275d3e34emr43295987b3.2.1724947671124; Thu, 29 Aug 2024 09:07:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: KK CHN Date: Thu, 29 Aug 2024 21:37:39 +0530 Message-ID: Subject: Re: PgBackRest Full backup and N/W reliability To: Greg Sabino Mullane Cc: pgsql-general Content-Type: multipart/alternative; boundary="0000000000003197300620d4ad65" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003197300620d4ad65 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 29, 2024 at 6:54=E2=80=AFPM Greg Sabino Mullane wrote: > On Thu, Aug 29, 2024 at 2:21=E2=80=AFAM KK CHN wrote= : > >> I am doing a full backup using PgBackRest from a production server to >> Reposerver. >> > ... > >> If so, does the backup process start again from scratch ? or it >> resumes from where the backup process is stopped ? >> > > It resumes. You will see a message like this: > > WARN: resumable backup 20240829-091727F of same type exists -- invalid > files will be removed then the backup will resume > > Any suggestions much appreciated >> > > Boost your process-max as high as you are able to speed up your backup > time. > > what will be the ideal process-max number to use ? Once I update the process-max param in pgbackrest.conf , do I need to stop and start the pgback rest ? Or just editing the pgbackrest.conf on the fly will reflect the increased process-max numbers advantage ? Is there a limit for proces max. setting ? > Cheers, > Greg > > > --0000000000003197300620d4ad65 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Aug 29, 2024 at 6:54=E2=80=AF= PM Greg Sabino Mullane <htamfids@g= mail.com> wrote:
On Thu, Aug 29, 2024 at 2:21=E2= =80=AFAM KK CHN <kkchn.in@gmail.com> wrote:
I am do= ing a full backup=C2=A0 using PgBackRest from a production server=C2=A0to R= eposerver.=C2=A0=C2=A0
...=C2=A0
= If so, does the backup process start=C2=A0 again from=C2=A0 scratch ?=C2=A0= =C2=A0or it resumes from=C2=A0 where the backup process is stopped=C2=A0 = =C2=A0?=C2=A0

It resumes. Y= ou will see a message like this:

WARN: resumable b= ackup 20240829-091727F of same type exists -- invalid files will be removed= then the backup will resume

Any suggestions much appr= eciated

Boost your process-max = as high as you are able to speed up your backup time.

<= /div>

what will be the ideal process-= max number to use ?=C2=A0

=C2=A0Once I update the = process-max param in pgbackrest.conf ,=C2=A0 do I need to stop and=C2=A0 st= art the pgback rest ?=C2=A0

Or just editing the pg= backrest.conf=C2=A0 on the fly will reflect the increased process-max=C2=A0= numbers advantage ?=C2=A0 =C2=A0

Is there a limit= for proces max. setting ?
Cheers,<= /div>
Greg

=C2=A0
--0000000000003197300620d4ad65--