NonStop S-Series Operations Guide (G06.27+)

Starting and Stopping the System
HP NonStop S-Series Operations Guide—522459-008
16-2
When to Use This Section
When to Use This Section
You normally leave a system running. Therefore, powering the system on and off, or
starting (performing a system load) and stopping the system, are not part of the daily
operations routine. However, you do have to perform these procedures as part of some
system operations. For example, you stop and restart a system (without powering
down) during these types of procedures:
•
Powering on and starting a new NonStop S-series server for the first time. Follow
the directions described in the NonStop S-Series Installation and FastPath Guide.
•
Installing an updated RVU or a software product revision (SPR).
•
Performing some major maintenance or repair operations.
•
Performing some recovery operations.
•
Restarting the system after the entire system has been shut down with the
operating system images and files on disk still intact.
•
Changing the system topology.
You have to stop and power down the system prior to an extended planned power
outage for your building or computer room.
Minimizing the Frequency of Planned Outages
You can minimize the frequency of planned outages by:
•
Anticipating and planning for change
•
Performing changes online
Anticipating and Planning for Change
Anticipating and planning for change is a key requirement for maintaining an
enterprise-level, 24 x 7 operation. To avoid taking a NonStop S-series system down
unnecessarily:
•
Evaluate system performance and growth—Track system usage and anticipate
system capacity and performance requirements as new applications are
introduced. For guidelines and a list of tools provided by HP, refer to the
Availability Guide for Change Management.
•
Provide adequate computer room resources—Avoid unnecessary downtime by
ensuring you have enough physical space and power and cooling capacity to
handle future growth.
•
Configure the system with change in mind—Configure the system in a way that
easily accommodates future growth. One way to do this is to select limits that
allow for growth. For example, by configuring enough objects to provide for the
anticipated growth of your online transaction processing environment, you can