ptx/INSTALL supports both scratch and update (or delta) installations of the base operating system and layered products. Scratch installations install the full operating system. Updates require that a version of the operating system already be installed. During an update, only new or changed files are installed and obsolete files are removed.
Layered products included on the distribution CD can be installed at the same time as the operating system. These products can also be installed at a later time.
Installations can be done on either the current root disk or an alternate disk. Typically, the operating system and layered products are updated on an alternate disk. Using an alternate disk minimizes down time; the installation can be done while the system is running in multiuser mode. When the operating system is booted on the alternate disk, that disk becomes the root disk.
To perform an update on an alternate disk, there must be a valid root filesystem on the alternate disk. ptx/INSTALL can copy an image of the current root filesystem to the alternate disk, or you can manually install a valid root filesystem on that disk.
ptx/INSTALL provides four installation types: SCRATCH, ROOT, INIT ALT DISK DELTA, and ALT DISK DELTA.
Depending on the products you are installing, you may need to install certain products with one installation type and other products with another installation type. You will need to run ptx/INSTALL again to change the installation type.
The ALT DISK DELTA installation procedure can be used in three different ways:
Use a mirrored plex of the current root disk as the alternate disk. You must remove the mirrored plex from ptx/SVM control temporarily before doing the install. This method must be used if ptx/SVM V2.x is currently installed on your system.
Update the base operating system and layered products on an unused alternate disk partition. You must manually copy an image of the root filesystem to the alternate disk. If you will be installing software in any other filesystems, you must also copy an image of those filesystems to the alternate disk.
Update the base operating system and layered products on the current root disk. First boot the operating system from the distribution CD, and then specify the current root disk as the alternate disk. You can also use this procedure if ptx/EFS is not currently installed and you want root to be an EFS filesystem. If ptx/SVM is currently installed on the root disk, you cannot use this method.
ATTENTION The NUMA Online Diagnostics Dispatcher, ptx/AGENT, ptx/PDC, ptx/SYNC, and SequentLINK products cannot be installed with the ALT DISK DELTA procedure. Use the ROOT procedure to install these products after updating the base operating system.
Backup Toolkit and ptx/LAE can be installed with the ALT DISK DELTA or ROOT procedure; however, DYNIX/ptx V4.6.1 must be installed and booted before the installation.
ATTENTION For systems with a single boot bay, you must perform an alternate disk installation on another partition of the current root disk. See "Requirements for Systems with a Single Bootbay" later in this chapter for more information.
This installation type updates the base operating system and layered products on an alternate disk while the system is running in multiuser mode. The procedure installs a VTOC on the alternate disk (if necessary), copies an image of the current root filesystem to the alternate disk, and then updates the specified products on that disk.
ATTENTION If ptx/SVM is installed on your system, use the ALT DISK DELTA procedure to perform the upgrade. See Chapter 4.
This procedure is not supported for any CD other than the DYNIX/ptx Volume 1 CD. This includes the DYNIX/ptx Volume 2 CD, the ptx/LAE CD, and the Backup Toolkit CD. Use the ROOT procedure to install products from these CDs after updating the base operating system.
Lastly, this procedure cannot be used to install the NUMA Online Diagnostics Dispatcher, ptx/AGENT, ptx/PDC, ptx/SYNC, or SequentLINK. Use the ROOT procedure to install these products after updating the base operating system.
ATTENTION The INIT ALT DISK DELTA procedure will place an image of root and /usr on the same partition on the alternate disk. Although root and /usr may currently be on different partitions, the INIT ALT DISK DELTA copy procedure will create a single root filesystem containing your current root and /usr filesystems. When the installation is complete, there will no longer be a separate /usr filesystem.
ATTENTION For systems with a single boot bay, you must perform an alternate disk installation on another partition of the current root disk. See "Requirements for Systems with a Single Bootbay" later in this chapter for more information.
The INIT ALT DISK DELTA procedure is supported only for the root and /usr filesystems; it cannot create an image of other filesystems. If your current root filesystem structure includes other filesystems containing directories where products install software, you cannot use the INIT ALT DISK DELTA procedure to install those products.
The following products install software in directories sometimes maintained as separate filesystems:
Product |
Directory |
DYNIX/ptx Public Software |
/usr/local |
ptx/XWM |
/usr/src |
If you want to use the INIT ALT DISK DELTA procedure to update DYNIX/ptx and other layered products, do not include products that install software in another filesystem. Instead, use the ROOT procedure to install those products after the INIT ALT DISK DELTA is complete.
Alternatively, you can manually create images of each filesystem on the alternate disk and then do the update with the ALT DISK DELTA procedure.
This installation type installs or updates layered products on the current root disk. It cannot be used to update the base operating system.
If you are updating a layered product that is already installed on the system, you should do the installation in single-user mode. If you are installing a layered product for the first time, you can do the installation in multiuser mode.
The SCRATCH installation type does an initial (full) installation of the base and layered products. A scratch installation can be done in two ways:
If DYNIX/ptx V4.4.2 or later is currently installed on your system, boot from the current root disk and install on an alternate disk.
If DYNIX/ptx is not currently installed, boot from the distribution CD and install on the designated disk. This method can also be used to install on the current root disk.
ATTENTION Scratch installations are not supported for Backup Toolkit, NUMA Online Diagnostics Dispatcher, ptx/AGENT, ptx/LAE, ptx/PDC, ptx/SYNC, or the SequentLINK product. These products must be ROOT installed after installing and rebooting on DYNIX/ptx V4.6.1. Alternatively, Backup Toolkit and ptx/LAE can be installed with ALT DISK DELTA after installing and rebooting on DYNIX/ptx V4.6.1.
Depending on the products you are installing, you may need to run ptx/INSTALL multiple times. For example, you may want to update DYNIX/ptx and certain layered products on an alternate disk using the INIT ALT DISK DELTA procedure and then run ptx/INSTALL again to install other layered products with the ROOT procedure.
ATTENTION After installing DYNIX/ptx on an alternate disk or with a scratch installation, you must boot the system on the V4.6.1 kernel before using the ROOT installation method to install other layered products.
Also, you must run ptx/INSTALL separately for each CD.
Before beginning the installation, we recommend that you determine whether you will need to run ptx/INSTALL more than once. If you will be making multiple install passes, also determine the products that will be installed on each pass and the appropriate installation type for each pass.
If you currently have a UFS root filesystem and will be installing ptx/EFS, you can change the filesystem to EFS. Similarly, you can change your current EFS root filesystem to UFS. To do this, you must use the ALT DISK DELTA installation type and copy the filesystem image manually.
If you are changing to an EFS root filesystem and ptx/EFS is not currently installed on your system, take one of these actions:
If you have a version of ptx/EFS that is compatible with your current version of DYNIX/ptx, install that version of ptx/EFS before performing the ALT DISK DELTA installation.
Boot from the distribution CD before copying the filesystem image for the ALT DISK DELTA installation. You cannot use this procedure if ptx/SVM is currently installed on your system.
Perform a SCRATCH installation.
Table 3-2 provides a summary of the installation types.
Software to Install |
Installation Type |
Boot From |
Installation Disk |
Update of base and layered products |
INIT ALT DISK DELTA |
Original root disk |
Alternatea,c,e |
ALT DISK DELTA |
CD |
Current rootb,c,d |
|
ALT DISK DELTA |
Original root disk |
Alternate; will create an image manuallyc,d |
|
ALT DISK DELTA |
Original root disk |
Mirrored plexc,d |
|
Update of base and layered products, changing filesystem type |
ALT DISK DELTA |
If filesystem type is already installed, original root disk. If filesystem type is not installed, CD. |
Alternateb,c,d |
Scratch of base, layered products (DYNIX/ptx is currently installed) |
SCRATCH |
Original root disk |
Alternatec,e |
SCRATCH |
CD |
Current rootc,e |
|
Scratch of base, layered products (DYNIX/ptx is not installed) |
SCRATCH |
CD |
Designated root diskc,e |
Layered products only |
INIT ALT DISK DELTA |
Original root disk |
Alternatea,c,d,e |
ALT DISK DELTA |
Original root disk |
Alternatea,c,d |
|
ROOT |
Current root disk |
Current root |
|
a. INIT ALT DISK DELTA can copy only the root and /usr filesystems. Products installing files in other filesystems cannot use this method. Not supported for any CD other than the DYNIX/ptx Volume 1 CD. This includes the DYNIX/ptx Volume 2 CD, the ptx/LAE CD, and the Backup Toolkit CD. b. If ptx/SVM is currently installed, update procedures requiring booting from CD cannot be used. c. Not supported for NUMA Online Diagnostics, ptx/AGENT, ptx/PDC, ptx/SYNC, or SequentLINK. d. Before Backup Toolkit or ptx/LAE installation, DYNIX/ptx V4.6.1 must be installed and booted. e. Not supported for Backup Toolkit or ptx/LAE. |
ATTENTION The root partition must contain at least 2 GB.
If your system is currently booted on DYNIX/ptx V4.6 (or you are performing a scratch installation and have booted from the distribution CD), you can install the operating system on a local or shareable disk. Disks that require the installation of a layered product (such as rd disks supported by ptx/RAID) cannot be used.
ATTENTION If ptx/CLUSTERS wll be installed on the node, the installation must be performed on a local disk.
If you are upgrading from DYNIX/ptx V4.4/V4.5, you must install the operating system on a local disk. For systems with a single boot bay, you must specify another partition on the current root disk as the alternate disk for the installation. The VTOC for the root disk contains two partitions, 0 and 2, that can be used for this purpose. (By default, the operating system is shipped on partition 0). If you currently have other data on your alternate partition, you will need to move the data to another disk before you begin the upgrade.
Also, if ptx/SVM is installed on your system, you will need to mirror the current root partition to the alternate partition before performing the upgrade.
If your system is currently booted on DYNIX/ptx V4.6 (or you are performing a scratch installation and have booted from the distribution CD), you can install the operating system on a local or shareable disk. For systems with multiple quads, the disk must be accessible from the first four quads. Disks that require the installation of a layered product (such as rd disks supported by ptx/RAID) cannot be used.
ATTENTION If ptx/CLUSTERS will be installed on the node, the installation must be performed on a local disk.
If you are upgrading from DYNIX/ptx V4.4/V4.5, you must install the operating system on a local disk. The disk must be connected to the qlc SCSI controller on the PCI bus on the boot quad and, for ALT DISK DELTA installations, must contain the following:
Root filesystem
Naming database (/etc/system/ndb). If this file does not already exist, it will be generated when you update the operating system.
The following must also be on a qlc SCSI controller: