- Notifications
You must be signed in to change notification settings - Fork86
Description
I have a some problem with incremental backup (PAGE)
Backup log looks like
2021-06-07 22:04:29 MSK [9524]: INFO: command: /usr/bin/pg_probackup-11 backup --instance pg_server -b PAGE --compress -j 2 --delete-expired --merge-expired --delete-wal
2021-06-07 22:04:29 MSK [9524]: INFO: Backup start, pg_probackup version: 2.4.15, instance: pg_server, backup ID: QUCIBH, backup mode: PAGE, wal mode: ARCHIVE, remote: true, compress-algorithm: zlib, compress-level: 1
2021-06-07 22:04:29 MSK [9524]: WARNING: This PostgreSQL instance was initialized without data block checksums. pg_probackup have no way to detect data block corruption without them. Reinitialize PGDATA with option '--data-checksums'.
2021-06-07 22:04:30 MSK [9524]: INFO: wait for pg_start_backup()
2021-06-07 22:04:30 MSK [9524]: INFO: Parent backup: QUAPJ1
2021-06-07 22:04:32 MSK [9524]: INFO: Wait for WAL segment /export/backup/wal/pg_server/00000001000000E10000008C to be archived
2021-06-07 22:04:36 MSK [9524]: INFO: PGDATA size: 20GB
2021-06-07 22:04:36 MSK [9524]: INFO: Extracting pagemap of changed blocks
2021-06-07 22:04:39 MSK [9524]: WARNING: Thread [1]: Could not read WAL record at E0/94799998: unexpected pageaddr E0/94800000 in log segment 00000001000000E000000094, offset 7970816
2021-06-07 22:04:39 MSK [9524]: ERROR: Thread [1]: Possible WAL corruption. Error has occured during reading WAL segment "/export/backup/wal/pg_server/00000001000000E000000094"
2021-06-07 22:04:39 MSK [9524]: ERROR: Thread [2]: Interrupted during WAL reading
2021-06-07 22:04:39 MSK [9524]: ERROR: Pagemap extraction failed, time elasped: 3 sec
2021-06-07 22:04:39 MSK [9524]: WARNING: backup in progress, stop backup
My system is
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"
$ pg_probackup-11 --version
pg_probackup-11 2.4.15 (PostgreSQL 11.11)
$ /usr/lib/postgresql/11/bin/postgres --version
postgres (PostgreSQL) 11.7 (Ubuntu 11.7-5.1C)
I have this problem on two different servers and no idea what is wrong