Sun Microsystems Solaris 7 11/99, Руководство по аппаратной платформе

Страница: 142 / 224

130 Solaris 7 11/99 Sun Hardware Platform Guide • November 1999
If you do not have a good understanding of device numbering, you should either
perform a fresh install and recreate your AP configuration from scratch, or ask your
service representative for assistance.
AP Database Partitions
The AP upgrade scripts attempt to recreate the AP databases in the same partitions
that they occupied before the upgrade to the Solaris 7 11/99 operating environment.
Note, however, that the Solaris 7 11/99 operating environment requires more disk
space than earlier versions of the Solaris operating environment. Because of this, you
can choose to modify the boot disk partitioning scheme during
suninstall
. If you
place file systems in all partitions that were previously used for AP databases,
ap_upgrade_finish
is not able to recreate any databases and the upgrade process
fails. Furthermore, if you place a file system in any partition that was previously
used for an AP database, and if for some reason that file system is not mounted at
the time you run
ap_upgrade_finish
, that file system is overwritten by a copy of
the AP database.
Root Disk Partitions
The AP upgrade facility assumes that the partitioning of the
root
disk (the disk
containing the
root
partition) is not modified during the upgrade. The
Solaris 7 11/99 software requires more disk space than earlier versions.
One way to acquire the additional space is to repartition the original disk or to split
the
root
disk into two disks using standard commands prior to the Solaris 7 11/99
upgrade. If you need to repartition the
root
disk, you should do so before
performing the AP 2.2 upgrade procedure. If there is insufficient space when you
run
suninstall
, you have the option to modify the disk partitioning layout to
acquire more space. However, during
suninstall
, you must not relocate the
root
or
usr
partitions to another disk as this will cause the AP upgrade script to fail.
Uncommitted AP Database Entries
Before you run
ap_upgrade_begin
, commit any uncommitted entries in the AP
database. Any metadevices that were created but not committed are not preserved
during the upgrade. Similarly, any metadevices that were deleted but not committed
will continue to exist after the upgrade.
▼
To Upgrade To AP 2.2
1. If necessary, commit any uncommitted AP metadevices.