 |
» |
|
|
|
To update from an earlier vPars A.02.xx or A.03.xx
version to the latest vPars A.03.xx version, perform the following
steps. Save
a copy of the vPars database in case you need to revert back to the
earlier version of vPars or you need to restore the database. Shut
down all the virtual partitions. Reboot
the server into standalone mode. This consists of the following: At the MON> prompt, type reboot If needed, interrupt the
boot sequence at the BCH> prompt and boot /stand/vmunix instead of /stand/vpmon. For example: BCH> bo pri
interact with IPL? y
.
.
.
ISL> hpux /stand/vmunix |
Install
the new vPars bundle using swinstall. For the appropriate
bundle name, see “Bundle Names”. Reboot
the system: # shutdown -r Boot
the vPars Monitor and the virtual partitions from the disk where you
installed the vPars bundle. For example, if we had installed the bundle
to the disk at the primary path: BCH> bo pri
interact with IPL? y
.
.
.
ISL> hpux /stand/vpmon -a |
If you have configured your AUTO file in the LIF area to boot the vPars Monitor and virtual partitions
automatically, then this step will be performed automatically. For
more information, see “Autoboot”. On
each virtual partition, repeat Step 4 to install the new vPars bundle on
each boot disk of each virtual partition (you
do not need to reboot the hard partition). Because the boot disk used
to boot in standalone mode in Step 3 already has the new vPars bundle
(this was installed during Step 4), you can exclude this step for the
boot disk at the primary path. You must install the new vPars bundle on each virtual partition before
putting the virtual partitions back into production. Running a mix
of older and newer vPars versions within a group of virtual partitions
is not supported.
|
Printable version
