Hpss Operational Planning - IBM Hub/Switch Installation Manual

High performance storage system release 4.5
Table of Contents

Advertisement

Chapter 2
HPSS Planning
If deciding to purchase Sun or SGI servers for storage purposes, note that OS limitations will only
allow a static number of raw devices to be configured per logical unit (disk drive or disk array).
Solaris currently allows only eight partitions per logical unit (one of which is used by the OS). Irix
currently allows only sixteen partitions per logical unit. These numbers can potentially impact the
utilization of a disk drive or disk array.
Refer to Section 2.10: HPSS Sizing Considerations on page 105 for more information on calculating
the number and size of raw devices that will be needed to meet your requirements.
Refer to Section 2.3: Prerequisite Software Considerations on page 46 for more information on the
required software that will be needed to run HPSS.
When you finally have an HPSS configuration that meets your requirements, it is then time to
purchase the necessary hardware and software.
2.1.3

HPSS Operational Planning

The following planning steps must be carefully considered for the HPSS operational phase:
1. Define the site policy for the HPSS users and SSM users.
Each HPSS user who uses the storage services provided by HPSS should be assigned
an Accounting ID and one or more appropriate Classes of Service (COS) to store files.
Each SSM user (usually an HPSS administrator or an operator) should be assigned an
appropriate SSM security level. The SSM security level defines what functions each
SSM user can perform on HPSS through SSM. Refer to Section 11.1: SSM Security on
page 275 of the HPSS Management Guide for more information on setting up the
security level for an SSM user.
2.
Define the site policy and procedure for repacking and reclaiming HPSS tape volumes. This
policy should consider how often to repack and reclaim HPSS volumes in the configured
tape storage classes. In addition, the policy must consider when the repack and reclaim
should be performed to minimize the impact on the HPSS normal operations. Refer to
Section 3.7: Repacking HPSS Volumes on page 74 and Section 3.8: Reclaiming HPSS Tape
Virtual Volumes on page 76 (both in the HPSS Management Guide) for more information.
3.
Define the site policy and procedure for generating the accounting reports. This policy
should consider how often an accounting report needs to be generated, how to use the
accounting information from the report to produce the desired cost accounting, and
whether the accounting reports need to be archived. Refer to Section 2.8.3: Accounting
Policy and Validation on page 85 and Section 6.6.3: Configure the Accounting Policy on page
289 for more information on defining an Accounting Policy and generating accounting
reports.
4.
Determine whether or not gatekeeping (monitoring or load-balancing) will be required. If
so, define and write the site policy code for gatekeeping. Refer to Section 2.8.7: Gatekeeping
on page 90 for more information on Gatekeeping and HPSS Programmers Reference, Volume
1 for guidelines on implementing the Site Interfaces for the Gatekeeping Service.
42
September 2002
HPSS Installation Guide
Release 4.5, Revision 2

Advertisement

Table of Contents
loading

This manual is also suitable for:

Hpss

Table of Contents