We are moving a major application off one box which is AIX 5.2 to another box which is AIX 5.3. I was hoping someone else may have done this and can give a list of configuration files that I may need to move to the new bax along with the application....configuration files that relate to printers, users/passwds, hosts etc. We would like this move to be seamless to the users but do not want to copy over the 5.2 environment to the 5.3 environment and them update the OS.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Migrating - configuration files to preserve
- Thread starter teakandme
- Start date
I think I'd use mksysb migration for such a job.
Verify that your applications run on AIX 5.3. Also, verify that your applications are binary-compatible with AIX 5.3. If your system is an application server, verify that there are no licensing issues.
Verify that your hardware microcode is up-to-date.
If the source system is available, run the pre-migration script on it. Correct any other problems as recommended by the script.
Verify that your applications run on AIX 5.3. Also, verify that your applications are binary-compatible with AIX 5.3. If your system is an application server, verify that there are no licensing issues.
Verify that your hardware microcode is up-to-date.
If the source system is available, run the pre-migration script on it. Correct any other problems as recommended by the script.
I just would like to add to DukeSSD point, the mksysb will take care of users/passwords, hosts and printers and your application as a whole if it reside on rootvg! but if it is on other volume group then i suggest you backup that volume group and restore it as well! (smitty savevg)
But There are alot of variance in here (specially if the hardware is not the same on the two boxes!) you need to take care of new device drivers on the new box (if needed).
What is the application you are moving? and what is the boxes (target and source) of the application?
Regards,
Khalid
But There are alot of variance in here (specially if the hardware is not the same on the two boxes!) you need to take care of new device drivers on the new box (if needed).
What is the application you are moving? and what is the boxes (target and source) of the application?
Regards,
Khalid
khalidaaa, the point of the mksysb migration is that it takes care of the different AIX level and the different hardware for you.
Obviously if you have resourses, applications or data outside of rootvg you will need to copy these vg's over as well.
Obviously if you have resourses, applications or data outside of rootvg you will need to copy these vg's over as well.
So would the mksysb takes care of the different in hardware devices? like the kernel device drivers? How about if used to have SAN disks and now he wants to connect to Hitachi disks (just for the sack of exmple) I just thought that he might need to look into that as well.
Correct me if i'm missing the point!
Correct me if i'm missing the point!
If there is a different SAN device attached to the new machines he will obviously need to install the associated third party device drivers, but the mksysb migration will take care of any new p series features and install the associated drivers.
This is the point of the mksysb migration, you can even migrate a 4.3 mksysb on to hardware that doesn't support 4.3, it will migrate the oslevel to 5.3 in the process, as well as loading the new drivers for for the new system..
This is the point of the mksysb migration, you can even migrate a 4.3 mksysb on to hardware that doesn't support 4.3, it will migrate the oslevel to 5.3 in the process, as well as loading the new drivers for for the new system..
- Thread starter
- #7
There is some other things that I forgot to mention. The reason we are restoring or copying from a mksysb is because we had a break in our system where alot of things were changed, and removed. We want to just move the application and any configuration we can to preserve the essential configuration like users and printers so that we don't have to do it manually, without moving the entire vg, etc.
- Status