Chapter 2 HPSS Planning
HPSS Installation Guide September 2002 111
Release 4.5, Revision 2
MountDaemon Configurations. Each NFS Mount Daemon must have an entry in this configuration
metadata file describing various startup/control arguments. There will be one Mount Daemon
entry for each NFS server defined.
Mover Configurations. Each Mover (MVR) must have an entry in this configuration metadata file
describing various startup/control arguments. The minimum number of MVRs configured is
determinedby the number of nodes that have attached storage devices, plus the number of nodes
used to manage network-attached storage devices.
NFSDaemon Configurations. Each NFS Daemon must have an entry in this configuration metadata
file describing various startup/control arguments.
PVL Configurations. Each PVL server must have an entry in this configuration metadata file
describing various startup/control arguments. Currently, only one PVL server is used in a single
HPSS system.
PVR Configurations. Each PVR server must have an entry in this configuration metadata file
describingvarious startup/control arguments. Generally, one PVR will be defined for each robotic
tape library used by HPSS.
Storage Server Configurations. Each Storage Server (SS) must have an entry in this configuration
metadatafile describing various startup/control arguments. Generally,one disk SS and one tape SS
will be defined.
DMAP Gateway Configurations: This metadata file describes the startup/control information
used by the DMAP Gateway. Multiple DMAP Gateway Servers may be defined.
Non-DCEClient Gateway Configurations: Each Non-DCE Client Gateway must have an entry in
this configuration metadata file describing various startup/control arguments. It is possible for a
single HPSS system to be configured and run multiple concurrent NDCGs.
2.10.2.4 Name Server Metadata
TheName Server is the primary user of the following SFS metadata files (the default SFS filenames
are shown in parentheses):
• Name Space Objects (nsobjects.#)
• Access Control List Extensions (nsacls.#)
• Text Extensions (nstext.#)
• Fileset Attributes (nsfilesetattrs.#)
• Global Filesets (nsglobalfilesets)
NameSpace Objects. Each name space object (file, fileset, directory, hard link, junction or soft link)
usesone record in the object file. The total number of objects permitted in the name space is limited
bythe number of SFS records available to the Name Server. The number of SFS records available to
the Name Server should therefore be large enough to handle the projected capacity of the name
space. For example, in a name space expected to consist of 50,000 directories that have 1,000,000
files distributed among them, should have at least 1,050,000 SFS records allocated to the Name