I would not recommend copying the file structure.
IMHO, mysqldump is a lot safer if you have use the correct parameters in the
dump command (lock tables, flush, delayed insert, etc.). Study the available
options in mysqldump.
When you copy the file structure, there is a risk that a query will be in
progress, potentially corrupting tables. If you are going to copy files, you
should at least shut the server down.
Gerald Jensen
----- Original Message -----
From: "Wouter | esctoday.com" <wouter@stripped>
To: "Januski, Ken" <kjanuski@stripped>; "Win32 MySQL List"
<win32@stripped>
Sent: Tuesday, August 06, 2002 2:42 AM
Subject: RE: Can mysqldump be trusted?
The commands for repairing you are referring to are:
REPAIR TABLE <tablename>
OPTIMIZE TABLE <tablename>
You may want to run those commands on your tables in the same batch file.
Keeps your db fresh and good. You can check the health of your tables with
CHECK TABLE <tablename>
Greetz,
Wouter
ps. if you're using mysqldump for backup, you may want to just copy the data
files instead. they're in the \mysql\data dir.
-----Oorspronkelijk bericht-----
Van: Januski, Ken [mailto:kjanuski@stripped]
Verzonden: 05 August 2002 18:38
Aan: win32@stripped
Onderwerp: Can mysqldump be trusted?
Hi,
I've run into an odd problem: every night I run mysqldump on a database. For
2-3 weeks it kept growing, from 11M to 29M. Then a couple of weeks ago it
dropped down to 2.7M went up to 3.6M over the next week, then dropped to
1K!!
It's run from a batch file with this command:
mysqldump -u user -ppassword --opt DB > D:/DBDumps/DB_%Date%, with the
%Date% defined elsewhere.
This has me scared. Does it mean that my database may be corrupted? Does it
mean that mysqldump doesn't do what I think it does, and that I have
corrupted dumps? I did notice that the dumps always end in the middle of
inserting data into the largest table, so that makes me suspect that it is
just mysqldump that has a problem. But I'd sure like to be sure.
I do know that there is a way to repair database. I'm unfamiliar with it and
haven't tried it yet. But I'd first like to get a better idea of what the
above information is really telling me before I go trying to repair the
database.
Any advice appreciated. This is a production server and there will be
serious problems if the database is corrupt.
Ken
---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail win32-thread9441@stripped
To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail win32-unsubscribe@stripped instead.
---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail win32-thread9449@stripped
To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail win32-unsubscribe@stripped instead.
