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.96) (envelope-from ) id 1wbWXg-002dP5-32 for pgsql-general@arkaria.postgresql.org; Mon, 22 Jun 2026 04:45:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wbWXf-004Pvn-2A for pgsql-general@arkaria.postgresql.org; Mon, 22 Jun 2026 04:45:51 +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.96) (envelope-from ) id 1wbWXf-004Pvf-0h for pgsql-general@lists.postgresql.org; Mon, 22 Jun 2026 04:45:51 +0000 Received: from mail-ed1-x530.google.com ([2a00:1450:4864:20::530]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wbWXd-00000001XHB-1bIu for pgsql-general@lists.postgresql.org; Mon, 22 Jun 2026 04:45:49 +0000 Received: by mail-ed1-x530.google.com with SMTP id 4fb4d7f45d1cf-693c69b97e7so6334395a12.2 for ; Sun, 21 Jun 2026 21:45:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1782103546; cv=none; d=google.com; s=arc-20240605; b=DKqRBYiG4/Al45zBRSBaER5pX27ucYszQHU/LJViJUDrK9iSoMArRP/1FepJ4v5hZi FiAh2sXGS21ks0QT6h9j4HnwBb61lOaT8/TzswGWI8DjTM7ECDtVKHEQwqIkuWrOgd/S NiKDjmxeHopDd5/zjx501FsRYxei0jlOfeC2yauJZnGUlqfSRlbqyRCFNyaXzAggPxP0 WHqE/6oKLEZOW17SOVyfegOUJ9XtFFRCIAsXnztUKrRpZ/qQS6YvdzPgaVY/sNdME5tE Ik3d2fuh++nwRQmvsniqnigGx561eDWkwxk3G6mZ96IXYfoGJoRL5Ds4KruSH1s5LNFG /SNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=QyFB0HZ4zdzvpCT3NamiyyrzcPw/PTjqEQWoEKKOVRA=; fh=9wcRWTN0b0esSw84k4RMWm+snNyrDNgx2g9AL/62EvE=; b=ACeLdDs0aapqevLFZkdORLevxkwmS07FLp9ANYLfMwxKRcu1F846xoKFu1SWOZ6GKF fY+KOfz+/K4IXBu9RZ89ugYykWbJJZQCevek1NXNubc7Vg6NplppRolxiXCuQrIajW9b GTeSHdcyL98J1ojXmfxNcM5yELXAc71XTb/7NtU4sfZzjmnsNK8LQeFgVp8x75ZHstrT xxZAaiHp4FqsJjLXiAwUzVslVaSprnfGweWh3c5XYHQ6lPrUwkxKPP7CoPG/toOpLR9G ZWo3GLAK8DiTgi3J8FYqncdU37cisb7Eg+tRkwnVqBnbjHRbQIJTTM3Uy6T6gEqjRZEH f3qw==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1782103546; x=1782708346; darn=lists.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=QyFB0HZ4zdzvpCT3NamiyyrzcPw/PTjqEQWoEKKOVRA=; b=n+sw0hsibtqHcAvosbcYf+K9oFo9dsknVrL/NEN3ZfakBBdNtbR2wyHzk+wg0HFa66 PDES7eFj8EtrV6wzgq9Cvnm9h6IGZdsrhwqdmEjpolJfHuRG8mkD57n/C0LHdw3JMexi TiMFRew3CDJB60RT6Q3xEtZqqZD7tPUsH5y/CW4SbNFxTh2FErc6efeSuUBrFuYiKpYj CD6HPWAzARe981EsdlvIEHIhPQhc3qdUJPC6aI3OX6k1T+GfS+cuVq2mgdvPPygooDqP xkXNw6tvJNEp4f0licGK0FPNdnshchjoagPsa/f4BMZoxpdpgnrEI88IcTbBek78kw+G q8qQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1782103546; x=1782708346; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=QyFB0HZ4zdzvpCT3NamiyyrzcPw/PTjqEQWoEKKOVRA=; b=rrtCv4XQXDvgOevxEJklnnjrMOGC98sTSx1c0OKZvWHGfgJf5TErPQX60FPK3becOO FVhnx14eIBsgjkIiQpOnxHpnJD8g6xdBYngySjJD4Ah+uDA1u2/vPtcBgk2eyKNninpU IG1RpY3ULk949cNRdtE22z/ehlTYPtn6MkHUvVdD3aPwuAr1znUvqTqGN5YA6yXTDO7n LW1VRHk2HCD+sp/Q2jF4smkym9I61KJNmo1lsPxCzY2cWPc9yrqSey13M6JKwdcaegqO 6ELLFYAfkrSPL8ekmDtMJhotZHurtQDhv19BSBpQ+NHpzYi2Nd3Vq7yB9v7R5NK+biLo ATfQ== X-Gm-Message-State: AOJu0YyqZeWyeeTSQQrp5J3HXNJq4S6+rhF+QOpc+lqADLhHjBDaVTAZ sNHUZBcw0eDVK8CWwPdBLwmckJ5Vj4n+RFQyS+HkgHN9axLl73UdN2kJGq8LHGwLvMPw7jGhGvb uWVZiIc6c0x1++y8cjkPkhl9pKrN3dfI76deW X-Gm-Gg: AfdE7ckDM1JyVYtiqWj781JDNtNqQdUXQUBXxLlWJJABOPeYktxvfvBeRw0c2dWry7y 3HBq46E59a+zf/Bqdmz2gUW64od/gf8cj967H+QeoreXCLdR4Bmon4eVliKt0fbXb/WvxNIL/QX tOIedy7C3lY9Y4qHL1vD1PJE7gQtwAOAIy59RUpR66+l+HEtjRZHI1kduhMcj6J/Wt3ZO94nBcv GlNFzG9zAzkwUi1NDIeC8tpl9jM2AM/LhTA7aMzfAFdly7jP87oNAWq0WVLTah/xW+bEQFNxQ== X-Received: by 2002:a05:6402:1470:b0:697:bdff:176 with SMTP id 4fb4d7f45d1cf-697bdff022amr311494a12.28.1782103545581; Sun, 21 Jun 2026 21:45:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: KK CHN Date: Mon, 22 Jun 2026 10:23:40 +0530 X-Gm-Features: AVVi8CfXn51V-aeQjg3CM4SZRYTZH3ow9-bvBI08_NUXjZ7tt0u6SR5nk7utlho Message-ID: Subject: Re: PgbackRest : backup command end: aborted with exception [101] To: Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000c994000654d0505f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c994000654d0505f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable it stopped full backup multiple times. This time it succeeded, One difference, I have ran the full backup script again immediately after the full backup failure happened after running for almost 20 Hours (2026-06-19 10:49:12.739 P00 ERROR: [101]: raised from remote-0 ssh protocol on '10.140.0.202': NULL result required to complete request) . After this time stamp I scheduled the full backup again on 2026-06-19 11:19 Hrs and it completed the next day 2026-06-20 05:20 Hrs. (~=3D 18 Hrs). I assume the full backup continues from the last point from where it stopped , not afresh when you reschedule the full backup again ? Here the time duration is observed. full backup: 20260614-011004F timestamp start/stop: 2026-06-19 11:19:05+05:30 / 2026-06-20 05:20:17+05:30 wal start/stop: 000000010000158A000000CA / 000000010000159A000000FE database size: 3876.8GB, database backup size: 3876.8GB repo1: backup size: 967.1GB Almost 18 Hrs. diff backup: 20260614-011004F_20260621-030404D timestamp start/stop: 2026-06-21 03:04:04+05:30 / 2026-06-21 04:55:20+05:30 wal start/stop: 00000001000015AD000000E7 / 00000001000015AF00000057 database size: 3895.9GB, database backup size: 70.2GB repo1: backup size: 12.8GB backup reference list: 20260614-011004F approx : 2 Hours As suggested, add the ServerAliveInterval 60 ServerAliveCountMax 3 vars in sshd_config next time and observe the difference. Thank you, Krshane. On Sat, Jun 20, 2026 at 8:22=E2=80=AFPM Greg Sabino Mullane wrote: > Smells like a timeout of some sort to me. Could be a firewall dropping an > "idle" connection. How long does the diff backup take to complete? How lo= ng > from when you kick off the full backup to the time it errors out? Is that > timeout consistent? See if you have ServerAliveInterval set in your ssh > config, and if not, consider adding it (and related vars). > > Cheers, > Greg > > --000000000000c994000654d0505f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

it stopped full backu= p multiple times.=C2=A0 This time it succeeded, One difference,=C2=A0 I hav= e ran=C2=A0 the full backup script again immediately after the full backup= =C2=A0 failure happened=C2=A0after running for almost 20 Hours (2026-06-19 10:49:12.739 P00 =C2=A0ERROR: = [101]: raised from remote-0 ssh protocol on '10.140.0.202': NULL re= sult required to complete request) .=C2=A0 After this time stamp I schedule= d the full backup again on=C2=A0 =C2=A02026-06-19=C2=A0 11:19 Hrs and it co= mpleted the next day 2026-06-20=C2=A0 05:20 Hrs.=C2=A0 =C2=A0(~=3D 18 Hrs).=

<= /div>
I assume the full ba= ckup continues from the last point from where it stopped , not afresh when = you reschedule the full backup again ?=C2=A0

Here the time duration is observed.=C2=A0 =C2=A0<= /span>

full backup: 20260614-011004F
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 timestamp start/stop: 2026-06-19 11:19:05+0= 5:30 / 2026-06-20 05:20:17+05:30
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 wal start/stop: 000000010000158A000000CA / 000000010000159A000000FE
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 database size: 3876.8GB, database= backup size: 3876.8GB
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 repo1: = backup size: 967.1GB

Almost 18 Hrs.=C2=A0


=C2=A0diff backup: 20260614-011004F_2026062= 1-030404D
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 timestamp start/stop= : 2026-06-21 03:04:04+05:30 / 2026-06-21 04:55:20+05:30
=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 wal start/stop: 00000001000015AD000000E7 / 0000= 0001000015AF00000057
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 database = size: 3895.9GB, database backup size: 70.2GB
=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 repo1: backup size: 12.8GB
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 backup reference list: 20260614-011004F

<= div>
approx : 2 Hours

As suggested, add th= e=C2=A0=C2=A0 =C2=A0 =C2=A0 Se= rverAliveInterval 60=C2=A0=C2=A0=C2=A0 =C2=A0 =C2=A0ServerAliveCountMax 3=C2=A0 =C2=A0vars in sshd= _config next time and observe the difference.=C2=A0



Thank you,
Krshane.
<= div>

On Sat, Jun 20, 2026 at 8:22=E2= =80=AFPM Greg Sabino Mullane <htam= fids@gmail.com> wrote:
Smells like a timeout of so= me sort to me. Could be a firewall dropping an "idle" connection.= How long does the diff backup take to complete? How long from when you kic= k off the full backup to the time it errors out? Is that timeout consistent= ? See if you have ServerAliveInterval set in your ssh config, and if not, c= onsider adding it (and related vars).

Cheers,
= Greg

--000000000000c994000654d0505f--