Renaming the managed sysnn (optional) – HP Integrity NonStop H-Series User Manual
Page 221
Loading the System
DSM/SCM User’s Guide — 529846-014
12 - 2
Renaming the Managed SYSnn (Optional)
Renaming the Managed SYSnn (Optional)
If you prefer to load your system from the same SYSnn subvolume such as SYS00:
You can configure the update on the current SYSnn without problems if the
software update does not require system generation.
If system generation is required, configuring the update on the current SYSnn
would cause the Apply request to stop with errors. Configure the update on a
different SYSnn and then rename that SYSnn to the one you plan to load the
system from.
For example, to always load your system from SYS00, configure your update on
SYS01 and then rename SYS01 to SYS00:
1. Perform an Apply on the new SYSnn (in this example, SYS01).
2. Run ZPHIRNM on the new SYSnn (SYS01).
3. Rename the running SYSnn (SYS00) to another unused SYSnn (SYS20).
4. Rename the running CSSnn (CSS00) to another unused CSSnn (CSS20).
5. Rename the new SYSnn (SYS01) applied by DSM/SCM to your usual SYSnn
(SYS00).
6. Rename the new CSSnn (CSS01) applied by DSM/SCM to your usual CSSnn
(CSS00).
7. Perform a system load on your usual SYSnn (SYS00), which now contains the
updated software configuration.
8. Restart DSM/SCM.
9. 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 ever need to
back out to the previous revision.)
a. Before the next Apply to the system, run Verify Database so that DSM/SCM
can resolve the current names of the SYSnn subvolumes. See
Target System Database (ZPHITI)
b. Create an independent snapshot of the target. See
c.
On the host system, receive the independent snapshot you just created into
the host database. See
Task 9: Transfer and Receive the Snapshot Into the
You can back out to the previous revision if you used this procedure to rename the
managed SYSnn. (See