Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Add documentation on Incremental backup with page tracking could fail if it's not able to copy the system tablespace

Description

To reproduce the error consistently, the environment should have:

(1) More than one system tablespace

(2) sysbench running OLTP RW with tables that have secondary indexes

(3) Looping concurrent transactions that delete all rows on the table but then rollback right after

MySQL configuration:

Instructions on populating tables with sysbench and starting it:

Running Xtrabackup full backup followed by successive incremental backups:

At this point incremental backups will run successfully. To get the incremental backup to fail, run the following in different sessions:

Session 1:

Session 2:

Session 3:

Then, incremental backups will fail:

Environment

None

AFFECTED CS IDs

CS0048131

Activity

Show:

Satya Bodapati September 4, 2024 at 9:49 AM
Edited

Unfortunately yes. We have added the current bug to the backlog. We will take care of it in the future to remove the limitation.

Francisco Miguel Biete September 4, 2024 at 8:00 AM

Am I to understand that page tracking is not supported with multi-ibdata tablespace with XtraBackup?

I don’t see that limitation with MySQL Enterprise Backup

Satya Bodapati August 13, 2024 at 3:44 PM

Someone asked on the support ticket (may be) , why are the ibdata pages being tracked?? Thats a good question.

It is because of innodb_change_buffering. The change buffer still exists in ibdata*. Undo is in separate tablespaces by default. So another way to workaround this bug would be to disable innodb change buffer by using innodb_change_buffering=none.

Satya Bodapati August 13, 2024 at 3:11 PM

Updates: am able to reproduce the bug and record it in rr.

To me it looks this multi-file tablespace (idata*) is causing some confusion wrt to page_number and the actual file offset.

Work in progress..

Done

Details

Assignee

Reporter

Labels

Needs QA

No

In progress time

1.1

Time tracking

No time logged1d 1h remaining

Components

Sprint

Fix versions

Affects versions

Priority

Smart Checklist

Created July 16, 2024 at 7:37 AM
Updated December 23, 2024 at 11:42 AM
Resolved September 3, 2024 at 2:38 PM