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 1sjf8l-002jNR-Bs for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 13:24:43 +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 1sjf8i-002FJi-Ss for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 13:24:41 +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 1sjf8i-002FJZ-Ha for pgsql-general@lists.postgresql.org; Thu, 29 Aug 2024 13:24:41 +0000 Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sjf8g-00219e-K7 for pgsql-general@postgresql.org; Thu, 29 Aug 2024 13:24:39 +0000 Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-5344ab30508so1645616e87.0 for ; Thu, 29 Aug 2024 06:24:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724937877; x=1725542677; 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=yAvwKPuTN8utRzfQL59aj4NaFOuDszE+rR7enLWDdwE=; b=J7WE/olGoeldUXPe2ukvv7coRJ9783+vdNOkjwoL8qjNt0lmpouRUZTwCn34ySqIYI 4t+5UElIBJgyYcQ74w7BJCiIlUx2SFWMRaC9vupT+zV2CQps/ZJl4U0T8HG06eWcOn3z JVf1/Bi/lDXWLbbLZOnLh9+XJ2bb5Uy3Xd6cfmNWuLTxhqh5qFGdkYnWIIKdjHNE4Udr z1DbjGsSmF2geUJOwMI+Zt9DtVRid9K/cr1jWa3UxQKxamA6BUZz2q7ItRsi9qBf1uN3 74xx1IukhMsJ4rbYU3JLCsA/ALOfJQZ4bM2M697fYOAgiHggSR4LWm7L+hmVEa+MF2cp 3Wjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724937877; x=1725542677; 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=yAvwKPuTN8utRzfQL59aj4NaFOuDszE+rR7enLWDdwE=; b=kruCeAxNREuocoT1StrMrQ/i/S1G1/Htcj6Qc6ktDJy8HIfwJNf7Xmfmp0vU02/tMo dQQSP5DD7h4TYk5HHtEPxhNfVDpOP1OYRF37YYycCsyeiDF7EZ3kRQCZMijajyS75mx/ tmboxX8bCsef3BX4KmevYSCI3ZnKCfCki+xGrNsu8f6jMwhF8EDii7DoMVouzrVNimP8 LKM9IGx5dx0zO4rGydFPZalwKnoy7fZ9t50wQUxWfQ0k1aSmIAURpDaWHVIQ2ueZTabt 35Jnh/4CyAk6cCy3b4LLFuwaCimtH9gDUuXV7iMCVHH5Mkc7izwyK4Mvc+gMBKOs+kmm lpvA== X-Gm-Message-State: AOJu0YwRyXjXtSQku/G58pkP12neBWKIkm2zUNgrt1Tg8PSXCdbszyc/ 2aT2U3TMs9X3wvYk2r15RuwTC/bRC5jCSkaPJ2zeL8VGzA8KXx5A8WeNFaX5oNOldjTYnA2zBmb 6wEkJjrLr8tef2z5b+HKfQLy3gyY= X-Google-Smtp-Source: AGHT+IGH3x+pe2TEcNc2u1jvOBflmHpd6mA6FcfuxtdrJ2XZRSgZWCsGiIYnZtlyRjaGWJ+29X29omHbimszped6BD4= X-Received: by 2002:a05:6512:23a0:b0:533:415e:cd9a with SMTP id 2adb3069b0e04-5354104f2a2mr825877e87.23.1724937876181; Thu, 29 Aug 2024 06:24:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Thu, 29 Aug 2024 09:24:00 -0400 Message-ID: Subject: Re: PgBackRest Full backup and N/W reliability To: KK CHN Cc: pgsql-general Content-Type: multipart/alternative; boundary="0000000000005e9c560620d26595" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005e9c560620d26595 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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= . Cheers, Greg --0000000000005e9c560620d26595 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Aug 29, 2024 at 2:21=E2=80=AFAM K= K CHN <kkchn.in@gmail.com> = wrote:
I am doing a full backup=C2=A0 usin= g PgBackRest from a production server=C2=A0to Reposerver.=C2=A0=C2=A0
=
...=C2=A0
If so, does the backup proce= ss 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. You will see a message like th= is:

WARN: resumable backup 20240829-091727F of sam= e type exists -- invalid files will be removed then the backup will resume<= br>

<= div dir=3D"ltr">
Any suggestions much appreciated

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

Cheers,
Greg

=C2=A0
--0000000000005e9c560620d26595--