aanya247
asked on
AIX to Linux
We have various AIX images on which we have Databases and Applications running and we are planning to convert them into RHEL. Is there any special migration process I have to follow ..?
As most of the data is already on the SAN, We will be installing new DB's and new Applications on RHEL and are planning to connect our data..
Can someone help me with the procedure or a document..???
As most of the data is already on the SAN, We will be installing new DB's and new Applications on RHEL and are planning to connect our data..
Can someone help me with the procedure or a document..???
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You need to create architecture-neutral database backup and restore it in new place (sure you need same or better DB running there)
For applications? Depends on application, say IHS can move to Apache, java webservers are usually same on both platforms, whatever was compiled in-houdse needs to be recompiled... etc etc.
For applications? Depends on application, say IHS can move to Apache, java webservers are usually same on both platforms, whatever was compiled in-houdse needs to be recompiled... etc etc.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
sure you cannot blindly copy the scripts - you need to examine all filesystem paths hardcoded inside :)
smit -> system-config-[tab]-[tab]
lvm -> lvm (only command line or GUI, no TUI like smitty) yes online expansions and reductions
ODM -> LSB
patch reversal -> yum downgrade (works well with RHEL, not so good with CentOS)
mksysb -> Nothing (but it can keep unlimited number of bootable kernels intact)
smit -> system-config-[tab]-[tab]
lvm -> lvm (only command line or GUI, no TUI like smitty) yes online expansions and reductions
ODM -> LSB
patch reversal -> yum downgrade (works well with RHEL, not so good with CentOS)
mksysb -> Nothing (but it can keep unlimited number of bootable kernels intact)
In that case, you have a big migration project to undertake, there are a lot of differences in system calls , compilers and options between AIX and RHEL that need to be accounted for.
it starts with assessing what is running andthen disbanding piece by piece...
Say for DB2+Websphere migration to Linux even IBM will help you...
Say for DB2+Websphere migration to Linux even IBM will help you...
>>...AIX images ....planning to convert them into RHEL<<
Red Hat doesn't have any documentation or article for migration between non-RHEL system to RHEL and it is not recommended. Below are the recommended steps to migrate NON-RHEL OS to RHEL:
1) Take the full backup of the required data from AIX system.
2) Do the fresh installation of RHEL OS
3) Restore the data copied from the AIX system to your new RHEL system.
4) If any third parity application running on the AIX system then Red Hat will suggest you to contact the application vendor prior to migration regarding support-ability of the application in RHEL.
Be aware; any issues on the migrated RHEL will be unsupported.
Red Hat doesn't have any documentation or article for migration between non-RHEL system to RHEL and it is not recommended. Below are the recommended steps to migrate NON-RHEL OS to RHEL:
1) Take the full backup of the required data from AIX system.
2) Do the fresh installation of RHEL OS
3) Restore the data copied from the AIX system to your new RHEL system.
4) If any third parity application running on the AIX system then Red Hat will suggest you to contact the application vendor prior to migration regarding support-ability of the application in RHEL.
Be aware; any issues on the migrated RHEL will be unsupported.
Unsupported? Are you in IBM sales? Theyalways shout you have wrong data and everything is unsupported... Redhat at least asks if you have backup...
Red Hat do not support:
-Modified RPMs
-Third-party software/drivers and uncertified hardware/hypervisors
-Community projects upon which enterprise releases are based
-Code development
-System and network design
-Implementation and development of security rules and policies
-Red Hat Extras/Supplementary channel
-Optional repository/channel
-Technology preview features
-Packages included to satisfy dependencies when deployed as standalone items
https://access.redhat.com/site/support/offerings/production/soc
https://access.redhat.com/site/articles/1067
https://access.redhat.com/site/support/offerings/production/scope_moredetail/
-Modified RPMs
-Third-party software/drivers and uncertified hardware/hypervisors
-Community projects upon which enterprise releases are based
-Code development
-System and network design
-Implementation and development of security rules and policies
-Red Hat Extras/Supplementary channel
-Optional repository/channel
-Technology preview features
-Packages included to satisfy dependencies when deployed as standalone items
https://access.redhat.com/site/support/offerings/production/soc
https://access.redhat.com/site/articles/1067
https://access.redhat.com/site/support/offerings/production/scope_moredetail/
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Got "supported" by both:
IBM may send you a heavy bill of services even they fix their bugs under warranty or support contract... (if the fix involved programing)
In sam case RH might announce that particular product feature was included by accident so it is unsupported.
IBM may send you a heavy bill of services even they fix their bugs under warranty or support contract... (if the fix involved programing)
In sam case RH might announce that particular product feature was included by accident so it is unsupported.
That is not the case. You need to contact every software vendor and ask them individually what the process is for their app.