Rebuilding an APS server procedure? 1

[OldSkoolSkater]

Mornin'

I have to move my existing Info 7.5 system onto another server. The new server is going to totally replace the old one, so here is what I propose to do:
1.Copy the SI input & output folders on the existing server to a network share, and shut the server down.
2.Build the new server with the hostname and ip address of the old server. Install the full Info 7.5 product (APS, Report server, Baan drivers, notes drivers, Seagate analysis, etc) and add the ODBC sources that the existing server had.
3.Paste the input & output folders from my network into the relevant location on the new server, and make sure that Info Config Manager points to these areas.
4.Reboot the server and cross fingers. I should now be able to open the Info desktop on any client machine and find all the reports listed in the original folder locations. Folder and report permissions should not have been altered in any way.
Could anybody clarify what I propose to do is actually correct before I go and destroy my Info system!!!
Also, is there a way to copy over the groups and roles for users that I have created on the existing server?

Cheers

Steve

 

[rhinok]

All of this sounds fairly good, however, I have a couple of suggestions or tips:

1) Make sure that your new ODBC drivers use the exact same case as they did on the old machine or your reports won't work.

2) If you use Oracle, don't forget to recreate your TNS Names

3) Since Info will create a new System Database by default, you will need to point your APS to the old System Database via the Info Configuration Manager|APS Tab. If you still use the Access Database then I would back it up and copy it to the appropriate directory on your new server. By pointing to the old Info System Databse, you will retain all users, groups, permissions and report schedules.

Hope this helps! Good luck.

 

[OldSkoolSkater]

Rhinok

Thanks for your reply. Didn't know about the case problem with ODBC for thanks for that tip.
I currently use the cinfo.mdb on the APS, so if I install Info on the new server and let it create the default database, I could then overwrite the default cinfo.mdb file with my existing one right?
Another question:
I also have an SQL server which could be used to store Info information. What exactly would I move off the APS server and onto the SQL server, and what benefits would I get out of it if any? Or am I just complicating matters?

Cheers

Steve

 

[rhinok]

I would wait until after the move before attempting to migrate from cinfo.mdb to SQL Server. Generally speaking, you should see better performance if you use SQL Server over MS Access.

I'd recommend reading the following Crystal Decisions articles:

http://support.crystaldecisions.com/library/kbase/articles/c2008009.asp

http://support.crystaldecisions.com/communityCS/TechnicalPapers/aps_database_migration.pdf

 

[OldSkoolSkater]

Having read the migration pdf I checked the size of cinfo.mdb and found it to be 75Mb!
I was told by a colleague however that I could compact the database to reduce the size. I took a copy of the file and compacted it. New file size = 3MB!
Is it wise to compact the mdb and leave it as an access d/b?, or would it be better if I left the mdb un-compacted and moved it to SQL?

 

[rhinok]

When you compact the Access database you're basically clearing up file space that is no longer used. The mdb isn't compacted in the same manner that a file would be zipped, for example. I personally haven't had any problems using the Access database (in a small Info environment), however, I'd recommend maintaining it in the following manner if you intend to keep using it:

1) Shutting down the APS
2) Making a backup copy of the cinfo.mdb (cinfo_011217.mdb, for example)
3) Compacting and even repairing the database
4) Starting your APS back up.

This should probably be done on a monthly basis if you want to keep the database as lean as possible.

 

[OldSkoolSkater]

Thanks for the info, my new server is coming in today so shall be building it up soon!