xbstream extraction does not output usable archive

Bug #989488 reported by Walker Traylor on 2012-04-27
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Hrvoje Matijakovic

Bug Description

I created a backup using :
 innobackupex-1.5.1 --stream=xbstream --parallel=4 --compress --compress-threads=2 /var/lib/mysql | ssh walker@db-stat-slave cat > db-stat-newbackup

I attempted to restoring using:
 xbstream -x < /home/walker/backups/db-stat-newbackup

The xbstream operation completed with a "bad magic" error.

The output of du -hs in the restore directory was the same as the xbstream file.

I attempted to run --apply-log to process the directory, but it couldn't read the files.

I noticed most of them ended in .qp.

I don't know if I'm supposed to decompress them myself, or if that was supposed to be handled by streamxb and failed, or if xtrabackup --apply-log is supposed to handle that step.

Tags: doc Edit Tag help

Related branches

description: updated
Alexey Kopytov (akopytov) wrote :

Yes, compressed archives must be decompressed before --apply-log. We don't have that documented explicitly, so changing this bug into a documentation bug.

As to the "bad magic" error, it's most likely bug #983720. The fix will be released in XtraBackup 2.0.1

tags: added: doc
Changed in percona-xtrabackup:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Hrvoje Matijakovic (hrvojem)
milestone: none → 2.0.1
Changed in percona-xtrabackup:
status: Triaged → In Progress
Changed in percona-xtrabackup:
status: In Progress → Fix Committed
Changed in percona-xtrabackup:
status: Fix Committed → Fix Released

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

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

Duplicates of this bug

Other bug subscribers