<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using Xtradb Backup</title>
	<atom:link href="http://www.pythian.com/news/2850/using-xtradb-backup/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news/2850/using-xtradb-backup/</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Thu, 18 Mar 2010 16:45:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gerry</title>
		<link>http://www.pythian.com/news/2850/using-xtradb-backup/#comment-364144</link>
		<dc:creator>Gerry</dc:creator>
		<pubDate>Fri, 26 Jun 2009 18:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=2850#comment-364144</guid>
		<description>I&#039;ve been trying to install xtrabackup/innobackupex for a customer and I&#039;m finding a few glitches, especially w/ streaming:

We use innoback(ex) wrapped in our own scripts to allow for rotation and other operations. We also use ZRM for some installations, so this would apply to integration with this tool as well. These are the glitches I found:

1. Using streaming by piping it into &#039;gzip&#039; masks the return code from innobackupex.pl. Since gzip will almost always return 0, you can&#039;t rely on it to determine backup success.

2. The next alternative would be to review the innobackupex.pl&#039;s output for the OK at the end. But since it redirects the output to &#039;stderr&#039; to allow for streaming, you need to add &quot;2&gt; innobackupex.log&quot; before piping and grep for the &quot;OK&quot; at the end.

3. As Sheeri pointed out, the need to run it as user &#039;mysql&#039; seems to come from the fact that it requires &#039;write&#039; privileges for at least some of the &#039;ibdata*&#039; files. I don&#039;t feel quite comfortable with this requirement since it&#039;s not necessary for &#039;innobackup.pl&#039;

My $.02
Gerry</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been trying to install xtrabackup/innobackupex for a customer and I&#8217;m finding a few glitches, especially w/ streaming:</p>
<p>We use innoback(ex) wrapped in our own scripts to allow for rotation and other operations. We also use ZRM for some installations, so this would apply to integration with this tool as well. These are the glitches I found:</p>
<p>1. Using streaming by piping it into &#8216;gzip&#8217; masks the return code from innobackupex.pl. Since gzip will almost always return 0, you can&#8217;t rely on it to determine backup success.</p>
<p>2. The next alternative would be to review the innobackupex.pl&#8217;s output for the OK at the end. But since it redirects the output to &#8217;stderr&#8217; to allow for streaming, you need to add &#8220;2&gt; innobackupex.log&#8221; before piping and grep for the &#8220;OK&#8221; at the end.</p>
<p>3. As Sheeri pointed out, the need to run it as user &#8216;mysql&#8217; seems to come from the fact that it requires &#8216;write&#8217; privileges for at least some of the &#8216;ibdata*&#8217; files. I don&#8217;t feel quite comfortable with this requirement since it&#8217;s not necessary for &#8216;innobackup.pl&#8217;</p>
<p>My $.02<br />
Gerry</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulM</title>
		<link>http://www.pythian.com/news/2850/using-xtradb-backup/#comment-362363</link>
		<dc:creator>PaulM</dc:creator>
		<pubDate>Thu, 11 Jun 2009 01:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=2850#comment-362363</guid>
		<description>Seems that the 0.7 is already available.

http://www.percona.com/mysql/xtrabackup/0.7/
http://www.percona.com/mysql/xtrabackup/xtrabackup-0.7.tar.gz

So the issue is the wiki points to the old version 0.3
http://www.percona.com/docs/wiki/percona-xtrabackup:howtogetbin

I have updated the wiki.</description>
		<content:encoded><![CDATA[<p>Seems that the 0.7 is already available.</p>
<p><a href="http://www.percona.com/mysql/xtrabackup/0.7/" rel="nofollow">http://www.percona.com/mysql/xtrabackup/0.7/</a><br />
<a href="http://www.percona.com/mysql/xtrabackup/xtrabackup-0.7.tar.gz" rel="nofollow">http://www.percona.com/mysql/xtrabackup/xtrabackup-0.7.tar.gz</a></p>
<p>So the issue is the wiki points to the old version 0.3<br />
<a href="http://www.percona.com/docs/wiki/percona-xtrabackup:howtogetbin" rel="nofollow">http://www.percona.com/docs/wiki/percona-xtrabackup:howtogetbin</a></p>
<p>I have updated the wiki.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerry</title>
		<link>http://www.pythian.com/news/2850/using-xtradb-backup/#comment-362354</link>
		<dc:creator>Gerry</dc:creator>
		<pubDate>Thu, 11 Jun 2009 00:24:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=2850#comment-362354</guid>
		<description>Discussed this with Paul and Sheeri based on some project for clients and I need to add a few items I found:

* innobackupex script is limited in the type of options you can specify compared to what the xtrabackup executable supports. I find this annoying since it limits the directories where you can have the backups, data directories and logs. I&#039;m exploring the possibility of creating a ZRM pluging that should get rid of these limitations.

* Xtrabackup doesn&#039;t work for MySQL v4.1. In the Percona forums there was a suggestion that the 5.0 patch should work. This is true, but xtrabackup.c has other dependencies on 5.x definitions and structures I didn&#039;t have time to review. Baron Schwartz correctly suggested that these dependencies might be trivial in a tweet directed to myself. I&#039;ll post my findings to the Percona forums and hopefully we can soon have a patched version.</description>
		<content:encoded><![CDATA[<p>Discussed this with Paul and Sheeri based on some project for clients and I need to add a few items I found:</p>
<p>* innobackupex script is limited in the type of options you can specify compared to what the xtrabackup executable supports. I find this annoying since it limits the directories where you can have the backups, data directories and logs. I&#8217;m exploring the possibility of creating a ZRM pluging that should get rid of these limitations.</p>
<p>* Xtrabackup doesn&#8217;t work for MySQL v4.1. In the Percona forums there was a suggestion that the 5.0 patch should work. This is true, but xtrabackup.c has other dependencies on 5.x definitions and structures I didn&#8217;t have time to review. Baron Schwartz correctly suggested that these dependencies might be trivial in a tweet directed to myself. I&#8217;ll post my findings to the Percona forums and hopefully we can soon have a patched version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulM</title>
		<link>http://www.pythian.com/news/2850/using-xtradb-backup/#comment-362350</link>
		<dc:creator>PaulM</dc:creator>
		<pubDate>Wed, 10 Jun 2009 23:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=2850#comment-362350</guid>
		<description>We discussed this offline first and Sheeri asked me to post a comment.
The current RHEL/CentOS binaries include a bug where the innodb datadir is incorrectly handled. It is a fixed bug but not in the binaries available.

To get around this I successfully built the rc-0.7 from the source, following the instructions on the xtrabackup website. The main issues with building was building MySQL from the source (not xtrabackup).

Evgeniy, Yasufumi et al, please bite the bullet and release official binaries for rc-0.7

This is bleeding edge software. If you are going to use it in a production environment you need to fully aware that bugs will exist.

Have Fun

Paul</description>
		<content:encoded><![CDATA[<p>We discussed this offline first and Sheeri asked me to post a comment.<br />
The current RHEL/CentOS binaries include a bug where the innodb datadir is incorrectly handled. It is a fixed bug but not in the binaries available.</p>
<p>To get around this I successfully built the rc-0.7 from the source, following the instructions on the xtrabackup website. The main issues with building was building MySQL from the source (not xtrabackup).</p>
<p>Evgeniy, Yasufumi et al, please bite the bullet and release official binaries for rc-0.7</p>
<p>This is bleeding edge software. If you are going to use it in a production environment you need to fully aware that bugs will exist.</p>
<p>Have Fun</p>
<p>Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shlomi Noach</title>
		<link>http://www.pythian.com/news/2850/using-xtradb-backup/#comment-362281</link>
		<dc:creator>Shlomi Noach</dc:creator>
		<pubDate>Wed, 10 Jun 2009 04:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=2850#comment-362281</guid>
		<description>Hi Sheeri,

I think it&#039;s worthwhile mentioning that Xtrabackup allows for streaming: you can pipe the backup into &#124; tar, &#124; ssh, what have you.
I think this must be one of its simple yet big advantages. ibbackup requires enough local or nfs mounted disk space, while xtrabackup allows for easy network backup. (with ibbackup it&#039;s even worse when restoring from backup: it actually requires the backup and restored files to be on the same directory).

Cheers</description>
		<content:encoded><![CDATA[<p>Hi Sheeri,</p>
<p>I think it&#8217;s worthwhile mentioning that Xtrabackup allows for streaming: you can pipe the backup into | tar, | ssh, what have you.<br />
I think this must be one of its simple yet big advantages. ibbackup requires enough local or nfs mounted disk space, while xtrabackup allows for easy network backup. (with ibbackup it&#8217;s even worse when restoring from backup: it actually requires the backup and restored files to be on the same directory).</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan R</title>
		<link>http://www.pythian.com/news/2850/using-xtradb-backup/#comment-362263</link>
		<dc:creator>Dan R</dc:creator>
		<pubDate>Tue, 09 Jun 2009 22:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=2850#comment-362263</guid>
		<description>While there&#039;s no compress option supported yet, you can stream your backup to gzip:

#&gt; innobackupex --user=foo --password=bar --stream=tar ./ &#124; gzip - &gt; /path/to/backup.tar.gz

I haven&#039;t tested it extensively, but it worked for me.</description>
		<content:encoded><![CDATA[<p>While there&#8217;s no compress option supported yet, you can stream your backup to gzip:</p>
<p>#&gt; innobackupex &#8211;user=foo &#8211;password=bar &#8211;stream=tar ./ | gzip &#8211; &gt; /path/to/backup.tar.gz</p>
<p>I haven&#8217;t tested it extensively, but it worked for me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
