I have a baan IVc4 server running on winnt 4 and I want to setup a new wndows 2003 server with SQL 2000. Can ne1 give me suggestions on how to accomplish this with minimal downtime? Or is there any documentation that describes this process.

tia

Hi,
To have an uneventfull migration, i would suggest installing a fresh copy of Baan on the new server (Win2k/SQL2k) and then restoring the sequential dump of your production company. Prior to doing this (restoring), you would have to make sure you have the correct porting set (7.1c.02 or above, i guess) installed on the new server. The downtime here would be just the time taken to restore and re-organize your production company data.

hth
sk

If the porting set on the old server is less than 7.1c.02 or above should i still put the lastest porting set? Also what about the Baan folder should i move that over? Can you give me steps on doing a sequential dump properly?

thank you kindly for the help

I made a mistake in my earlier post as i was referring to porting set 6.1c.07.02 and not 7.1c.. So kindly ignore that..

In order to install Baan on Windows 2k or 2k3, you need 6.1c.07.02 or above. Anything below than this only works on Windows NT.

I wouldnt recommend copying over the BSE folder as these are two different OS's (and a major leap at that NT->Win2k3) and so the best option would be is to install a fresh copy of Baan on your Win2k3. Secondly, you would need to maintain the same service pack level as of your old server. With certain service packs you would need to even install a higher porting set, so watch out for that..

You want to know how to create a dump or how to restore one?

sk

So these are the steps i should take:
1. Install Windows 2003 Server Standard Edition
2. Install latest Service Packs and Updates for WIndows 2003
3. Install SQL 2000 and Latest Service Pack
4. Install BaaN 4c4 using the latest Master CD.
5. Update the Porting Set to 6.1c.07.02
6. Stop Users from entering data on the Old Server.
**7. Copy the old Baan directory over to the New server in the same path and overwrite the new one. (I think the previous person install baan on the C: Drive which i would like to move to a different partition if possible)
8. Create a Sequential Dump ( of what) and move that file to the new server and restore it. (This is what i dont know how to do.)
9. Call BaaN and relicense the new server.

Questions:

What about the customizations they have. Will they be moved when i copy the baan directory over?

If i dont copy the baan directory over then wont i loose all the custom reports and other stuff created after baan was installed?

Is there anything im missing?

First and foremost, copying the bse folder wont be such a good idea. For your customized reports and forms, you could export these objects using ttiex1280m000 session by selecting the appropriate VRC package your customized objects belongs to. You could also use the service of ttcon61export session to move all your user, user permissions, currency and device data to the new server (at the new server you got to use ttcon61import to import). The only issue with this session is that you got to install a solution which will update this session with range facility which wasnt there earlier. I am not sure of the solution number but you could get it from Infor or baanboard by typing ttcon61export...

Secondly, when you install Baan on Windows 2003 with the latest Baan Master Cd, it will be having porting set 6.1c.07.13 or higher.

To restore the sequential dump follow these procedures
1) Open session Create Table from Sequential Dump {ttaad4227m000}
2) Enable checkbox "Create Table for Different Company" and select the company.
3) Enable the "Append if table exists", "Overwrite duplicate records", "Disable Domain Constraints" and "Ignore Referential Integrity Constraints"
4) Enter the path where your sequential dump is and then give an appropriate name to your error log and hit continue.
5) After the sequential dump is over, you got to run Re-organize tables for the company you imported in the steps above

sk
P.S: Copying the BSE folder may or may not work but i based my suggestion on the fact that if problems do crop up later then you would have a handfull..

I always install my new Baan/Oracle servers by copying bse directory. By this I am sure that I have all my solutions and customisations installed.

Can't help you though with the SQL-server since I am not familiar with it.

The way I do it:
- have a new server with os installed ready
- install oracle db software
- turn database off, copy db files and create a new instance on the new server using the copied database files
- copy bse folder
- install portingset (in order to have correct setup in registry)

Since you have to make sure that the procedure works you need to perform a test migration. If your users confirm that everything works fine than you can perform the real migration.

Regards,
Han

how do you guys feel about setting up a windows 2003 server with all the bells and whistles and then installing VMware Server and making a Virtual disk image of the old server and running Baan on the VMware Server. Is this a bad idea. Also i did notice that all the new server are 64 bit is this going to be an issue with BaaN 4c4

Not too familiar with VMWare and so i cant comment on that. As far as the 64bit is concerned there shouldnt be any problem. You could install 32bit OS and DB on it. If on the other hand you install 64 bit version of OS and Db then you should have porting set 6.1c.07.13 or later installed (info courtesy Infor)..

sk

how do you guys feel about setting up a windows 2003 server with all the bells and whistles and then installing VMware Server and making a Virtual disk image of the old server and running Baan on the VMware Server. Is this a bad idea. Also i did notice that all the new server are 64 bit is this going to be an issue with BaaN 4c4


i have using vmware guest for my Baan Server so far very good.

i have make a virtual image from physical to virtual so i do not need to reinstall the Baan Server.

My baan server now still running Win NT 4 as vmware guest in W2K3 Vmware Server host.