5.2 to 5.3 migration

[MoreFeo]

Hi all, I'm kind of new to AIX administration and I've got to migrate from 5.2 to 5.3 ML 2. What are the steps you'll recomend me to follow? (unmirror rootvg, run pre_migration, etc....)

Thanks.

 

[Breslau]

1. create a mksysb backup image of your rootvg. you can use tape if you have a drive attached to your host, or an nfs mounted directory from a NIM host. even if you don't have either of these, you can run your mksysb to a filesystem outside of rootvg and pull files out you might need since the mksysb image is in backup format.

2. boot off the first cd from the 5.3 media pack and do a migration install. you'll have to watch the console to see the menus when they come up.

you can do the 'break the mirror and upgrade one side routine' if you're paranoid, but what's described above is safe enough for most ppl. it's very rare that i've seen an upgrade trash a rootvg... and even then, it was in an SP env and not on a stand alone box.

holler if you need mroe details....

 

[MoreFeo]

Thanks a lot. It's just that I don't want to miss anything, 'cause I've never done a migration before and I haven't seen a lot of info about migrating from 5.2 to 5.3.

 

[mrn]

I'd do a savevg as well

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

http://www.airport-parking-site.co.uk/

 

[Breslau]

The mksysb is really your best line of defense against a serious problem. no matter what happens with your upgrade, you'd always have that image to put you right back into a stable state.. providing you have a method to install it back into your system, such as mentioned above.

i've done a half dozen or so migrations to 5.3 and so far i've seen no issues, everything ran real smooth. a few things i would check for tho, and these usually happen after any aix upgrade:

1 - your sendmail.cf will get overwritten, note your customizations beforehand and alter the new file to fit your needs.

2 - some services in inetd.conf will be turned back on. i think ntalk is one of them. so if you're in the habit of shutting off unwanted services, check this file after you upgrade. think this might also happen after a ML upgrade too.

3 - /etc/motd is copied to /tmp/bos/etc and replaced with a generic 'welcome to aix 5.*' motd. so, you may want to copy back your old one if you use the motd.

4 - if you use any of the toolbox rpm's that have been ported over from linux, check to see if there are any versions of them specific to aix 5.3 and upgrade those as well after you get to 5.3

5 - verify that any tunables (network & i/o) that you set for 5.2 got carried over to 5.3. i'm not sure if these get wiped out, but it wouldn't hurt to check.

hmm, i guess those are the 'major' things i would look out for...

 

[remsauk]

One thing that happened to me going from 5.1 to 5.3 (level 4) was that it expired root's account. I worked w/a Business Partner; we were able to access root's account and noticed the EXPIRATION date value for root was set (as I recall) to 0101000071. We were able to change that to 0.

 

[MoreFeo]

Well, finally I migrated and didn't have any problem, it all went fine.

Thank you for your replies.

 

[chkpulse]

I recommend using alt_disk_install, restoring the mksyb to the alt_rootvg and then upgrading that from a spot. Then all you have to do is reboot. You can manually do it by booting to the alt_root_vg and then migrating my hand.