I'm not sure that is true. I haven't seen a case where the
architecture matters. I think the floating-point format is the big
issue; as far as I've seen, even InnoDB stores its data in an
I am not familiar enough with the SPARC architecture to know whether
it uses IEEE standard floating-point format, but if it does, I think
the files should copy fine. And that's assuming there are even any
float columns -- maybe this is all textual or integer data.
I would suggest to the original author to create a trivial example
database with representative data types, then shut it down and copy it
to the new architecture. Start mysqld on the copied files, and see
what happens. That's likely to be better than any of us experts
guessing about it. A 3.5TB copy is not a reasonable test; a 3.5TB
dump and restore should be the absolute *last* resort.
On Fri, Feb 13, 2009 at 5:04 PM, Walter Heck <lists@stripped> wrote:
> It actually depends on your table types. With MyISAM it is no problem,
> but with InnoDB you are looking at a dump-and-restore..
> OlinData: Professional services for MySQL
> Support * Consulting * Administration
> On Fri, Feb 13, 2009 at 6:23 PM, Kurt Cypher <kurt.cypher@stripped> wrote:
>> On Feb 13, 2009, at 11:41 AM, Aaron Blew wrote:
>>> I've currently got a project to migrate a LARGE (3.5TB) MySQL data set
>>> a Sun SPARC machine to a Sun x86 machine, both running Solaris 10 (though
>>> obviously one is x86 and the other is SPARC). Is it possible to simply
>>> the data files from one host to the other or is a full mysqldump/import
>>> necessary to preserve data integrity?
>> I have done straight data directory copy from server to server before
>> (granted they were both SPARC machines) and had no problem. Off-hand, I
>> can't think of any reason why it wouldn't work between SPARC & x86, both
>> running the same Solaris version, especially if they're both running the
>> same version of mySQL.
>> I would suggest doing a test copy, if possible to see what happens.
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
Baron Schwartz, Director of Consulting, Percona Inc.
Our Blog: http://www.mysqlperformanceblog.com/
Our Services: http://www.percona.com/services.html