System load and dsm/scm restart succeed, Backing out to an older configuration – HP Integrity NonStop H-Series User Manual
Page 214
System Load and DSM/SCM Restart Succeed
1.
Run ZPHITI to perform a backout (tasks 1 through 5 of
“Backing Out if DSM/SCM is Running”
).
2.
Run ZPHIRNM on the previous SYSnn (in this example, SYS20). For more information, refer
to
. The previous SYSnn is the software configuration that was
running before the current softwareconfiguration.
3.
Rename the current SYSnn (SYS00) and CSSnn (CSS00) to an unused SYSnn (SYS01) and
CSSnn (CSS01), respectively. For example:
> FUP RENAME $SYSTEM.SYS00.*, $SYSTEM.SYS01.*
> FUP RENAME $SYSTEM.CSS00.*, $SYSTEM.CSS01.*
4.
Rename the previous SYSnn to the name it had at the completion of the Apply. For example:
> FUP
> RENAME $SYSTEM.SYS20.*, $SYSTEM.SYS00.*
> RENAME $SYSTEM.CSS20.*, $SYSTEM.CSS00.*
5.
Perform a system load on your usual SYSnn (SYS00), which now contains the revision before
the last update.
6.
Restart DSM/SCM.
7.
Update the DSM/SCM database with the new SYSnn subvolumes. (You do not need to do
this immediately, but do it as soon as possible in case you need to back out to the previous
revision.)
a.
Before the next Apply to the system, run a Verify Database so that DSM/SCM can resolve
the current names of the SYSnn subvolumes.
b.
Create an independent snapshot of the target.
c.
Receive the independent snapshot into the host database.
System Load Fails or DSM/SCM Does Not Run Correctly
1.
Perform a system load from the previously working SYSnn (renamed to SYS20).
2.
Rename the current SYSnn (SYS00) and CSSnn (CSS00) back to the last built SYSnn (SYS01)
and CSSnn (CSS01), respectively. For example:
> FUP RENAME $SYSTEM.SYS00.*, $SYSTEM.SYS01.*
> FUP RENAME $SYSTEM.CSS00.*, $SYSTEM.CSS01.*
3.
Rename the previous SYSnn to the name it had at the completion of the Apply. For example:
> FUP
> RENAME $SYSTEM.SYS20.*, $SYSTEM.SYS00.*
> RENAME $SYSTEM.CSS20.*, $SYSTEM.CSS00.*
4.
Run ZPHIRNM to reverse the ZPHIRNM done before the SYSnn subvolume was renamed. For
more information, refer to
. For example:
> RUN ZPHIRNM $volume.SYS00, FROM $volume.SYS01
5.
Perform a system load from the newly renamed working SYSnn (now renamed to SYS00).
6.
Start DSM/SCM.
7.
Run ZPHITI to perform the backout step (Tasks 2 through 4 of
) to back out to SYS00.
Backing Out to an Older Configuration
In this procedure, you are applying a new configuration, but want to be able to back out to a
previous configuration if needed instead backing out to the configuration currently running on your
system. A previous configuration is the configuration that was executing on the target system just
before the current configuration.
In this example, G06.25 is currently running on your system. The previous configuration was
G06.24. To run G06.26, but keep G06.24 as the configuration to back out to instead of G06.25:
214
Backing Out a Revision