restore pre-2.2.10 compressed backup behavior

[Ernie Souhrada]

Prior to PXB 2.2.10, when decompressing a backup made with --compress, PXB would automatically delete the compressed *.qp files. It no longer does that. Please bring back the old behavior, or provide a command-line option to enable it. Why? Disk space. I can't restore the backups for any of my larger servers because there isn't enough disk space to hold all of compressed backup files and the uncompressed files simultaneously; although I have a manual process to purge them all out after the entire decompression operation is finished, that's not good enough.

170822 06:37:03 [01] decompressing ./pbdataXXXXX/stuff.ibd.qp
qpress: Disk full while writing destination file
cat: write error: Broken pipe
qpress: Disk full while writing destination file
cat: write error: Broken pipe
qpress: Disk full while writing destination file
cat: write error: Broken pipe
...

FWIW - I am using PXB 2.3.9.

[Ernie Souhrada (denshikarasu)]

Nevermind. It appears that I can do what I need to do with --remove-original. But it should be more obvious in the documentation that this is how to recreate the old behavior.

[Sergei Glushchenko (sergei.glushchenko)]

Hi! Thanks for the bug report. We have following in our docs:

https://www.percona.com/doc/percona-xtrabackup/LATEST/backup_scenarios/compressed_backup.html

Percona XtraBackup doesn't automatically remove the compressed files. In order to clean up the backup directory you should use xtrabackup --remove-original option. Even if they're not removed these files will not be copied/moved over to the datadir if xtrabackup --copy-back or xtrabackup --move-back are used.

How we can further improve this page? Maybe we should mention this option in other places?

[Ernie Souhrada (denshikarasu)]

I think in the ideal scenario, I would add the --remove-original option to innobackupex and pass it through to xtrabackup, so that people who are currently using innobackupex to take / restore backups don't need to worry about which binary to use. The confusing part is that there are two different binaries which accept two different sets of options, and some things which work with one do not work with the other (for example, '--remove-original').

Alternatively, maybe the better solution is to just get rid of innobackupex entirely in the 2.5 release series and only have a single xtrabackup binary. Then there's no confusion - it's one binary, with one set of command-line options.

[Sergei Glushchenko (sergei.glushchenko)]

Our plan is to get rid of innobackupex in 2.5.

[Launchpad Janitor (janitor)]

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

[Shahriyar Rzayev (rzayev-sehriyar)]

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