Gatekeeper is already configured, simply add it to your storage subsystem's configuration.
However, if it is not yet configured, it will be necessary to wait until Section 4.2. 3.4: Assign a
Gatekeeper if Required on page 80 to add the Gatekeeper.
6. Set the metadata space thresholds and the update interval. Typical values are 75 for warning, 90
for critical and 300 to have the metadata space usage checked every 300 seconds.
7. Set the DB Log Monitor Interval. Minimum value is 300 seconds, typical value is 1800 seconds.
8. Press the Add button to store the configuration.
4.2.3.3. Create Storage Subs ystem Servers
The new storage subsystem must contain a single Core Server. If migration and purge services will be
needed then a Migration Purge Server is also required. See the following sections for instructions on
configuring these new servers:
•Section 5.1: Server Configuration on page 87
•Section 5.1.1: Core Server Specific Configuration on page 96
•Section 5.1.2: Migration/Purge Server (MPS) Specific Configuration on page 101
On each server's basic configuration window, be sure to assign the server to the new storage subsystem.
4.2.3.4. Assign a Gatekeep er if Required
If gatekeeping or account validation are needed and an appropriate Gatekeeper is not already configured,
a new Gatekeeper will be required. See the HPSS Installation Guide, Section 3.7.3: Gatekeeper, Section
5.1.2: Gatekeeper Specific Configuration on page 98 for instructions on configur ing the Gatekeeper.
Be sure to assign this Gatekeeper to the appropriate storage subsystem by choosing it from the
Gatekeeper selection list on the appropriate Storage Subsystem Configuration window.
4.2.3.5. Assign Storage Re sources to the Storage Sub system
Storage resources are tied to a storage subsystem through storage classes. To determine which storage
classes belong to a particular subsystem, look up the configuration for each Class of Servi ce available to
the storage subsystem. Each Class of Service is tied to one storage hierarchy which is in turn tied to some
number of storage classes. Storage resources must then be assigned to the storage classes which are used
in the referenced hierarchies. See Section 8.1.2: Creating Storage Resources on page 234 for details.
4.2.3.6. Create Storage Subs ystem Fileset and Juncti on
The HPSS namespace consists of filesets that are connected by junctions. The top (root directory) of the
HPSS namespace is the RootOfRoots fileset managed by the Root Core Server. The rest of the
namespace is built by pasting filesets together using junctions.
Since each subsystem has its own Core Server, it also has its own root fileset. This fileset needs to be
connected to the HPSS namespace in order for files to be stored in the new subsystem. This is
accomplished by creating a junction from the HPSS namespace to the root fileset of the new subsystem.
See Chapter 10: Filesets and Junctions for more information.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 80