Try dropping the indexes first if you can, would save you about half the
time and then re-build them after the dump finishes. Obviously you
would need to do it at a quite time though when the DB is not being
used. Is a binary backup not an option? at 29G is a large text file to
write

Ade

David Sparks wrote:
> I'm trying to dump some bigger tables without much luck. Anyone have
> any advice to dump larger tables?
>
> mysqldump starts guns blazing, but quickly it isn't doing anything as
> viewed by strace.
>
> After 1 day trying to dump a MyISAM table with 2.7G .MYD and 5.3G .MYI
> the dumpfile is 270MB compressed and it seems to be dumping 1K per second.
>
> After 12 hours trying to dump an InnoDB table with a 29G .ibd, same
> problem ... data is trickling out.
>
> I'm using mysqldump from 5.0.26 dumping a 4.1.21 server. I've tried
> several incarnations of options, that latest is (-e, -q *should* be
> enabled by default):
>
> mysqldump -e --no-create-db --skip-add-drop-table -q -single-transaction
> -v database
>
> How to speed this up?
>
> TIA!
>
>