Comments on: mydumper

By: Domas Mituzas

Domas Mituzas — Thu, 09 Jun 2011 12:16:52 +0000

I think there were some build instructions – it uses cmake nowadays, I hear. Check out also website at http://mydumper.org/

By: Domas Mituzas

Domas Mituzas — Thu, 09 Jun 2011 12:16:22 +0000

@Jeff, http://dom.as/2010/05/08/on-hot-backups/ ;-)

And sometimes people want logical dumps too, which xtrabackup doesn’t do.

By: Jeff Schroeder

Jeff Schroeder — Thu, 09 Jun 2011 12:12:55 +0000

Try xtrabackup from percona. It is essentially a reimplementation of mysqlhotcopy that works with their version of innodb in the percona mysql server and with the standard upstream mysql + innodb.

By: Anurag

Anurag — Thu, 02 Jun 2011 06:48:55 +0000

Hi Domas,

I download mydumper-0.2.3.tar.gz , and untar it , found mydumper-0.2.3.

[root@adampur mydumper-0.2.3]# make
make: *** No targets specified and no makefile found. Stop.

Although, I have installed all the required packages though yum.

Kindly suggest !!

Regards,
Anurag

By: MySQL Data Dumper 0.2.0 released! « LinuxJedi's /dev/null

MySQL Data Dumper 0.2.0 released! « LinuxJedi's /dev/null — Mon, 09 May 2011 14:07:39 +0000

[...] couple of years ago Domas Mituzas created a tool which could basically be thought of as basically a lightweight multi-threaded mysqldump. By this [...]

By: Tarto

Tarto — Fri, 08 May 2009 08:19:30 +0000

I removed PCRE_NEWLINE_ANY and it worked perfectly.
Really fast and easy to use!
I need to run more tests but it looks very promising.
Thank you for such a nice tool.

By: Domas Mituzas

Domas Mituzas — Thu, 07 May 2009 16:18:33 +0000

my fault – it has been fixed in trunk though, I was depending on too new PCRE version.

just removing PCRE_NEWLINE_ANY from the file helps ;-)

I’ll release 0.1.6 with that fix, I guess, was a bit slacking, and expecting more changes to accumulate.

By: ddddddddddddd

ddddddddddddd — Thu, 07 May 2009 13:09:45 +0000

[root@localhost mydumper-0.1.5]# yum install glib2-devel mysql-devel zlib-devel pcre-devel
Setting up Install Process
Parsing package install arguments
Package glib2-devel – 2.12.3-4.el5_3.1.i386 is already installed.
Package mysql-devel – 5.0.45-7.el5.i386 is already installed.
Package zlib-devel – 1.2.3-3.i386 is already installed.
Package pcre-devel – 6.6-2.el5_1.7.i386 is already installed.
Nothing to do
[root@localhost mydumper-0.1.5]# make
cc `mysql_config –cflags` `pkg-config –cflags glib-2.0 gthread-2.0` `pcre-config –cflags` -O3 -g -c -o mydumper.o mydumper.c
mydumper.c: In function ‘check_regex’:
mydumper.c:112: error: ‘PCRE_NEWLINE_ANY’ undeclared (first use in this function)
mydumper.c:112: error: (Each undeclared identifier is reported only once
mydumper.c:112: error: for each function it appears in.)
make: *** [mydumper.o] Error 1
[root@localhost mydumper-0.1.5]#

Thank you for “nice” software.

By: Domas Mituzas

Domas Mituzas — Sun, 19 Apr 2009 16:47:56 +0000

Baron,

I know about mk-parallel-dump options and about the –tab :). Actually in my tests gzip doesn’t matter (client has enough of CPU to facilitate that ;-) – and I don’t want to use tab formats (the whole idea was having the logical sql dump).

This project showcases that there are ways to do things better ;-)

By: Xaprb

Xaprb — Sun, 19 Apr 2009 16:36:19 +0000

What options did you use for mk-parallel-dump? If you give it –tab, it does NOT use mysqldump, it uses SELECT INTO OUTFILE. This might end up being faster than mydumper. Of course it only works if you run it on the same machine you’re dumping. Oh, and by default it’s gzipping the result of the dump, so if you disable that, it should be faster too.

Not that I disagree with you: Perl ain’t the solution here…