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. (~= 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 PM Greg Sabino Mullane <[email protected]>
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 long
> 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
>
>
