kashani wrote: > On 4/6/2011 3:47 PM, Alex Schuster wrote: > >> On Linux there is no difference between the on disk format so rsync > >> away assuming you're keeping roughly the same Mysql version. > > > > Um, but only when the architecture is identical. I'm pretty sure binary > > data is stored in different format on 32bit and 64bit systems.
> I had done it myself in the past a number of times without issue, but > here's the documentation to back it up. > > kashani > > http://wikis.sun.com/display/WebStack/MySQL64bitARC > > "It should be noted that, when switching between 32bit and 64bit server > using the same data-files, all the current major storage engines > (with one exception) are architecture neutral, both in endian-ness and > bit size. You should be able to copy a 64-bit or 32-bit DB either way, > and even between platforms without problems for MyISAM, InnoDB and NDB. > For other engines it doesn't matter (CSV, MEMORY, MERGE, BLACKHOLE and > FEDERATED) either the engine doesn't have a disk storage format or > the format they use is text based (CSV) or based on MyISAM (MERGE; and > therefore not an issue). The only exception is Falcon, which is only > available in MySQL 6.0. > > It is generally recommended from MySQL that a dump and reload of > data for absolute compatibility for any engine and major migration." Interesting. I searched a little, and while there are many warnings that binary data will not survive when moved to another architecture, some people say this definitely is NOT a problem. I stand corrected. Wonko
