[GRLUG] Backing up MySQL

[Michael Mol]

On Fri, Sep 23, 2011 at 5:39 PM, L. V. Lammert <lvl at omnitec.net> wrote:
> At 04:35 PM 9/23/2011, you wrote:
>
>> My (vague, unsophisticated) understanding is that mysqlhotcopy makes a
>> copy of the raw data files. I'll note that I don't know whether or not
>> it even works with InnoDB.
>
> That might be true, .. but the docs mention "files", which would seem to
> indicate ISAM. In this case, the engine is InnoDB.

I'll note that InnoDB can be configured to split to file-per-database
as well. But I'd still be wary of MyISAM support.

>> mysqldump, on the other hand, outputs valid SQL which recreates the
>> database.
>
> Yes, .. but at least it gets the entire database (ISAM *OR* InnoDB).
>
>> BTW, if you think mysqldump is running slow, wait until you try
>> restoring that dump. At 33 hours or so for a backup, it might take you
>> more than a week to restore, depending on the options you gave
>> mysqldump for building the output.
>
> No kidding!

-- 
:wq

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.