HP NonStop G-Series - Manual (Page 52)

Configuring and Managing SMF Processes
HP NonStop Storage Management Foundation User's Guide—523562-008
3-2
Configuration and Management Overview
The COUP interactive command interface is described in the Dynamic System
Configuration (DSC) Manual.

PUP lets you define storage pools and associate them with physical volumes. PUP
lets you define virtual disks and associate them with storage pools. PUP also lets
you control SMF process states and retrieve information about SMF processes.
PUP commands that support SMF are described in
Appendix B, COUP and PUP
Interfaces .
PUP is described in the Peripheral Utility Program (PUP) Reference Manual.

SCF provides the functionality described for both COUP and PUP; that is, it lets
you configure the attributes of SMF processes and establish the relationships
among them through a single utility.
SCF command descriptions, prerequisite usage considerations, and examples of
usage are described in the SCF Reference Manual for the Storage Subsystem.
Comparisons between SCF commands for G-series versions of SMF and COUP
and PUP utility commands for D-series versions of SMF are listed in
Appendix B,
COUP and PUP Interfaces .
Configuration and Management Overview
Configuration planning is vital. It will affect performance and manageability of your
system. Your configuration strategy will differ if you are configuring SMF on an existing
system or if you are migrating to a new system.
Configuration planning involves three main areas:

Considerations for pooling

Considerations for virtual disk process naming and location

Considerations for data, including location and special cases
Considerations for Pooling
You must consider certain issues when setting up pools. Size and configuration of
pools, catalog placement, frequency of gathering statistics, and how disk full errors are
reported will all affect recovery, manageability, and performance.
Pool Configuration
You will need to plan the size and configuration of your pools. You can group disks into
various types of pools: as one large pool, a separate pool per disk, by CPU, across
multiple CPUs, by disk attribute, and so forth. Following is a discussion of the reasons
you might choose different configurations.
The simplest way to plan pools might be to use one big pool. However, the
disadvantages outweigh the benefits of this scheme: