NonStop NS-Series Operations Guide (H06.12+)

Table 15-1 System Load Paths in Order of Use (continued)
Data Travels
Y0$SYSTEM-MMirror6
X0$SYSTEM-MMirror backup7
Y0$SYSTEM-MMirror backup8
X1$SYSTEM-PPrimary9
Y1$SYSTEM-PPrimary10
X1$SYSTEM-PBackup11
Y1$SYSTEM-PBackup12
X1$SYSTEM-MMirror13
Y1$SYSTEM-MMirror14
X1$SYSTEM-MMirror backup15
Y1$SYSTEM-MMirror backup16
Configuration File
Normally, you select Current (CONFIG), the default system configuration file. For the system
disk volume you select to load the system, CONFIG represents the system configuration database
that is currently running or was last running.
If you cannot load the system using Current (CONFIG), you might need to use these files to
recover:
• Saved Version (CONFxxyy) is a saved system configuration file. Use this file to recover
from a configuration change that causes a problem. If you cannot load the system using the
CONFIG file, you can use a saved version in the form xx.yy, if one is available. For example,
the CONF0205 file would be specified as 02.05. Use this method to recover from a
configuration change that caused a problem (such as a system freeze). When the system
starts and displays a TACL prompt, you can log on and start the rest of the system
applications.
• Base (CONFBASE) is the most basic configuration required for system startup. Although
you will probably never need to load the system from the CONFBASE file, you might need
to use this file if you cannot load the system using any other method.
For more information about when to use CONFSAVE or CONFBASE, see “Recovering From a
System Load Failure ” (page 168)
Starting Other System Components
HP recommends that you bring your system up in stages, verifying each stage, to facilitate
recovery if any step fails. When the system starts, many individual devices, processes, applications,
and communications lines start automatically, but others might need to be started using start up
files. Follow your site’s procedures for starting your applications.
• Many processes are configured by default to be started automatically by the $ZPM persistence
monitor. These processes include the Kernel subsystem, SLSA subsystem, storage subsystem,
and WAN subsystem. The manager processes for these subsystem start disks, SWAN
concentrators, some LAN devices, and many processes.
• You can use SCF to configure other processes, typically monitor or manager processes, to
start automatically as generic processes when the system starts. For example, you can use
160 Starting and Stopping the System