Moving app to new server

kklosson

I have to move my app to a new server, basically recreate the whole setup. I've run into some problems:

When porting my database over (MYSQL), the import breaks my AwareIM license - Support has helped me with that.
I used a backup tool called Autobackup for MYSQL and got some errors on the restore, then I backed up with Navicat and restored, and got some errors there too. My data appears intact but I'm not comfortable. Having never done this, are there any deep secrets to exporting from one server and importing to another?
When I launch a MS Word document, I get an error that it can't find something. I note that my old server has a lot of stuff in the DocTemplates folder. Do I need to move that folder? If so, I don't understand why.
Many of my icons have either scrammed or changed to something else. What can cause this since my bsv is identical?

Any help on these please.

pbrad

Hi,
With respect to your asset path issues, try copying over your whole AwareIM folder from your old server to your new server. With respect to your database migration concerns, the biggest issue is the id numbers for references. Just take your time and take it one step at a time. What exact issues are you having with it?

Pete

kklosson

Thanks Pete. I'm not sure what you mean re: the id numbers. My current problem is that I can logon (so it's reading the database), but no data will display anywhere.

It would be helpful to me to do a number of database portages from my old server to the new one, but doing so wipes my Aware license, so I'm a bit crippled. For the life of my I don't know why the AwareIM license is tied to my application db.

rocketman

Hi,

Consider

1) install AwareIm Cleanly from scratch on your new server, (note - if BasDb and Bastdbtest exist in your MySQL because of a previous install - delete them first)

2) Import your latest BSV, then publish it. This will create all the necessary (empty) tables.

3) restore all your MysQL tables for the bsv - these are the ones named YourBSV_YourTableName PLUS Bas_IDGEN. DON'T restore anyhing else

If you restore the ENTIRE BasDB, you will effecively be restoring the old serial number and AwareIM won' run.

With regard to Bas_idgen, This table has one row containing the last unique id generated by AwareIM (every new record in every BO has a unique ID generated by Aware, so If you don't re-import the Bas_idgen table, the count will be zero so when you enter a new record, you'll get a duplicate key error because 1 (the number AWare will try to assign) will already exist in your restored data

Doing a clean insall should ensure all your icons are in the right place

Not sure about the MS Word thing

The serial number is in Bas_System (I think)

rocketman

Ps ... Never used Navicat. I use MysqlAdmin which allows me to analyse the backup and selectively restore individual tables.

Doing them one at a time is a pain in the rear but will help in finding the source of the error(s)

kklosson

RMan,

This information was gold to me. Helps me a lot. I'm in a place now where, even knowing this, my database imports are not going well, and I'm getting some errors. I did not delete the whole app database as you suggested since I still need the Bas_IDGEN table for the license.

I'm using a tool called Autobackup for MYSQL. I don't expect you to know it but I found that even if I deleted a whole table, it did not restore it. But I don't think this is a tool problem.

Considering that I have two identical installs and all I need to do is move the data from one machine to the other, while keeping the AwareIM license alive, can you recommend a path?

My experience with MYSQL is pretty low, but I'm learning.
Thanks!

rocketman

In haste - will write more fully later,

If it's a new server package, Are you sure the MySQL versions are the same. A new box might be 5.5.

If your old box is 5.1.something, you might need to upgrade your old Mysql, then backup the database, then try the restore again.

Support should have given you a new key for your new server, so doing a clean install shouldn't be a problem as long as you remember to run the prodkey.bat file from the AwareIM/Bin directory. Then do the BSV import/publish bit. At least then you'll know there is nothing wrong with the AwareIM installation - It's really a question of elimination at this stage.

Will be back in a couple of hours

kklosson

You're probably onto something that the MYSQL versions may be different.

kklosson

I am moving from a 5.0 install to a 5.1 install. Do you think I need to upgrade the 5.0 install first, then migrate? Reading the MYSQL docs makes the upgrade sound pretty rough especially from 4.x.

ACDC

When restoring to a MySql DB, images in the database can sometimes create errors on the restore. To prevent this, include the following in your my.ini file:

[mysqld]
max_allowed_packet=20m

kklosson

That actually helped but I still have two tables that post errors. Simple tables, the biggest one has 1600 records, so there's no heavy lift here.

rocketman

Nice tip ACDC. I'm about to jump through this particular hurdle myself.

KKlosson, in your two remaining tables - are there any Images or Word Docs stored in the actual tables. There are a number of posts on the forum regarding spurrious data in such docs causing restore problems

MySQL 5 to 5.1 shouldn't be an issue, but when you're done you might want to consider going to 5.5 which - in build 1427 AwareIM now supports

kklosson

I think I'm out of the woods on this. Thanks for your help. Turned out my best bet was to just make a SQL dump and then port it in. I had one error with packet too large, and maybe I could have overcome that by increasing the packet size more, but I new what the item was and it was not significant.

How hard is it to update to 5.5? Is it just install and go, or are there data manipulations to be performed?

Thanks again

rocketman

I'll let you know when I've done it LoL.

Some time over this weekend