|
|
Your operating system normally resides in what HP Stage/iX calls the
Base. The Base is the set of files laid down by the last
UPDATE or INSTALL, and RESTORE from tape. The "base
location" or "natural location" is where a file officially resides (for
example, NL.PUB.SYS).
HP Stage/iX creates, fills, and validates staging areas. A
staging area is an HFS directory: /SYS/hpstage/stage_name. It
is located on disk and contains only the files of the OS that change as a
result of applying a set of patches. As needed, using the HP Stage/iX SET
command, you activate your system software to boot from either
the Base or a designated staging area.
Creating and Activating a Staging Area
When you boot your system from a staging area, HP Stage/iX:
Creates a Base file
archive.
Moves the affected Base
files to the archive:
/SYS/hpstage/base_archive.
Moves the staging area
files to their Base
location.
Boots the system using the
staging area files.
Much of the disk space used by the staging area and the archive is on LDEV 1.
When the system is booting from the Base files, the archive area is empty. When
the system is booting from the staging area files, the staging area is empty.
The amount of disk space used depends on the set of patched files. Refer to
Figure G-1 Creating and Activating a Staging
Area for more information.
Figure G-1 Creating and Activating a Staging Area
Backing Out a Staging Area
To backout the changes from a staging area, use the HP Stage/iX SET
command to designate the Base instead of the staging area. When you use the
SET command to backout a staging area, HP Stage/iX:
Moves the staging area
files back to the staging area.
Moves the Base archive files back to their
Base location.
Boots the system using the
staging area files.
Refer to Figure G-2 Backing Out Patch Changes
for more information.
Figure G-2 Backing Out Patch Changes
Applying the Changes
After you have tested and are satisfied with the changes from an active staging
area, use the HP Stage/iX COMMIT command to permanently apply the
changes to your system. This accomplishes the following:
Creates a new Base
.
Frees up disk space by removing the archived Base files and the
committed staging area.
Refer to Figure G-3 Permanently Applying Patch
Changes for more information.
Figure G-3 Permanently Applying Patch Changes
Using Multiple Staging Areas
You can have more than one staging area at a time. Each staging area contains
the difference, or delta, between the Base OS and a patched OS. Staging area
stage_1 contains the changes to the Base from patch_set_1.
Staging area stage_2 contains the changes to the Base from only
patch_set_2. You can use the SET command and boot from either
staging area stage_1 or stage_2. Refer to
Figure G-4 Creating Another Staging Area, from
the Base Location for more information.
Figure G-4 Creating Another Staging Area, from the Base Location
If you create an additional staging area, stage_name2, while operating
from another staging area, stage_name1, the additional staging area,
stage_name2, will contain all the changes to the Base from
patch_set_1 plus the new patches in patch_set_2. Refer
to Figure G-5 Creating Another Staging Area from
an Existing Staging Area for more information.
Figure G-5 Creating Another Staging Area from an Existing Staging Area
|