Kbase P4441: How to change Progress installation from one machine to anot
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/25/2003 |
|
Status: Unverified
GOAL:
How to change Progress installation from one machine to another
GOAL:
Swapping Progress environment to new machine
GOAL:
Migrating Progress to another machine
GOAL:
Considerations when migrating Progress to another server
FIX:
Provided that the Directory structures and O/S levels are equal between both machines:
1) copy the complete Progress\dlc #including all subfolders and the "working directory"
2) copy the database over #maintaining the same directory structure
This action could either be undertaken by litterally "copying" the database(s) over (if user downtime is feasable), or
to read back the last backup and roll the ai- files forward.
3) Make sure that the PERMISSIONS, OWNER and GROUP are the same as the original, once it has been restored. #this is where potential issues with the kind of activity that you are undertaking usually go awry. For example:
find $DLC -exec chown root {} \;
chmod 4755 $DLC/bin/_dbutil
chmod 4755 $DLC/bin/_mprosrv
chmod 4755 $DLC/bin/_mprshut
chmod 4755 $DLC/bin/_orasrv
chmod 4755 $DLC/bin/_proapsv
chmod 4755 $DLC/bin/_probrkr
chmod 4755 $DLC/bin/_probuild
chmod 4755 $DLC/bin/_progres
chmod 4755 $DLC/bin/_prooibk
chmod 4755 $DLC/bin/_prooidv
chmod 4755 $DLC/bin/_proutil
chmod 4755 $DLC/bin/_rfutil
chmod 4755 $DLC/bin/_sqlsrv2
chmod 4755 $DLC/bin/prolib
chmod 4755 $DLC/bin/sqlcpp
... etc.
4) Tunable kernel settings will have to be considered on the new server. Refer to the OS documentation and use the previous settings on the 'old' machine as a baseline.