Documentation explains wrongly what files compression affects

Bug #1239791 reported by Jaime Crespo on 2013-10-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to
Fix Released
Hrvoje Matijakovic
Fix Released
Hrvoje Matijakovic
Fix Released
Hrvoje Matijakovic
Fix Released
Hrvoje Matijakovic

Bug Description

Here <> it says:

"When compression is enabled, xtrabackup compresses all output data, including the transaction log file and meta data files, using the specified compression algorithm. The only currently supported algorithm is ‘quicklz’. The resulting files have the qpress archive format, i.e. every *.qp file produced by xtrabackup is essentially a one-file qpress archive and can be extracted and uncompressed"

Only Innodb tablespaces seem to be compressed (.ibd s and ibdata1), no metadata, no logs, no non-innodb files.

To reproduce:
// create a compressed backup:
# innobackupex --compress --stream=xbstream /tmp > /media/backups/backup.xbstream
# cd /media/backups
# xbstream -x < backup.xbstream -C .
# qpress -d xtrabackup_logfile .
qpress: Source file was not compressed with qpress
# qpress -d ibdata1.qp .
// <---- no error

# xtrabackup -v
xtrabackup version 2.1.5 for Percona Server 5.1.70 unknown-linux-gnu (x86_64) (revision id: 680)
# innobackupex --version .
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

Tags: doc Edit Tag help

Related branches

Alexey Kopytov (akopytov) wrote :

Yes, meta and non-InnoDB files are not compressed, so we should fix the docs to reflect that.

xtrabackup_logfile not being compressed is a separate issue that should be fixed, reported as bug #1242309.

tags: added: doc

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers