Percona XtraBackup moved to https://jira.percona.com/projects/PXB

Incremental backups may take up to 5x more space after the fix for bug #1022562

Bug #1043762 reported by Alexey Kopytov on 2012-08-30

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB	Fix Released	High	Laurynas Biveinis	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.1-pre-initial-release
2.0	Fix Released	High	Laurynas Biveinis	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.0.3
2.1	Fix Released	High	Laurynas Biveinis	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.1-pre-initial-release

Bug Description

Fix for bug #1022562 introduced a regression that may potentially lead to a 5x increase in disk space occupied by incremental backups.

The problem is that after the fix for bug #1022562 incremental backups take 64 KB more per _every_ table, even if it has not been modified. We have customers with 100,000+ tables (see bug #950334). A simple calculation shows their incremental backups would now take 6+ GB more, even if there have been absolutely no data updates.

I think the fix should be re-implemented to properly initialize the 1st page when a new tablespace has to be created on prepare. It's quite easy to do, we can reuse the code from fil_create_new_single_table_tablespace().