The idea is to have backups.
Backups of unchecked data are not useless.
Backups of truncated data files are.
People have lost data when the disk became full during isamchk, or the
index had been crashed because it reached filesystem size limits.
If you blow the data away with a failed [my]isamch
If you back them up before you check them, and the check blows up, you
still have your backups.
Koen Gogne wrote:
> hi,
>
> I'm trying to automate the back up of my MySQL databases,
> and before I perform my backup I check my tables using
> myisamchk and isamchk.
> When myisamchk and isamchk r
hi,
I'm trying to automate the back up of my MySQL databases,
and before I perform my backup I check my tables using
myisamchk and isamchk.
When myisamchk and isamchk report errors I would like to catch that
and maybe perform a restore operation.
hence my question: what could go wrong when runn
hi,
I'm trying to automate the back up of my MySQL databases,
and before I perform my backup I check my tables using
myisamchk and isamchk.
When myisamchk and isamchk report errors I would like to catch that
and maybe perform a restore operation.
hence my question: what could go wrong when runn