Table of Contents
Advertisement
•
A detailed description of the anticipated production usage of HPSS, including distribution
of file sizes, data acquisition and access methods, key projects, user expectations, admin/
operations expectations, availability requirements, and performance and loading
requirements.
•
Detailed HPSS configuration information (Note: The lshpss.ksh script is from the
deployment tools package).
To generate the HPSS configuration information locally, issue the following on the core
HPSS server node:
% dce_login hpss_ssm -k /krb5/hpss.keytabs
% lshpss -s sfsServer -cos -hier -sc -migp -purgep -dev -drv \
To generate the HPSS configuration information, store it locally in /var/hpss/stats/
lshpss.out, and have it automatically emailed to IBM Houston, issue the following on the
core HPSS server node:
% lshpss.ksh
See Section 12.2.33: lshpss — List Information About HPSS on page 397 of the HPSS
Management Guide for detailed usage and sample output information for lshpss.ksh
The following is a list of lshpss review considerations:
HPSS Installation Guide
Release 4.5, Revision 2
-svr -mvr -acct -logp -locp -ffam -bfs -ns \
-pvr -logd -logc -nfsd -listmeta
Class of Service List
File sizes - Will COS be selected by file size? If so, do the sizes presented make
sense (is there overlap amongst the COS's that can be selected by file size)? Are
some of the COS's so close that, all other things being equal, it would make
sense to combine two or more COS's – or does one COS have such a large file
size range that it would make sense to split it into two or more COS's?
Stage Code - For the standard disk-tape hierarchy, is the stage code set to
anything other than "stage on open"? If so, what are the reasons for doing so
(e.g., if "no stage" a good reason is that large files will only be read back once,
but don't want those to compete for new files in the disk cache)? Especially
need to make sure all understand the ramifications of background or async
staging.
Flags - Normally RWA are on – if not, why? If 'F' is on, means that this COS
can only be selected by explicitly naming it (not via other create-time hints –
like file size) – is that desired? Verify the "enforce maximum file size" setting
matches desired intent.
Hierarchy List
Hierarchy Layout - Verify that the hierarchy levels make sense – tape or disk
only hierarchies are what is really desired. Any hierarchies with multiple
levels are correctly set up (need to check migration policy to ensure that the
copy count stuff is set correctly).
September 2002
Chapter 3
System Preparation
197
Advertisement
Table of Contents
