innobackupex tar stream backup not working properly on 50GB database
68 views
Skip to first unread message
Aaron Gould
Feb 4, 2011, 3:31:06 PM2/4/11
to Percona Discussion
I've got a 50GB database that I'm trying to backup using the tar
streaming feature of innobackupex.
Here's my backup command:
innobackupex-1.5.1 --slave-info --stream=tar ./ | gzip - > /var/
backup/mysql/db_2011-02-04.tar.gz
The entire procedure takes several minutes, and appears to complete.
There's even a successful "innobackupex: completed OK!" on the last
line of output.
However, the resuling tar.gz file seems to be bad every time.
Whenever I list the file's contents via the tar command ("tar -iztvf
db_2011-02-04.tar.gz"), tar exits due to failure.
The server is running RedHat Enterprise 4 AS, and the tar and gzip are
the standard ones included in the distribution. innobackupex is
version 1.5.1.
Has anyone experienced this?
Oddly, I tried a much smaller database (< 1GB) on another server, and
everything seems to be ok with the above commands...
streaming feature of innobackupex.
Here's my backup command:
innobackupex-1.5.1 --slave-info --stream=tar ./ | gzip - > /var/
backup/mysql/db_2011-02-04.tar.gz
The entire procedure takes several minutes, and appears to complete.
There's even a successful "innobackupex: completed OK!" on the last
line of output.
However, the resuling tar.gz file seems to be bad every time.
Whenever I list the file's contents via the tar command ("tar -iztvf
db_2011-02-04.tar.gz"), tar exits due to failure.
The server is running RedHat Enterprise 4 AS, and the tar and gzip are
the standard ones included in the distribution. innobackupex is
version 1.5.1.
Has anyone experienced this?
Oddly, I tried a much smaller database (< 1GB) on another server, and
everything seems to be ok with the above commands...
Lee
Feb 6, 2011, 10:56:42 AM2/6/11
to percona-d...@googlegroups.com
The symptoms sound similar to this bug - https://bugs.launchpad.net/percona-xtrabackup/+bug/690822
If you are using a 32 bit binary of tar4ibd it will silently fail to send the entire contents of a (what I thought) was a file more than 64GB but that threshold could be less as I didn't check what the biggest possible file was. If this turns out to be your issue the patch is included in the bug report and is just a one line change changing a size_t type to a long long.
If you are using a 32 bit binary of tar4ibd it will silently fail to send the entire contents of a (what I thought) was a file more than 64GB but that threshold could be less as I didn't check what the biggest possible file was. If this turns out to be your issue the patch is included in the bug report and is just a one line change changing a size_t type to a long long.
--
You received this message because you are subscribed to the Google Groups "Percona Discussion" group.
To post to this group, send email to percona-d...@googlegroups.com.
To unsubscribe from this group, send email to percona-discuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/percona-discussion?hl=en.
Aaron Gould
Feb 7, 2011, 3:17:32 PM2/7/11
to Percona Discussion
Thank you Lee -- the patch worked perfectly! Got a full live backup,
and a "tar -iztvf" of the resulting archive read without error.
On Feb 6, 10:56 am, Lee <leely...@gmail.com> wrote:
> The symptoms sound similar to this bug -https://bugs.launchpad.net/percona-xtrabackup/+bug/690822
and a "tar -iztvf" of the resulting archive read without error.
On Feb 6, 10:56 am, Lee <leely...@gmail.com> wrote:
> The symptoms sound similar to this bug -https://bugs.launchpad.net/percona-xtrabackup/+bug/690822
Reply all
Reply to author
Forward
0 new messages