On Tuesday 03 March 2009, Iñaki Baz Castillo wrote:
what do you mean by not optimized? If the slave is not active (not running) and one use DRDB just for synchronizing the data, how this could be dangerous?
Simpler than that. Forget DB replication stuff. I just mean that if you have a MySQL 1 with a large MyISAM table and you copy it to other server using "scp/rsync", you will get a non optimized or corrupted table (even if both servers have same CPU, architecture and file system).
I've experimented it by copying with "rsync" a 2 GB long MyISAM table. After restarting the MySQL-2 and run a SQL command to check tables [1], you probably will get a "NOT OPTIMIZED TABLE" and you must to repair it. This is the best case.
PD: This is based on my experience with MySQL. However I'have no too much knowledge on it.
Hi Iñaki,
ok, thanks for the clarification. This sounds strange. I mean, how is this different to a normal backup/ restore cycle when some machine crash? I'd expect that it simply continue to use the restored data.
Cheers,
Henning