Re: [Bacula-users] MySQLdump import seems very slow for Filename and Path tables

2013-03-21 Thread Uwe Schuerkamp
On Tue, Mar 19, 2013 at 10:37:13AM -0500, Melvin Ross wrote: You may also want to try Xtrabackup from Percona. -Melvin Brilliant, thanks for the heads-up, Melvin! FWIW, in order to get xtrabackup to work with MariaDB 5.5, I had to add a [mysqld] section to my.cnf, pointing to the correct

Re: [Bacula-users] MySQLdump import seems very slow for Filename and Path tables

2013-03-19 Thread Uwe Schuerkamp
On Sat, Mar 16, 2013 at 11:39:40AM -0400, Phil Stracchino wrote: 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

Re: [Bacula-users] MySQLdump import seems very slow for Filename and Path tables

2013-03-19 Thread Melvin Ross
You may also want to try Xtrabackup from Percona. -Melvin On Tue, Mar 19, 2013 at 4:24 AM, Uwe Schuerkamp uwe.schuerk...@nionex.netwrote: On Sat, Mar 16, 2013 at 11:39:40AM -0400, Phil Stracchino wrote: On 03/16/13 05:54, Uwe Schuerkamp wrote: Hi folks, I've been warned re-importing

Re: [Bacula-users] MySQLdump import seems very slow for Filename and Path tables

2013-03-18 Thread Clark, Patricia A.
On 3/16/13 11:43 AM, Phil Stracchino ala...@metrocast.net wrote: On 03/16/13 06:18, Jérôme Blion wrote: Le 16/03/2013 10:54, Uwe Schuerkamp a écrit : My question: Is there some way to optimize the catalog dump to make the import faster, like maybe omitting indices and re-creating them

[Bacula-users] MySQLdump import seems very slow for Filename and Path tables

2013-03-16 Thread Uwe Schuerkamp
Hi folks, I've been warned re-importing an innodb mysql database was slow, but I hadn't expected it to be *this* slow. I'm dumping a catalog instance that is about 55GB in size (dump), but the file table has 294GB in the database, so obviously there's a lot of unused / deleted data in there.

Re: [Bacula-users] MySQLdump import seems very slow for Filename and Path tables

2013-03-16 Thread Jérôme Blion
Le 16/03/2013 10:54, Uwe Schuerkamp a écrit : My question: Is there some way to optimize the catalog dump to make the import faster, like maybe omitting indices and re-creating them manually once the import has completed? Seeing the Path table also has 19GB, its import probably won't have

Re: [Bacula-users] MySQLdump import seems very slow for Filename and Path tables

2013-03-16 Thread Phil Stracchino
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

Re: [Bacula-users] MySQLdump import seems very slow for Filename and Path tables

2013-03-16 Thread Phil Stracchino
On 03/16/13 06:18, Jérôme Blion wrote: Le 16/03/2013 10:54, Uwe Schuerkamp a écrit : My question: Is there some way to optimize the catalog dump to make the import faster, like maybe omitting indices and re-creating them manually once the import has completed? Seeing the Path table also has