On 03/16/13 05:54, Uwe Schuerkamp wrote:
> Hi folks,
>
> I've been warned re-importing an innodb mysql database was slow, but I
> hadn't expected it to be *this* slow.
The basic problem here is that mysqldump has not aged or scaled well,
and badly needs to be put out to pasture in favor of something better.
I won't go into all of its failings here; suffice it to say that there
are many of them.
One better alternative is mydumper. Just for starters, it can dump and
restore in parallel, and it inherently understands transactional and
non-transactional storage engines and can correctly back up both in a
single run on a table-by-table basis, something which is simply not
possible with mysqldump. However, it's still not hugely faster for
restores than mysqldump because it's still a logical dump and mysqld
still has to re-execute all the SQL.
Another option is Percona's XtraBackup, which does a binary backup
rather than a logical dump. It is much faster both to back up and
restore, but restores are all-or-nothing and the backup is not
guaranteed portable across architectures or operating systems. It's
also very much some-assembly-required, and the documentation is terrible.
Probably the best tool currently available is MySQL Enterprise Backup,
but as the name implies it requires a MySQL Enterprise license.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
