 |
» |
|
|
|
|  | |
Upgrade Tools | |
10.x involves major changes both to the structure and content
of HP-UX. To smooth the transition from 9.x, HP has provided tools
to: Automate the conversion of the file
system and system configuration files. These tools are invoked automatically during the upgrade itself;
see Chapter 6 “Upgrading Your System from 9.x to
10.01 ” for more information. Link 9.x system pathnames to 10.x system pathnames. These links, called transition links,
will be installed by default when you upgrade to 10.01. They will
allow many 9.x applications to run without modification on 10.01. Analyze your 9.x system for any configuration or
other problems that could cause the upgrade to fail. For example, you might not have enough disk space or memory,
or you might be running optional software that is not supported
on 10.01, such as DataPair/800. The snoop
tool, described in Chapter 4 “Pre-Upgrade Tasks for All 9.x Systems”,
will give you precise information about each system you run it on.
Upgrade Options | |
There are two possible approaches you should keep in mind
when planning your upgrade, though you may in fact decide to combine
the two. Option B: Full Preparation
The following subsections provide details of each approach. | | | |  | NOTE: Bear in mind as you read that if you are going to 10.10
you must do a two-stage upgrade: first to 10.01, then to 10.10.
See Chapter 1 “Introduction ” for an outline of
the whole process. | | | | |
This approach relies on the transition links
(sometimes referred to as "fast transition links" or "compatibility
links"). Transition links are installed by default on all 10.x systems;
they link HP-UX 9.x "system" pathnames to their 10.x equivalents,
and they are intended to reduce the amount of conversion work you
will have to do on 9.x code and scripts when you first come up on
a 10.x system. If you adopt this approach entirely, you will simply run your
normal regression tests on applications and scripts once you come
up on 10.01 or 10.10, just as you would after any other upgrade.
You should find that much of your code runs without problems. But do not rely on transition links to solve all problems,
or as more than a short-term aid; HP does not intend to support
them beyond 10.x and they will only help with problems related to
pathnames; there could be other problems. For example, if your code uses commands or system calls that
are no longer supported or whose options or behavior have changed,
or if it builds or makes reference to 9.x device files (other than
"default" names such as /dev/lp
which are still recognized by HP-UX), you will have to fix it. HP recommends that you do the following for a "quick start": For more information on transition links, see the tlinstall(update_aid)
manpage, which you'll find on your system after you upgrade to 10.01. Estimated time required for this approach:
Pre-Upgrade: 8 - 20 hrs
Upgrade (Downtime): 4 - 12 hrs
Post-Upgrade: 3 - 5 hrs
-----------
Total: 15 - 37 hrs |
Option B: Full PreparationThis approach requires more preparation time than option A,
described in the previous subsection; but it has the following advantages: Your 9.x applications and scripts
are more likely to work first time and without problems when you
first come up on 10.01, and will be more easily portable to other
vendors' "V.4" systems. All the same, contact the suppliers of critical applications,
including HP applications, well before you commit to an upgrade,
to make sure these applications are supported on 10.x. You will have a more thorough understanding of 10.01/10.10
and how they differ from earlier HP-UX releases. By the time you come up on 10.01, you will have
done the conversion work that must be done sometime over the lifetime
of 10.x.
This approach involves the following steps: Estimated time required for this approach:
Pre-Upgrade: 11 - 28+ hrs
Upgrade (Downtime): 5 - 12 hrs
Post-Upgrade: 5 - 8 hrs
------------
Total: 21 - 48+ hrs |
|
Printable version
