Details
Description
Customer is running backup on very large dataset (18TB). Backup completes successfully, but fails during prepare step.
Here is the planned backup process as the customer has detailed:
-
- On Source:
mariabackup --user=root --backup --target-dir=/opt/database/backup --stream=xbstream --parallel=12 | pigz -c | socat - TCP-LISTEN:4444,reuseaddr - On Target
rm -rf /var/lib/mysql/*
rm -rf /var/log/mysql/*
cd /var/lib/mysql
socat -u TCP:192.168.111.184:4444 STDOUT | pigz -dc | mbstream -x
mariabackup --user=root --use-memory=100G --prepare --target-dir=/var/lib/mysql/
rm -rf ib_logfile*
chown -R mysql:mysql /var/lib/mysql/
systemctl start mariadb
- On Source:
The prepare fails as such:
2020-11-03 15:08:46 0 [Note] InnoDB: To recover: 2407553 pages from log
2020-11-03 15:08:54 0 [ERROR] InnoDB: Not applying INSERT_REUSE_REDUNDANT due to corruption on [page id: space=0, page number=120831]
2020-11-03 15:08:54 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore corruption.
Attachments
Issue Links
- causes
-
MDEV-25328 --innodb command line option causes mariabackup to fail
- Closed
- is blocked by
-
MDEV-25031 Not applying INSERT_REUSE_REDUNDANT due to corruption on page
- Closed
- relates to
-
MDEV-17289 Multi-pass recovery fails to apply some redo log records
- Closed
-
MDEV-21724 Optimize page_cur_insert_rec_low() redo logging
- Closed
-
MDEV-24719 backport MDEV-24705 from 10.5 to 10.2, 10.3, 10.4
- Closed
-
MDEV-25031 Not applying INSERT_REUSE_REDUNDANT due to corruption on page
- Closed
-
MDEV-24705 add check that LSN of the last skipped log record equals to FIL_PAGE_LSN field
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...