Filter
Top Products
GUI. The hpssgui simplifies the management of HPSS by organizing a broad range of technical data
into a series of easy-to-read graphic displays. The hpssgui allows monitoring and control of virtually
all HPSS processes and resources from windows that can easily be added, deleted, moved, or
overlapped as desired.
HPSS also provides a command line SSM interface, hpssadm. This tool does not provide all the
functionality of the hpssgui, but does implement a subset of its frequently used features, such as some
monitoring and some control of servers, devices, storage classes, volumes, and alarms. It is useful for
performing HPSS administration from remote locations where network traffic is slow or difficult.
Additionally, hpssadm provides some rudimentary mass configuration support by means of the ability
to issue configuration commands from a batch script.
In addition to SSM, HPSS provides a number of command line utilities for specialized management
purposes, such as listing the volumes managed by a particular PVR or core server. See the HPSS
Management Guide Chapter 14: Management Tools for more information. See also the HPSS man
pages for descriptions of these utilities.
2.3.7. HPSS Policy Modules
There are a number of aspects of storage management that probably will differ at each HPSS site. For
instance, sites typically have their own guidelines or policies covering the implementation of
accounting, security, and other storage management operations. In order to accommodate site-specific
policies, HPSS has implemented flexible interfaces to its servers to allow local sites the freedom to
tailor management operations to meet their particular needs.
HPSS policies are implemented using two different approaches. Under the first approach, used for
migration, purge, and logging policies, sites are provided with a large number of parameters that may
be used to implement local policy. Under the second approach, HPSS communicates information
through a well-defined interface to a policy software module that can be completely replaced by a
site. Under both approaches, HPSS provides a default policy set for users.
• Migration Policy. The migration policy defines the conditions under which data is copied
from one level in a storage hierarchy to one or more lower levels. Each storage class that is to
have data copied from that storage class to a lower level in the hierarchy has a migration
policy associated with it. The MPS uses this policy to control when files are copied and how
much data is copied from the storage class in a given migration run. Migration runs are started
automatically by the MPS based upon parameters in the migration policy.
Note that the number of copies which migration makes and the location of these copies is
determined by the definition of the storage hierarchy and not by the migration policy.
• Purge Policy. The purge policy defines the conditions under which data that has already been
migrated from a disk storage class can be deleted. Purge applies only to disk storage classes. It
is common, but not necessary, for disk storage classes which have a migration policy to also
have a purge policy. Purge runs are started automatically by the MPS based upon parameters
in the purge policy.
• Logging Policy. The logging policy controls the types of messages to log. On a per server
basis, the message types to write to the HPSS log may be defined. In addition, for each server,
options to send Alarm, Event, or Status messages to SSM may be defined.
• Security Policy. Security policy defines the authorization and access controls to be used for
client access to HPSS. HPSS security policies are provided to control access (authentication)
from FTP and/or Parallel FTP using Username/Password, Ident, or Kerberos credentials.
HPSS Installation Guide July 2008
Release 6.2 (Revision 2.0) 47