HP-UX upgrade

[RandyRiegel]

I just started doing some work for a company and they have an HP-UX (HP9000 K200) machine. It is only running 10.10 which I'm pretty sure is outdated. There is a whole file cabinet full of updates CD's from HP which I don't think ever have been installed.

The newest CD I can find is from June 1998 and is labeled "HP-UX 11.00 Extension Pack 9804 Install and Core OS". By looking at the booklet in the CD it looks as though I can use this CD to upgrade to 11.00? Is this correct?

Randy

 

[MikeLacey]

Yes - 10.10 is outdated and is not even Y2K compatible, though I suspect that issue hasn't bothered this customer.

Yes - that CD can be used to upgrade - but I wouldn't do that.

Instead, I would:

Gather together:
[ul]
[li]Latest HP-UX release supported by *all* your applications[/li]
[li]The reccomended HP-UX patches for that UX release[/li]
[li]The reccomended HP-UX patches for all of your applications[/li]
[li]Installation media for all of your applications on the UX release you've decided on[/li]
[li]A new boot disk - on which to install new UX[/li]
[li]Enough spare diskspace on which to install new versions of applications[/li]
[li]Some beer[/li]
[/ul]

Then:

Look at migration procedures for migrating the current versions of your APPLICATIONS to the new version that will be running when you've upgraded HP-UX. Plan each step. Plan it so that the old data never goes away - so that you can step back to it if needed.

Then:
[ul]
[li]Back up your machine, completely.[/li]
[li]Make a boot tape using make_tape_recovery[/li]
[li]Install new boot disk[/li]
[li]Install new HP-UX on new boot disk, set this as alternate boot[/li]
[li]Disable application start-up on boot[/li]
[li]Test that the machine will boot ok under new HP-UX[/li]
[li]Install new versions of each application[/li]
[li]Apply the patches[/li]
[li]Migrate data for each application[/li]
[li]Test each application[/li]
[li]Enable application start-up on boot[/li]
[li]Test boot process, check each application[/li]
[li]Back up your machine, completely.[/li]
[li]Make a boot tape using make_tape_recovery[/li]
[li]Drink the beer[/li]
[/ul]
You'll notice that the above process doesn't need to be done all in one go. You can even have rehearsals of the switchover process and go back to your old data if needed.

Mike

To err is human,
but to really foul things up -
you require a man Mike.

Want to get great answers to your Tek-Tips questions? Have a look at faq219-2884

 

[KenCunningham]

Mike - why is it you always make things sound so simple ;-)

 

[MikeLacey]

Well.... If, like me, you're handicapped by limitless incompetence you have to learn to plan

Hmmm multiply the number of machines in the example above by about 30, put the new machines in a data-centre about 150 miles away, make *sure* your applications are a real pain in the neck and need a team of 50 ppl (I'm serious) to migrate the data. Then have a window of a single weekend to switchover. Then you'll have the project I'm currently working on...

Mike

To err is human,
but to really foul things up -
you require a man Mike.

Want to get great answers to your Tek-Tips questions? Have a look at faq219-2884

 

[KenCunningham]

My sympathies, Mike. I have a project at the moment where the original 'documentation' seems to have consisted of random pathnames, services, scripts etc written on post-it notes in no particular order and then dipped in coffee/coke or whatever and shuffled. I'm taking them home at the weekend to see whether my three-year-old has better luck in sorting them than I'm having!

 

[MikeLacey]

[hurt look] "why is it you always make things sound so simple"

Now that wouldn't be sarcasm would it Kenneth?

Mike

To err is human,
but to really foul things up -
you require a man Mike.

Want to get great answers to your Tek-Tips questions? Have a look at faq219-2884

 

[KenCunningham]

Moi? Absolutely not, Michael. The very suggestion!