Install 5.x against copied MySQL DB possible?

[gpatus]

I have SugarCRM 4.5.4h with MySQL 4.4.10a all works ok on openSUSE 9.x. I have setup a new server with the same hardware but a newer distro of openSUSE 10.3. It has MySQL 5.0.45 as of now. I have run all the software updates from the online repositories.

The next step is to install the latest SugarCRM download. I do not know the history of MySQL enough to know if I could just copy the MySQL directory to the new directory before the Sugar install. I'm sure it will not be that easy.

I would like to know how to do this transfer if possible.

George.

[Angel]

You'll need to perform a database repair using a MySQL utility such as phpMyAdmin or SQLyog.

Give this article a look as well: http://dev.mysql.com/doc/refman/5.0/en/upgrade.html

I am assuming you've made about 10 backups in advance too.

BTW, that would only address the point on the MySQL database, not the point about you moving from Sugar 4.5 to Sugar 5.0. I would try to upgrade the system to 5.0 once it is operational on the new server.

[gpatus]

10 is a good number. I'm going to have to take some time to learn how to do a MySQL for bare metal recovery. Second a data set recovery would be a good idea too. I'll visit the MySQL site for the details. I have to say that I'm installing this onto a new server to the original is being left in working condition.

Now based on your response it sounded like you were suggesting setting up a blank new 4.5.1h on the new server using the new MySQL The next step would be to copy the old MySQL 4.4.10a DB to the new server in place of the new blank MySQL 5.0.45 just created by the 4.5.1h install. Then run a MySQL repair. This would result in a working 4.5.1h with the old DB updated.

Then when I confirm the 4.5.1h is working I should run the 5.x upgrade for a final result.

I'm not so sure about this procedure as I've read some Help items about problems doing upgrades from 4.5.1 to 5.x. I was hoping that I could do the 5.x install and then copy the 4.5.1h DB over the 5.x. The question becomes what is the upgrade routines for coverting 4.5.1h to a 5.x DB?

George.

[gpatus]

Angel,

You'll need to perform a database repair using a MySQL utility such as phpMyAdmin or SQLyog.

Give this article a look as well: http://dev.mysql.com/doc/refman/5.0/en/upgrade.html

I am assuming you've made about 10 backups in advance too.

BTW, that would only address the point on the MySQL database, not the point about you moving from Sugar 4.5 to Sugar 5.0. I would try to upgrade the system to 5.0 once it is operational on the new server.

I have read the article you referenced in your reply. Those articles discuss changes from 4.1 to 5.0 to 5.1. My reading suggests to me there are incompatible changes to the underlying MySQL table structures. MySQL promises not to make large changes but some have occured.

I've come to understand there have been changes to SugarCRM's table layouts between versions. That implies the need to export the tables as a series of so called dump files that can build tables. Once a new versions of SugarCRM and MySQL are installed the dump files from the old MySQL version are used, imported, to build the tables for the new version.

Given that information I left thinking about what happens when I install SugarCRM version 4.5.1h on the new server using the latest MySQL 5.0.45. How will the table structure be transferred or will it work with the newer MySQL?


George.

[Angel]

Angel,
Given that information I left thinking about what happens when I install SugarCRM version 4.5.1h on the new server using the latest MySQL 5.0.45. How will the table structure be transferred or will it work with the newer MySQL?


George.

Perhaps this will help answer some of your questions...

If I had to do this, I would first try this approach:

1. Install Sugar 4.5.1 on MySQL 5.x on new server and verify that it is operating normally.
2. Copy the old Sugar DB from the old server over to the new MySQL server.
3. Run a database repair via a MySQL admin utility on the new server for the old Sugar DB.
4. Access Sugar 4.5.1 on new server to make sure things are still operational and run repair operations through Sugar.
5. Upgrade Sugar to 5.0

It is possible that step 3 would require some additional work beyond running the repair, but this would be my initial series of steps.

[gpatus]

Perhaps this will help answer some of your questions...

If I had to do this, I would first try this approach:

1. Install Sugar 4.5.1 on MySQL 5.x on new server and verify that it is operating normally.
2. Copy the old Sugar DB from the old server over to the new MySQL server.
3. Run a database repair via a MySQL admin utility on the new server for the old Sugar DB.
4. Access Sugar 4.5.1 on new server to make sure things are still operational and run repair operations through Sugar.
5. Upgrade Sugar to 5.0

It is possible that step 3 would require some additional work beyond running the repair, but this would be my initial series of steps.

I'll do the steps and report my results. Other items will pull me away from this new server setup for a few days. I will write a response when I know the outcome.

George.