[MDEV-22182] mariabackup: error: The transaction log file is corrupted. Created: 2020-04-07 Updated: 2021-08-10 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Backup |
| Affects Version/s: | 10.1 |
| Fix Version/s: | 10.1 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Stefan Midjich | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | galera, mariabackup | ||
| Environment: |
CentOS 7, MariaDB 10.1.29-1.el7, four node cluster with a 5th node as read-only slave. One of the nodes is garbd witness. Maxscale load balances in a master/master config. Has worked fine for at least 4 years now. (in spite of deadlock danger) |
||
| Attachments: |
|
| Description |
|
I've had issues with mariabackup/xtrabackup/innobackupex from day one. Can't remember the last time I successfully backed up and restored using these tools. Last couple of years mariabackup has been the tool I use, but it's never working. We always end up restoring from Veeam instead. I'd love to resolve this once and for all. I can't believe the mariabackup version I have is completely broken. If it is, of course we'll have to plan an upgrade. I've attached a transcript of my latest failed attempt at restoring incremental backups. I've followed this document: https://mariadb.com/kb/en/incremental-backup-and-restore-with-mariabackup/ To create the base backup I run: On one of the master DB nodes. To create subsequent incrementals I run the same command but with; $to_lsn is extracted from; This appears to work successfully for many days. It's only the restore that gives me errors. See the attached transcript for those details. Note that in the transcript I attempted a solution I found here: https://tutel.me/c/dba/questions/184185/percona+xtrabackup+transaction+log+corrupted |