HP Integrity NonStop H-Series - Manual (Page 272)

Backing Out a Revision
DSM/SCM User’s Guide — 529846-014
15 - 3
Task 3: Perform Backout Activities
Task 3: Perform Backout Activities
1. Enter 3 (Perform target activities) in the Selection number field, and press F1.
DSM/SCM displays the Target Menu - Select Target Screen.
2. On the Target Menu - Select Target Screen, enter the number corresponding to the
name of the target system, and press F1.
3. On the Target Menu - Select Action screen, enter 2 (Perform backout to S/W) in
the Selection number field, and press F1.
The ZPHITI requires that you provide the location of the snapshot
(\system.$volume) before it begins processing the backout.
DSM/SCM displays the Backout - Verify Request screen, which contains:

The SYSnn, date, and timestamp of the current software revision and of the
previous revision, which becomes the current revision after the backout
request finishes

The location where DSM/SCM will place the snapshot

A warning that the request will make the last software applied on this target
inaccessible
4. Press F1 to submit the ZPHITI Backout request.
DSM/SCM updates the target database to make the previous software revision the
current revision. An activity record is posted, the current revision is made an
inaccessible backed-out revision, and the rename work directory file in the SYSnn
subvolume is updated.
While the backout request is processing, DSM/SCM displays the Backout-
Processing Backout screen, which gives a description of the request, its
processing status, and the location of the previous SYSnn software affected by the
request.
Note. If selection 2 (Perform backout to S/W) is not available, you have either performed a
backout, or a previous configuration does not exist. In the latter case, see
Previous
Configuration Does Not Exist or DSM/SCM Does Not Run on page 15-6.
Note. Do not delete the SYSnn that was backed out until one more SYSnn has been
applied. DSM/SCM relies on these files being present until the next SYSnn is applied,
after which it automatically deletes them.
Although the backed-out revision continues to exist until a new revision is applied,
DSM/SCM no longer manages it. Thus, it is effectively removed. To reinstall the backed-
out revision, use the Planner Interface to rebuild and reapply it.