more information about configuring families.
•Plan for filesets and junctions, if any. Refer to Chapter 10: Filesets and Junctions in
the HPSS Management Guide for more information.
•Plan for HPSS storage classes. Refer to Section 3.10.1: Storage Class on page 102 for
more information on the storage class configuration.
•Plan for HPSS storage hierarchies. Refer to Section 3.10.2: Storage Hierarchy on
page 109 for more information on the storage hierarchy configuration.
•Plan for HPSS classes of service. Refer to Section 3.10.3: Class of Service on page
110 for more information on the Class of Service configuration.
•Plan the migration and purge policy for each storage class. Refer to Section 3.9.1:
Migration Policy on page 94 and Section 3.9.2: Purge Policy on page 95 for more
information.
•Determine the amount of user data storage space needed for each storage class. Refer
to Section 3.5.1: HPSS User Storage Space on page 69 for more information on the
HPSS storage space considerations.
•Identify the disk and tape media to be imported into HPSS.
7. Define the location policy to be used. Refer to Section 3.9.6: Location Polic y on page 99 for
more information.
8. Define the accounting policy to be used. Refer to Section 3.9.3: Accounting Policy and
Validation on page 96 for more information on the Accounting Policy configuration.
9. Define the logging policy for the each of the HPSS servers. Refer to Section 3.9.5: Logging
Policy on page 99 for more information on the Logging Policy configuration.
10. Define the security policy for t he HPSS system. Refer to Section 3.9.4: Security Policy on
page 98 for more information on the Security Policy for HPSS.
11. Determine if a Gatekeeper will be re quired. It is required if a site wants to do Account
Validation or Gatekeeping. Refer to Section 3.9.3: Accounting Policy and Validati on on page
96 and Section 3.9.7: Gatekeeping on page 99 for more information.
3.1.3. Purchasing Hardware and Softwa re
It is recommended that hardware be purchased only after the HPSS configuration has been planned.
Purchasing the hardware prior to the planning process may result in performance and utilizat ion
issues that could easily be avoided by advance planning.
If deciding to purchase Sun, SGI, or Linux servers for storage purposes, note that the operating
system limitations will only allow a fixed number of raw devices to be configured per logical unit
(disk drive or disk array). Sun's Solaris operating system currently allows only eight partitions per
logical unit (one of which is used by the system) unless the optional volume manager is used. SGI's
IRIX operating system currently allows only sixteen partitions per logical unit. Linux operating
system limits SCSI disks to 15 partitions and limits IDE disks to 63 partitions unless LVM is used.
These limits can potentially impact the utilization of a disk drive or disk array.
Refer to Section 3.5: HPSS Sizing Considerations on page 68 for more information on calculat ing the
number and size of devices that will be needed to meet your requirements.
Refer to Section 3.3: Prerequisite Considerations on page 58 for more information on the required
software that will be needed to run HPSS.
HPSS Installation Guide July 2008
Release 6.2 (Revision 2.0) 54