partial backup includes ibdata1 big file

Bug #1632258 reported by djay45
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Invalid
Undecided
Unassigned

Bug Description

Hello,

When I operate a partial backup one one database (or few tables), xtrabackup includes the ibdata1 (460Mo) in the backup whereas the database folder size is to 140ko.

Is it necessary to keep ibdata1 in the backup ? (in particular for preparing backup). I restore after individual tables ( via discard, import).

Is there an option to ignore ibdata1 file in the partial backup?

I create a bug because I had no answer to my question.

Thanks in advance,
Regards,
Jérémy

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

Yes, it is necessary to include system tablespace in order to prepare the backup and perform the export operation. System tablespace contains undo logs which are needed to rollback incomplete transactions and change buffer which needs be to merged into the tablespaces.

Changed in percona-xtrabackup:
status: New → Invalid
Revision history for this message
djay45 (djay45) wrote :

Hi Sergei,

Ok, I understand but it is strange to have ,in the case partial backup of 460mo including a database of 200ko and a tablespace system of 459Mo.

Mysql Enterprise Backup proposes an option (--use-tts: transportable tablespace) for specific tables and selective backup sets. So partial backup size is small (528ko) and the system tablespace is not backed up (skipping the binary log or the relay log in the backup).

So, for the next releases, do you foresee to develop that similar feature?

If not, before asking to relevant people, is it possible to do it?

Thank for your response.
Jeremy

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

Using transportable tablespaces for backup is completely different feature from what we call partial backup in xtrabackup.

It may be useful in some cases, but we yet to decide its priority.

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :
Revision history for this message
Lafaille (chlafaille) wrote :

Hi,

this missing feature is critical for my society... it blocks our migration from mysql to mariadb !

I hope you'll decide to solve it quickly.

For the moment, a red flag is raised for our migration process.

Revision history for this message
djay45 (djay45) wrote :

Hi Sergei,

Currently, we are testing migration from mysql to mariadb and backup one by one shema via our application.

So are you foresee a change request to take into account transportable tablespaces feature?

This is an important feature for us.

Thanks,
Regards,
Jeremy

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

@djay45 sorry, there is no plan to add this feature in near future.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1405

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.