Problem with back-up/recover

I'd like to know if MySQL performs a table integrity check
based on storage file date... Yesterday I copied an entire
database directory and when I finished I got a 127 error. I
tried also to recover previously backed-up files but the fatal
error continued to appear... Is there a solution, or I have
to set mysql (and its databases) again ?
Thank you !

--
Giuseppe Bonaccorso

WWW: http://www.giuseppebonaccorso.it
NewsID: newsid@giuseppebonaccorso.it

Giuseppe Bonaccorso wrote:
> I'd like to know if MySQL performs a table integrity check
> based on storage file date... Yesterday I copied an entire
> database directory and when I finished I got a 127 error. I
> tried also to recover previously backed-up files but the fatal
> error continued to appear... Is there a solution, or I have
> to set mysql (and its databases) again ?
> Thank you !
>

You can't just copy a directory (or files) unless MySQL is completely
shut down. Even then you must ensure you have *everything* - for
instance MySQL also keeps information on available databases in its own
tables.

And no, I don't believe the integrity check is based on the file date.
That would be very unreliable. Rather I believe it's based on
information kept internal to the files.

If you don't have a good backup of the entire system, chances are you're
going to have to set up MySQL again.

And next time I'd suggest you use mysqldump to dump your database. It
ensures a good copy.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================