SEO

I would like to move from 32-bit to 64-bit MySQL within the next year.
Unfortunately, there is not a lot of documentation on migration or anything
else regarding 64bit MySQL.

My current setup consists of one master and two slaves (all using 32bit and
MySQL 5.0). I am looking to add a 64bit slave to the mix.

What is the difference between 32-bit and 64-bit? Is this a good idea? Can
it be done? What would make this go wrong?

Mike wrote:
> I would like to move from 32-bit to 64-bit MySQL within the next year.
> Unfortunately, there is not a lot of documentation on migration or anything
> else regarding 64bit MySQL.
>
> My current setup consists of one master and two slaves (all using 32bit and
> MySQL 5.0). I am looking to add a 64bit slave to the mix.
>
> What is the difference between 32-bit and 64-bit? Is this a good idea? Can
> it be done? What would make this go wrong?
>
>

I have made this migration on multiple servers. It has never been any
trouble. Your biggest gain would probably be the ability to address
more RAM. I would just dump the database from the 32-bit platform and
import it into the 64-bit server.

Keith

--
Keith Murphy


editor: MySQL Magazine
http://www.mysqlzine.net

On Fri, 25 Apr 2008, B. Keith Murphy <bmurphy@paragon-cs.com> wrote:
> I would just dump the database from the 32-bit platform and import it
> into the 64-bit server.

By "dump" do you mean "mysqldump", or some other process?

--
Tim McDaniel, n00b, tmcd@panix.com

On Fri, Apr 25, 2008 at 11:45 AM, Olaf Stein <
olaf.stein@nationwidechildrens.org> wrote:

> As long as you use dumps to restore your databases on the new 64bit system
> (instead of the binary files) you should be fine
>
> Olaf
>

I have so much data that we can't take a mysqldump of our database. The
directory tared is about 18GB. I just use the other method by just copying
over the data directory. Do you think the data will be intact if a just
copy over the data directory?

As long as you use dumps to restore your databases on the new 64bit system
(instead of the binary files) you should be fine

Olaf


On 4/25/08 11:23 AM, "Mike" <lunarblu@gmail.com> wrote:

> I would like to move from 32-bit to 64-bit MySQL within the next year.
> Unfortunately, there is not a lot of documentation on migration or anything
> else regarding 64bit MySQL.
>
> My current setup consists of one master and two slaves (all using 32bit and
> MySQL 5.0). I am looking to add a 64bit slave to the mix.
>
> What is the difference between 32-bit and 64-bit? Is this a good idea? Can
> it be done? What would make this go wrong?

----------------------------------------- Confidentiality Notice:
The following mail message, including any attachments, is for the
sole use of the intended recipient(s) and may contain confidential
and privileged information. The recipient is responsible to
maintain the confidentiality of this information and to use the
information only for authorized purposes. If you are not the
intended recipient (or authorized to receive information for the
intended recipient), you are hereby notified that any review, use,
disclosure, distribution, copying, printing, or action taken in
reliance on the contents of this e-mail is strictly prohibited. If
you have received this communication in error, please notify us
immediately by reply e-mail and destroy all copies of the original
message. Thank you.

Probably not

AFAIK it should work in theory if you have no floating point columns but I
would not try it.
Why cant you take a dump, you can do it table by table, you will have some
downtime though.

One option might be to use a 64bit slave and make that the master and then
add more 64 slaves.


On 4/25/08 11:57 AM, "Mike" <lunarblu@gmail.com> wrote:

> On Fri, Apr 25, 2008 at 11:45 AM, Olaf Stein
> <olaf.stein@nationwidechildrens.org> wrote:
>> As long as you use dumps to restore your databases on the new 64bit system
>> (instead of the binary files) you should be fine
>>
>> Olaf
>
> I have so much data that we can't take a mysqldump of our database. The
> directory tared is about 18GB. I just use the other method by just copying
> over the data directory. Do you think the data will be intact if a just copy
> over the data directory?
>



----------------------------------------- Confidentiality Notice:
The following mail message, including any attachments, is for the
sole use of the intended recipient(s) and may contain confidential
and privileged information. The recipient is responsible to
maintain the confidentiality of this information and to use the
information only for authorized purposes. If you are not the
intended recipient (or authorized to receive information for the
intended recipient), you are hereby notified that any review, use,
disclosure, distribution, copying, printing, or action taken in
reliance on the contents of this e-mail is strictly prohibited. If
you have received this communication in error, please notify us
immediately by reply e-mail and destroy all copies of the original
message. Thank you.

Olaf Stein wrote:
> Probably not
>
> AFAIK it should work in theory if you have no floating point columns but I
> would not try it.
> Why cant you take a dump, you can do it table by table, you will have some
> downtime though.
>
> One option might be to use a 64bit slave and make that the master and then
> add more 64 slaves.
>
>
> On 4/25/08 11:57 AM, "Mike" <lunarblu@gmail.com> wrote:
>
>
>> On Fri, Apr 25, 2008 at 11:45 AM, Olaf Stein
>> <olaf.stein@nationwidechildrens.org> wrote:
>>
>>> As long as you use dumps to restore your databases on the new 64bit system
>>> (instead of the binary files) you should be fine
>>>
>>> Olaf
>>>
>> I have so much data that we can't take a mysqldump of our database. The
>> directory tared is about 18GB. I just use the other method by just copying
>> over the data directory. Do you think the data will be intact if a just copy
>> over the data directory?
>>
>>
>
>
Seriously, 18 gb isn't too big to do a mysqldump. And I really wouldn't
advise you trying to do a binary copy. You are just asking for trouble.
Plan ahead and you can do this on a slave without any problem, import
the data on the new server and sync it back up without any problems.

--
Keith Murphy


editor: MySQL Magazine
http://www.mysqlzine.net

That what I want to do, but I'm not sure if the data will propagate right.
Because of lack of documentation for 64bit.

On Fri, Apr 25, 2008 at 12:03 PM, Olaf Stein <
olaf.stein@nationwidechildrens.org> wrote:

> Probably not
>
> AFAIK it should work in theory if you have no floating point columns but I
> would not try it.
> Why cant you take a dump, you can do it table by table, you will have some
> downtime though.
>
> One option might be to use a 64bit slave and make that the master and then
> add more 64 slaves.
>
>
>
> On 4/25/08 11:57 AM, "Mike" <lunarblu@gmail.com> wrote:
>
> On Fri, Apr 25, 2008 at 11:45 AM, Olaf Stein <
> olaf.stein@nationwidechildrens.org> wrote:
>
> As long as you use dumps to restore your databases on the new 64bit system
> (instead of the binary files) you should be fine
>
> Olaf
>
>
> I have so much data that we can't take a mysqldump of our database. The
> directory tared is about 18GB. I just use the other method by just copying
> over the data directory. Do you think the data will be intact if a just
> copy over the data directory?
>
>

Every statement should be executed on the slave from the masters binary log
so in my opinion you should be ok


On 4/25/08 12:20 PM, "Mike" <lunarblu@gmail.com> wrote:

> That what I want to do, but I'm not sure if the data will propagate right.
> Because of lack of documentation for 64bit.
>
> On Fri, Apr 25, 2008 at 12:03 PM, Olaf Stein
> <olaf.stein@nationwidechildrens.org> wrote:
>> Probably not
>>
>> AFAIK it should work in theory if you have no floating point columns but I
>> would not try it.
>> Why cant you take a dump, you can do it table by table, you will have some
>> downtime though.
>>
>> One option might be to use a 64bit slave and make that the master and then
>> add more 64 slaves.
>>
>>
>>
>> On 4/25/08 11:57 AM, "Mike" <lunarblu@gmail.com> wrote:
>>
>>> On Fri, Apr 25, 2008 at 11:45 AM, Olaf Stein
>>> <olaf.stein@nationwidechildrens.org> wrote:
>>>> As long as you use dumps to restore your databases on the new 64bit system
>>>> (instead of the binary files) you should be fine
>>>>
>>>> Olaf
>>>
>>> I have so much data that we can't take a mysqldump of our database. The
>>> directory tared is about 18GB. I just use the other method by just copying
>>> over the data directory. Do you think the data will be intact if a just
>>> copy over the data directory?
>>>
>
>





----------------------------------------- Confidentiality Notice:
The following mail message, including any attachments, is for the
sole use of the intended recipient(s) and may contain confidential
and privileged information. The recipient is responsible to
maintain the confidentiality of this information and to use the
information only for authorized purposes. If you are not the
intended recipient (or authorized to receive information for the
intended recipient), you are hereby notified that any review, use,
disclosure, distribution, copying, printing, or action taken in
reliance on the contents of this e-mail is strictly prohibited. If
you have received this communication in error, please notify us
immediately by reply e-mail and destroy all copies of the original
message. Thank you.

Mike wrote:
>
> I have so much data that we can't take a mysqldump of our database. The
> directory tared is about 18GB.

Worst-case expansion for SQL data from binary to text format is about
5:1, which applies mainly to numeric data, not text. That's only 90 GB;
I carry a bigger hard drive in my backpack, which I use for moving files
between machines. Heck, my iPod holds more than that.

You don't even have to store a second copy of the data. You can do
something like pipe the mysqldump through a tool like nc (netcat) from
the old machine to the new. With a decent GigE network connection
between the two, the transfer should complete in about an hour. Add in
a little data compression and you can probably cut that in half.