Comments on: mysqlpdump

By: fr3nd

fr3nd — Thu, 20 Nov 2008 09:35:22 +0000

Que bò, havia llegit alguns capitols del llibre, pero no tot… suposo que hauré de fer-li una repassada més intensa :)
Merci per avisar

By: dani

dani — Wed, 19 Nov 2008 23:37:51 +0000

surts referiat a la segona edicio del “High Performance MySQL” pero veient qui et comenta més amunt, no m’extranya

By: fr3nd

fr3nd — Fri, 14 Sep 2007 08:24:13 +0000

This tool automatically locks all tables before starting the dump, so there is no need to lock them manually. It’ll create a consistent dump.

About the restore tool, I don’t think it’s needed… Restoring is as easy as doing:

cat *.sql | mysql

By: Monty Taylor

Monty Taylor — Thu, 13 Sep 2007 18:56:25 +0000

Thanks for the tool! I love it. I used it and blogged about it yesterday, and then today I wrote a restore tool for it (http://mysql-ha.com/2007/09/13/mysqlprestore-for-parallel-restores/)
Please feel free to grab the file and incorporate it however you like. I tried to do it in such a way that the two could be merged pretty well, I think.

By: Peter Zaitsev

Peter Zaitsev — Thu, 13 Sep 2007 09:52:44 +0000

Thank you !

Too bad MySQL does not have support for several connections sharing same transactional context so the only way you can get consistent backup is setting low priority updates and locking all the tables. As you have multiple threads you may have no luck locking all of them otherwise.

By: Devis

Devis — Thu, 13 Sep 2007 07:19:49 +0000

Hi danielj, to create a consistent dump you need to lock *all* tables before the dump.

By: danielj

danielj — Thu, 13 Sep 2007 07:09:36 +0000

This sounds very interesting and promising; but I think it will not be possible to create a consistent dump that way? Or how should locking be handled?

By: fr3nd

fr3nd — Thu, 07 Jun 2007 09:26:26 +0000

Devis: version 0.5 fixes that bug. Thanks for the bug report!

By: Devis

Devis — Wed, 06 Jun 2007 12:37:20 +0000

Hi fr3nd I’ve put mysqlpdump in a cron job but I am having little problems:

——-
Traceback (most recent call last):
File “mysqlpdump.py”, line 241, in ?
main()
File “mysqlpdump.py”, line 187, in main
parser.add_option(“-u”, “–user”, action=”store”, dest=”user”, type=”string”, default=os.getlogin(), help=”User for login.”)
OSError: [Errno 25] Inappropriate ioctl for device
——-

It is caused by “os.getlogin()” in combination with cron, as there isn’t any terminal or logged user.
For the moment I’ve substitued this with ‘root’ and it works for me.

By: Devis

Devis — Tue, 05 Jun 2007 15:51:22 +0000

Wonderful, it works! 10M Kudos to you!
Surely I will follow the script evolution and if I can help just write me :-)
Thank you!