I didn't mention xtrabackup because I have no experience with it =) I know the other
methods work, and honestly, for most mysql users just starting out, it's easier to use
mysqldump. It's simple, and it's easy to get help with, and it works across storage
From: tlyons@stripped [mailto:tlyons@stripped] On Behalf Of Todd Lyons
Sent: Thursday, September 10, 2009 3:44 PM
To: Gavin Towey
Subject: Re: DB/table problem
On Thu, Sep 10, 2009 at 2:49 PM, Gavin Towey <gtowey@stripped> wrote:
> When using innodb, your data is stored in the data/ibdata* files. Copying the
> database directory is not a valid backup.
> In the future, I would suggest using mysqldump. However if you want to make a
> file-system copy backup with innodb you need to 1. Shutdown the server 2. Copy
> *everything* in the data directory 3. Store a copy of your my.ini with the backup as well.
> 4. Restart mysql
Do you exclude xtrabackup as a potential solution because he's using
Windows (it doesn't build on Windows) or because you have some issue
or problem with xtrabackup? I'm not aware of any show-stopper bugs.
I'm just curious, because it works well for us. The backup is online
with the only lock held occuring while it's copying over the *.frm and
*.MY* files, which is not very much for us.
The information contained in this transmission may contain privileged and confidential
information. It is intended only for the use of the person(s) named above. If you are not
the intended recipient, you are hereby notified that any review, dissemination,
distribution or duplication of this communication is strictly prohibited. If you are not
the intended recipient, please contact the sender by reply email and destroy all copies
of the original message.