Thanks Keith :-)  Last question, do you think it's ok for me to do a sqldump on 
4.1.22 at say 3 am on sun, then import to 5.1.48 at 4 am and then just edit 
etc/hosts and have the web servers now point to 5.1?

This should work without any problems right?  Plus I have the original 4.x in 
case I break something during the dump and can revert within mins back to the 
4.x version?

Still don't know why I should do a mysql dump from 4.1.X to 5.0.x and then 
upgrade 5.0.x to 5.1.48 esp. if I am doing nothing more than a mysql dump and 
not upgrading in place ;-)

TIA...

Nunzio




________________________________
From: Keith Murphy <bmur...@paragon-cs.com>
To: Nunzio Daveri <nunziodav...@yahoo.com>
Cc: mysql@lists.mysql.com
Sent: Mon, August 16, 2010 11:47:39 AM
Subject: Re: Is upgrading from 4.X to 5.X really that easy?

I would really recommend that you have a second server set up running MySQL 
5.0.  Otherwise the complexity is going to drive you crazy. Either way you are 
going to have to get a backup of the master (4.1) server somehow. I am curious. 
If you can't take an hour or so take a mysqldump of the server how are you 
running backups now? And if you aren't runninng backups you need to run to your 
boss and say "It's REALLY REALLY REALLY critical that we start making backups." 
And do it beginning tonight at the latest.

Otherwise something is going to happen, the data is going to be lost and you 
are 
best case going to look REALLY REALLY bad. 


I wouldn't recommend going straight to 5.1. The upgrade from 5.0 to 5.1 is 
fairly trivial and doesn't require a dump/reload but I would still take the 
time 
to stop at 5.0 and make sure everything is working before moving on to 5.1.

keith




On Mon, Aug 16, 2010 at 12:42 PM, Nunzio Daveri <nunziodav...@yahoo.com> wrote:

Thanks William and Keith.  So how to have min down time since this is a stand
>alone mysql 4.1.22 box?  Are you saying install 5.X on the same box (port 
3307),
>then replicate the data as it comes into 4.x to 5.x and when it is all sync'd 
up
>then turn 4.x off, remove it and have 5.x responding on port 3306?
>
>Mysqldump takes over an hour and then prob more to reimport?  I only have a 30 
-
>45 min window.
>
>If I do a straight dump from 4.1.22 with all options why stop at 5.0 and not
>just go straight to 5.1.48?  This is a single box, no replication or clustering
>going on ;-)  Also all the data is in MyISAM, zero InnoDB :-)
>
>Thanks again for the advice :-)
>
>
>Nunzio
>
>
>
>
>________________________________
>From: Keith Murphy <bmur...@paragon-cs.com>
>To: Nunzio Daveri <nunziodav...@yahoo.com>
>Sent: Mon, August 16, 2010 9:42:07 AM
>Subject: Re: Is upgrading from 4.X to 5.X really that easy?
>
>
>No, that would be a huge mistake. There are subtle differences between the two
>versions. For example, check up on DECIMAL. Also, 5.0 and 5.1 have numerous new
>reserved words.
>
>
>You need to think about this carefully before you do it. I know there is binary
>incompatability between Innodb tables (vers 4.X - 5.X). I will take you word
>that what you are saying would actually work, but I still wouldn't recommend 
it.
>
>
>Just my 2 cents...
>
>keith
>
>
>On Mon, Aug 16, 2010 at 10:26 AM, Nunzio Daveri <nunziodav...@yahoo.com> wrote:
>
>Hi all, I was reading a few of the notes on this forum from a few months back
>>and it seems that ONE WAY of upgrading from 4.x to 5.X with MyISAM only
>>databases is to copy the actual data folder from the 4.X version to a temp
>>place, then remove 4.x from the OS, install 5.X and then just put the 4.X data
>>folder into the 5.X folder???
>>
>>
>>Is it really that simple?  Has anyone done this and can verify this please?  I
>>am thinking I am missing a few commands you have to run at least??? My 
database
>>is pretty small is an only 1.8GB so I am thinking this is a walk in the park
>:-)
>>
>>Please advise...
>>
>>And as always... TIA...
>>
>>Nunzio
>>
>>
>>
>
>
>--
>Chief Training Officer
>Paragon Consulting Services
>850-637-3877
>
>
>
>     


-- 
Chief Training Officer
Paragon Consulting Services
850-637-3877



      

Reply via email to