NonStop S-Series Planning and Configuration Guide (G06.25+)

Planning for System Configuration
HP NonStop S-Series Planning and Configuration Guide—523303-015
15-10
Creating an Alternate System Disk
For information about performing these configuration changes using TSM, refer to:
•
TSM Configuration Guide
•
TSM Low-Level Link Application online help
•
TSM Notification Director Application online help
•
TSM Online User Guide
Creating an Alternate System Disk
Reasons to create an alternate system disk include:
•
You can minimize unplanned outage minutes by having an alternate system disk
configured as a backup.
•
You can avoid a planned outage by configuring an alternate system disk to use in
case you must stop your current system disk.
•
You can use the alternate system disk to keep your system running while the main
system disk is offline.
For more information, see the DSM/SCM User’s Guide or the NonStop S-Series
Hardware Installation and FastPath Guide.
Startup and Shutdown Files
Automating System Startup
You can use startup command files to automate the starting of devices and processes
on the system, which minimizes the possibility of operator errors caused by forgotten
or mistyped commands. The system is shipped with a basic startup file named CIIN,
located on the $SYSTEM.SYS00 subvolume.
After the commands in the CIIN file are executed, other startup files can be invoked
either automatically, from another startup file, or manually, in commands entered by the
operator. The startup file sequence usually starts the spooler and other system
software first and then starts applications.
The sequence in which you invoke startup files can be important. Some processes
require other processes to be running before they can be started.
Because the TCP/IP configurations are not stored in the configuration database, they
are not preserved after system loads. Therefore, TCP/IP stacks must be configured as
well as started each time the system is started.