seen this type of behavior? It has me totally confused and
ready to switch back to mysqldump. mysqldump would work fine - never had a
problem with it.
What exactly does 'Incorrect information in file' indicate anyway?
Still plugging away
Mike
Original Message --------
Subject: O
For the longest time, I'v ebacked up my various MySQL databases using
mysqldump. However, I hated restarting the database each night (on a few
occasions it would restart but the databases could not be accessed until it
was restarted again) Plus I think mysqlhotcopy is a more elegant solution.
