I'm by no means an expert on this, but some things you might want to
An alternative method to not impact the disk space on the 32-bit system:
If you have connectivity between the 32-bit and 64-bit systems is to use
mysqldump on the 64-bit system and specify the 32-bit host using the -h
This could take quite a while, depending on the throughput you can get
across your network. (It's also possible that you may not have adequate
disk space on the new system.) However, it would effective at preserving
It would be worthwhile testing this on a small subset of your data, with
and without the -C switch. It might also be possible to pipe the mysqldump
output to gzip so that the size of your resultant disk file(s) would be
At 11:20 PM 10/4/2004, alex ye wrote:
>But our data is very big(about 400G), server don't have enough disk space
>and it will take long time to finish the dump.
> It may cause problem to floats if just copy data files to a 64 bit system?
>Eric Bergen <eric.bergen@stripped> wrote:
>The safest thing you can do to protect floats and the like is to use
>mysqldump to dump them to a .sql on the 32 bit system then import them
>again on the 64 bit system.
>On Mon, 4 Oct 2004 16:38:13 -0700 (PDT), alex ye wrote:
> > Does anyone has the experience on migrating mysql server from 32bit
> sysem to a 64bit system?
> > Can data files(from 32bit system) be readed properly by mysql server
> after copy to a 64bit system?
> > Thank you in advance!
> > --Alex
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
>MySQL General Mailing List
>For list archives: http://lists.mysql.com/mysql
>To unsubscribe: http://lists.mysql.com/mysql?unsub=1
>Do you Yahoo!?
>Yahoo! Mail Address AutoComplete - You start. We finish.