Benutzeranleitung / Produktwartung HPSS des Produzenten IBM
Zur Seite of 311
HPSS Installation Guide High Performance Storage System Release 6.2 July 2008 (R evision 2.0) HPSS Installation Guide July 2008 Release 6.2 (Revision 2.
© Copy right (C) 1992, 2008 I nternational Business M ach ines Corporation, The Regen ts of the University of California, Los A lamos National Security, LLC, Lawrence Li vermore National S ec urity , LLC, Sandia Corporation, and UT-Battelle. All rig hts reserved.
Ta ble of Cont ent s Chapter 1. Release 6.2.................................................................................................... ... .... 15 1.1.New Fea tures..............................................................................
2.3.3.HPSS Storage Subsys t ems ................................................................................................. ... .... ... .... ..44 2.3.4.HPSS Infrastructure ........................................................................
3.4.2.3.STK L40, STK SL500, STK SL8500............................................................................. .... ... .... ..63 3.4.2.4.STK.........................................................................................................
3.7.6.6.SCSI PVR.................................................................................................................... .... .... ... ...88 3.7.7.Mover ......................................................................................
3.10.4.File Families................................................................................................................................. ..112 3.11.HPSS Performance Considerations........................................................ ..
5.1.4.Installation Target Directory Preparation................................................................. .... ... .... .... ... .... .136 5.2.Ins tall Prerequisite Software.......................................................................
Chapter 6. Upgrading to HPSS Release 6.2 ....................................................... ... .... .... ... 179 6.1.Special Instruc tions for Upgra ding to HPS S 6.2.2.................................. .... ... .... .... .... .179 6.2.Planning for the HPSS 6.
6.3.16.Enable DB2 Backup..................................................................................................................... .215 6.3.17.Perform the DCE Export: hpss_dce_export..........................................................
D.6. Transfer Age nt Stanza.................................................................. .... .... ... .... .... .... ... ..287 D.7. Stanzas Reserved for Future Use ............................................................... .... .... ... ...
Lis t of F igur es Figure 1. File Migra tion and Stage Operations..................................................... ... .... .... ..37 Figure 2. Class of Service / Hierarchy / Storage Class................................................. .... ..38 Figure 3.
Lis t of T able s Table 1. HPSS Client Interface and Mover Platforms.......................................................49 Table 2. Supported Platform/Driver/Tape Drive Combinations...................... .... .... .... ... .64 Table 3. Cartridge/Drive Affinity Table.
Pre fa ce About thi s book The HPSS Installation Guide is for use both a t sy s tem insta llation time as well as throughout the lifeti me of the s y ste m . It will guide sy s tem administra tors through the planni ng and instal lation of a new HPSS system.
Cha pte r 1. Re leas e 6. 2 This chapter sum marizes HPSS changes for Release 6.2 into four categories: new feature s, retired features, deferred features, and changed features. Changes since release 4.5 and 5.1 are described. 1.1 . New Fe atu re s This section describes the new HPSS feat ures added to Release 6.
• Storage Clas s (but not subsystem-specific storage class options) • Global c onfiguration • Accounting policy • Location policy • All server configuration. Newly supported options include Cor e Server, Gatekeeper, Location Server, Log Daemon, Migrati on/Purge Server, PVL, all P VRs, and SSM.
1.1 .1 2. Dr ive Poo ls HPSS provides HPSS end clients the abili ty to direc t tape read I/O requests to a prede fined group of tape drives referred to as a Drive Pool. This abilit y helps HPSS administr ators m anage tape dri ve scheduli ng and thus avai labilit y .
1.1 .1 8. Move r Enh an cem ent Multipl e Movers for one or more HPSS ins tances can now be configur ed to run on the same machine. The - c <alternat e var path> flag is added to the Mover entry in the inetd c onfiguration file to specify an alter nate "/var/hpss" path to be used by the Mover.
Core Server's mem o ry image • Modifie d the DMG table. In support of the new HPSS RPC l ibrary, the TCP port was eliminate d and the Program and Version num b ers were added to DMG speci fic configuration. • Modifie d the DMGFILESET tabl e. The TCP port was eliminated and the TCP hostname and RPC endpoint information was added.
files y st ems do not support mirrored namespaces, f ields which were specif ic to m anagi ng mirrored fi lesets are also no longer availabl e. This includes the fol lowing configurati on options: · .
1.4 .4 . SSM C han ges Significant changes were m ade in SSM between Rele ases 4.5 and 5.1 and again bet ween 5.1 and 6.2. For the reader's convenience, all changes between 4. 5 and 6.2 are summarized in Section 3.3. 4.1: Changes Aff ecting Sites Upgradin g Directl y from 4.
Changes since 4.5 Server GUI ADM The SSM client scripts now use an int ernal poll ing mechanism for getting window updates (as opposed to being notified of the upda te by the server) .
Changes since 4.5 Server GUI ADM The SSM client scripts can use ports exempted by the network administrato r as fi rewall exc eptions. See the -n option on the hpssadm/hpssgui man pages. The port on which t he Sy st em Manager will lis ten may be controll ed by setting the $HPSS_SSM_SERVER_LISTEN_PORT environment variabl e.
Changes since 4.5 Server GUI ADM The abil ity to se e which users are logged into SSM, referred to i n HPSS 4.5 as a li st of SSM "consoles", is availa ble in 6.2 as part of the System Manager Stat istics window from both t he hpssgui and hps sadm .
Changes since 4.5 Server GUI ADM Column ordering is now controlled by dragging columns to the desired location. The modified order i s preserved aut om at icall y in the user prefer ences across hpssgui restarts. n When messages have been written to the sta tus bar, the most recent messages can be viewed in the st atus bar's toolt ip.
Changes since 4.5 Server GUI ADM The HPSS 4.5 hpssadm com mands • pvr_cartridge • pvl_volume • ss_pv • ss_map • ss_vv have been replace d by a single com mand "volum e ".
Changes since 4.5 Server GUI ADM The hpssad m config comm and now supports the addit ional structures: • Class of Service Confi g • Storage Clas s (but not subsystem-specific storage class options.
Changes since 5.1 Server GUI ADM Options to the hpssgui and hpssadm startup scripts have changed significa ntly . See the man pages for details. Following are som e highlights: n n The scri pts are dependent upon an ssm configurati on file (ssm.conf), cre ated by mkhpss, which cont ains some sit e-specific configurati on values.
Changes since 5.1 Server GUI ADM The SSM client script options f or connecting to the System Manager across a Virtual Private Network connection (VPN) have changed.
Changes since 5.1 Server GUI ADM The m enu bar has been reorganized sl ightly. The "Data Server Sta tistic s" menu item has been replace d by the "System Manager Stat istics " menu item, availabl e from the M onitor->SSM Information menu path.
Changes since 5.1 Server GUI ADM The m echani sm for sel ecting columns to be displa y ed in e ach list window has moved from the lis t's Preferences window to the "Column View" m enu of the list window itself. See the des cription of the "Col umn View" menu item in Secti on 3.
Changes since 5.1 Server GUI ADM Since SSM now represent s the three Core Server volum e struct ures as a single st ructure, the types specif ied t o the hpssad m v olume comm a nd have changed. The 5.1 types: • Disk Storage Map Inform ati on • Disk Phy s ical Volume Information • Disk Virtua l Volu m e Inform ation have been repl aced in 6.
Changes since 5.1 Server GUI ADM A new subcommand “update” has been added to the hpssadm device comm a nd for updat ing the mover device and pvl drive objec ts.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 34.
Cha pte r 2. HPSS Bas ics 2.1 . In tr odu ct ion The High Performance Storage Sy st em (HPSS) provides hierarchic al stora ge m a nagement and services for very large storage environments.
2.2 .4 . Ba sed o n S tan da rd Co mpo nen ts HPSS runs on UNIX and is written in ANSI C and Java. It uses remote proc edure call s, a sele ctable securit y service (Ker beros or UNIX), UN I X or LDAP for user configuration information, and DB2 as the basis for it s portable , distribu ted, t ransaction-base d architec ture.
2.3 . HPS S Com pon ent s The com pone nts of HPSS include files, f ilesets, juncti ons, virtual volumes, phy sica l volumes, stor age segments, metadata, servers, inf rastructur e, user interface s, a management interfa ce, and policies.
Figure 2. Class of Service / Hierarchy / Storage Class 2.3 .1 . HPS S Fi les, File se ts , Vo lum es, Sto ra ge Se gme nt s and Re lat ed Me tada ta The various metadata constructs used to descr ibe t he HPSS namespace and HPSS storage are describe d below: • Files (Bitf ile s) .
recorded on these t apes. HPSS support s grouping fil es on tape volum es only. Families can only be specifi ed by associ ating the family with a fil eset. All files created in the fi leset belong to the family . When one of these files is m i grated fr om disk to tape, i t is rec orded on a t ape with ot her files in the s am e family .
• Class of Service (COS) . Each bitfile has an at tribute called Class Of Service. The COS defines a set of parameters as sociated with operati onal and performance chara cterist ics of a bitfil e. The COS results in the bi tfile being stored in a storage hie rarchy sui table f or its anticipa ted and actual s ize and usage charac teristi cs.
consisti ng of direct ories, files, and links. These name space obj ects m a y exist withi n files ets that are connected via juncti ons. Second, t he Core Server provides the abs traction of logical bitfil es to i ts client s. A bitfil e is identifi ed by a Core Server generated nam e cal led a bitf ile ID .
The purpose of t ape file m igr ation is to make an additiona l copy (or multipl e additi onal copies) of a file , in a t ape storage cl ass, to a lower level i n the hierar chy . It is also possi ble to move files downwards instead of copy i ng them.
• Physical V ol um e Repository (PVR) . PVRs manage HPSS cartr idges. Though an HPSS sy s tem may contain m ul tiple PVRs, each cartridge is m anaged by only one. PVRs provide APIs for clients to request cartridge mounts and dis m ount s and quer y the status of cartri dges.
2.3 .3 . HPS S Sto ra ge Su bsy st em s The goal of storage s ubsy st ems (or j ust “subsy st ems”) is to increas e the scalabili ty of HPSS by allowing multipl e Core Servers to be used within a single HPSS system. Every HPSS sy ste m is partiti oned int o one or m ore subsystems.
HPSS Core Server performs most of the HPSS m et adata changes using the transacti on managem ent tools provided by DB2. For t he m ost pa rt, these metadata t ransaction s are managed entirel y within the Core Server.
HPSS. A delog functio n is pr ovided to extr act and f orm at log records from a central or archived log file. Delog opti ons support filter ing by time interval , record t y pe, server, and user.
GUI. The hpssgui simplifie s the m a nagem e nt of HPSS by organizing a broad range of technical data into a series of easy - to-read graphic di splays. The hpssgui all ows monitoring and cont rol of virtually all HPSS processes and resources from windows that can easil y be added, delet ed, moved, or overlapped as desired.
HPSS provides faciliti es for rec ording infor m a tion about authenti cation and object (file/ directo ry ) cr eation, deletion, access, and authorization events. The securit y audit polic y for each server deter m in es the records t hat each individual server will gener ate.
The following matrix il lustrat es which platforms support HPSS interfa ces. Tab le 1 . H PSS C lie nt I nt erf ace and Move r Pla tf orm s Platfor m PFTP Client Client API HPSS Mover HPSS VFS Client FTP Clients IBM AIX X X X Any platform running standard FTP cli ents.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 50.
Cha pte r 3. HPSS Pla nn ing 3.1 . Ov er vie w This chapter provides HPSS planning guidelines and considerat ions to help the adm i nistrat or effective ly plan, and m ake key decisions about, an HPSS system.
Figure 4. HPSS Generic C onfiguration 3.1 .2 . HPS S Con fig ur at ion Plan nin g Before beginning the planning process, there is an im p ortant issue to consider. HPSS was designed t o optimize the transfer of large fi les at the expense of some small file transfer performance.
aggregate the indi vidual fi les into large individua l files before moving them into the HPSS name space. The following planni ng steps must be carefull y considered for the HPSS infr astructur e confi guration and the HPSS configuration phases: 1.
more information about conf iguring families. • Plan f or filesets and ju nctions, if any. Refer to Chapter 10: Filese ts and Junct ions in the HPSS M anagement Guide for more infor m ati on. • Plan f or HPSS storage cla sses. Refer to Section 3.10.
3.1 .4 . HPS S Ope rat io na l Pla nni ng The following planni ng steps must be carefull y considered for the HPSS operat ional phase: 1. Define the site guidelines for the HPSS users and SSM users.
guide that the HPSS support /deploym e nt team uses to m onit or and check the progress of an install ation. 3.2 . Req uir eme nt s an d Int en ded U ses f or HP SS This section provides some guidance for the administ rator to identif y the sit e’s require m e nts and expectat ions of HPSS.
3.2 .5 . Dup lic at e Fi le Po lic y The policy on duplicat ing user data fil es impacts t he amount of data stored and the amount of da ta moved. If all user fil es are dupl icated, the system will require twice as m uch tape stor age. If users perform thei r own duplica tion of files, the system m ay consume a sm al ler am ount of storage space.
authenti cation and authoriz ation (subj ect to certain caveats – See FTP documentat ion for details). The pftp_clien t binar y m ust be built using the di stribute d source code. However, it is the si te's responsi bility to obtain the necessar y Kerberos com po nents.
If UN I X authentica tion will be used, this product is not required. 3.3 .1 .3 . LDA P and I BM Ker ber os HPSS can be configured to use an LDAP director y to store its aut horization information such as users' names, UIDs, GID s, and hom e directo ries.
• IBM ATL: atl dd.driver 6.5. 2.0 and Atape.driver 10.2.8.0 (if planning to control the IBM tape librar y and drives from this node) 3.3 .2 .1 .2 . Lin ux R equ ire men ts Each Linux server node mus.
• 1 GB RAM 3.3 .2 .2 .3 . Sol ari s Re qu irem ent s Each Sola ris Mover node m ust have the following prere quisites: • Solaris UltraSPARC bas ed processor • Solaris 8+ (32-bit or 64-bit) • C compiler: Forte Developer 7 C 5.4 2002/03/ 09 (if planning to rec ompile Mover code) 3.
• xfsdump-2.2.25-0.2 or higher • xfsprogs-2.6.25-0.2 or higher 3.4 . Har dwa re Co nsid er at io ns This section describes the hardware infrast ructure needed to operate HPSS and includes consider ations about infrast ructur e instal lation and operati on that m ay impact HPSS.
• STK SL500 and SL8500 • STK Tape Librari es t hat support ACSLS • ADIC i500 • ADIC A M L (supported by special bid only) 3.4 .2 .1 . IBM 3494 The 3494 PVR supports Ethernet and RS-232 (TTY) attache d robots. If appropriatel y configured, multiple robots can be accessibl e from a si ngle node.
9840C drives should not be used in conjunction with ei ther 9840A or 9840B drives. Tab le 2 . S up por ted Pla tfo rm /Dr ive r/T ap e Dr ive C ombi na tio ns Platform Driver Device(s) AIX IBM 3580 (G.
(LTO) Gen4 drive can rea d 3580 (LTO) Gen4, 3580 (LTO) Gen3, and 3580 (LTO) Gen2 cartridges, but can only write 3580 (LTO) Gen4 and 3580 (LTO) Gen3 cartridges ), HPSS will m ount a 3580 (LTO) Gen2 car.
Tab le 3 . C artr id ge /Dri ve A ffi nit y T abl e Cartridge Ty p e Drive Pr eference List AMPEX DST-312 AMPEX DST-312 AMPEX DST-314 AMPEX DST-314 AMPEX DST-314 Single-Length 3590 Single-Length 3590 .
3580 (LTO) Gen 4 3580 (LTO) Gen 4 3592 J1A Short Tape 3592 J1A Standard Ta pe 3592 J1A 3592 EO5 3592 EO6 3592 EO5 JJ Short Tape 3592 EO5 JA Standard Ta pe 3592 EO5 JB XL Tape 3592 EO5 3592 EO6 3592 EO.
Fibre Channel. For these devices, operating system disk part itions of the desired size m ust be crea ted (e.g., AIX logical volume or Linux/Solaris /IRIX disk partition ), and the raw device name must be used when c reating the Mover Device configurat ion (see Section 7.
Starting with HPSS 6.2 t here are many enhancements to the st orage sy stem to take advantage of Storage Area Networks. Though sepa rated in Figure 4, in rea lity there is usual ly only one SAN at an install ation and all the resources are att ached t o it.
Figure 5. Basic HPSS Metadata & Filesystem Allocation On the left hand side of the diagram , the raw phy si cal volum e s are shown attached to the disk array controll er.
mirrored log components will nee d to be deter mined by HPSS and the customer based on transacti on performance requirements. Potentiall y , disk res ources primarily alloca ted for HPSS disk cache can be used or the sit e m ay want to dedicate a second dis k array for thi s purpose to prevent any possible interfer ence.
to creat e a sit e policy conf iguration file, usual ly named /var/hpss/ gk/gksit epolicy . The size of this file depends on the si te-im pl emented gat ekeeping policy. If the Gatekeeper Service is not used, ther e is a m i nimal amount of di sk space used i n this dire ctory.
3.5 .3 .7 . /db 2/ ba cku ps /s ub sys 1 & su bs ysX Similar t o /db2/backups/ cfg , the /db2/backups/ subsys1 filesystem temporaril y stores backup images of the subsy st em archived logs and database as the y are generated.
Section 5.3.1.2: Instal l HPSS Documentat ion and DB2 Software on page 141. The t ables and i ndexes are separa ted i nto separate logical volum es /partit ions to ease futur e expansio n of t he database and to maxim i ze performance of databas e operati ons.
disk devices. The “6.2 Sizing Spreadsheet” input tab is shown below. Based on the input, the resulti ng output is show below: HPSS Installation Guide July 2008 Release 6.
Definiti ons for the DB2 table s are as follows: Bitf ile Disk Allocatio n Maps . (BFDISKALLOCREC) For each bitfi le stor ed on disk, one or more rows will be created in the Disk Allocation Maps t able.
by t es. Disk Storage Segments . (STORAGESEGDISK) Expect t he size of the disk storage segm ent metadata table to be quite vola tile. As f iles ar e added to HPSS, disk storage segments will be creat ed, and as fil es are m igr ated to tape and purged from disk, they will be deleted.
created will r equire appr oximately 10MB of disk space in a files y ste m that should be used only for database home directori es and other DB2 home direct ories (such as the DB2 Adm i nistrat ion Server and Fenced User).
The am ount of memory for nodes running HPSS Movers, and no DB2 servers, is dependen t on t he number and t y pes of devices configured on the Mover node, the expected usages of those devices, and the configuration of the M overs .
Class of Service and Accounting Code i nform ation. In addition, the chgrp , chmod , and chown comm a nds are supported as quote site options. The FTP daemon is bui lt on top of the Cli ent API and m us t be r un on a node that supports Kerberos clients.
3.7 .1 . Cor e Ser ver The Core Server is responsible for managing the HPSS name space (files , directori es, li nks, etc.), bitfil es, and storage (physical volumes, virtual volumes, etc. ) for a single subsystem. Each of these areas of responsibi lity are outlined in greater detail be low.
Figure 6. The Relationship of Various Server Data Structures Disk Stor age Allocati on Each Core Server manages disk storage units for HPSS. It m aps each disk stora ge unit ont o an HPSS disk Phy s ical Volume (P V) and recor ds configurat ion data for the PV.
The Core Server is designed to sc ale up its abilit y to m anage tapes as the number of tapes incr eases. As long as suffi cient m e m or y and CPU capaci ty exist, threads ca n be added t o the server to increase its thr oughput. Additio nal subs y ste ms can also be added to a sy s tem, increa sing concurr ency even further.
metadata updates and can impose extra overhead on DB2. Als o, unpredictab le purge behavior may be observed if the purge recor d ordering is changed with existing purge rec ords in the sy s tem unti l these existing records are cleared. A purge run ends when either the supply of purge records is exhausted or the purge t arget is reache d.
Sites can choose to configure z ero (0) or more Gatekeepers per HPSS system. Gateke epers are associat ed with storage subsystems. Eac h storage subs y ste m can have zero or one Gatekeeper associat ed with it and each Gatekeeper can support one or more storage s ubsy st ems.
requests from a particu lar host or user. The Site Interfaces will be locat ed in a shared librar y that i s linked int o the Gatekeeper . It is important that the Site Interf aces return a status in a timely fas hion.
PVL. It is poss ible for m ul tiple HPSS PVRs to m anage a single robot . This is done if it is necessary to organize the tape dr ives in the robot into partiti ons. Each tape drive in the robot is assigned to exactl y one PVR. Addition ally, each cartridge is assigned to only one PVR.
3.7 .6 .3 . 349 4 PVR The 3494 PVR can manage an IBM 3494 tape robot att ached via Ethernet or SCSI. The PVR will create a process to receive asy nc hronous notific ations from the robot. At least one PVR should be creat ed for ever y robot m a naged by HPSS.
3.7 .7 . Mo ver The Mover configuration is largel y dictated by the hardware configuration of the HPSS s y st em. Each Mover can ha ndle both disk and tape devi ces and must run on the node t o which the storage devices are att ached.
Driver has a built-in confi guration t able for all HPSS supported tape drives. This configurat ion provides vari able block size for most HPSS supported drives. In order to override the built-in configurati on, device information can be supplied in the /dev/kernel /st.
HBAs with a 7000 series chip set, uncomm ent the foll owing lines in the " .config " file and follow the procedure for rebui lding your Linux kernel . CONFIG_SCSI_AIC7XXX=y CONFIG_AIC7XXX_CMDS_PER_DEVICE=253 CONFIG_AIC7XXX_RESET_DELAY_MS=15000 3.
3.7 .9 . St art up D aem on The Startup Daemon is responsible for star ting, monitoring, and stopping the HPSS servers. The Daemon responds only to requests from the SSM Sy ste m Manager. It shares responsibil ity with each HPSS server for ensuring that only one copy of the server runs at a given time.
values may need to be overridden in env.conf. Key SM Envi ronment Variabl es Variable Default Value Functionali ty HPSS_SM_SRV_CONNECT_FAIL_COUNT 3 Connection Fail Count: number of connecti on failur .
Variable Default Value Functionali ty HPSS_SM_SRV_MAX_C ONNECTIONS 50 Num b er of HPSS server connection s to maintain at once. If this num ber of connecti ons is exc eeded, the n old connecti ons will be closed to m a intain this num ber of connecti ons * The SM attempts to throttl e the connection attempts to other servers.
Disk m i gration is control led by several parameters. By de fault, these par am et ers a re the same a cross all subs y st ems. However, subsystem-specific policie s may be created which override all of these values. For a list of these para meters, refer to Sect ion 6.
storage cl ass by periodi cally extract ing thi s information from the HPSS Core Server. Based upon parameters in the purge policy, a purge run will be st arted when appropriate.
out of the hpssGECOS fiel d, it does not exist in UNIX. It only exists in LDAP. The m et adata for each fil e and di rectory in a n HPSS sy s tem contai ns an Account field, which determines how the stora ge will be charged. Each user has at least one defa ult account index, which is put into the Account fiel d of all new files and direct ories .
the princi pal's LDAP hpssGECOS at tribute, then Site-st y le accounti ng will be used. Otherwise UNIX- s ty le account ing will be used. To keep t he accounting information cons istent, it is im por tant to set up all users in the HPSS Authorizati on services with the sam e style of accounting (i .
3.9 .4 .5 . Se cur ity Aud it HPSS provides the abilit y to record information a bout authent ication, file creation, deletion, access, and authoriz ation event s. The se curity audit polic y in each HPSS server determines what audit records a server will generate.
Gatekeeper configured in its storage subsy s tem. If one is found, the Cor e Server asks the Gatekeeper for its monitor types by cal ling the gk_GetMoni torTypes function which cal ls the loc ally implemented gk_sit e_GetMonit orTypes funct ion which determines which types of requests t o monitor.
DOWN or when the user a pplicatio n is abort ed. NOTES: 1. All open requests to t he Core Server wil l call the Gatekeepi ng Service open API ( gk_Open ). This incl udes opens that end up invoking a stage. 2. Any stage cal l that is invoked on behal f of open will NOT ca ll the Gateke eping Service stage API ( gk_Stage ).
(VVs). Each VV contains one or more PVs. The VV character istic s descri bed by a Storage Clas s include the VV Block Size and VV Stripe Width. If PVs are grouped one a t a time, so that their Stripe Width i s one, they are still defined as VVs. A number of addi tional parameters ar e defined in Storage Cla sses.
SSM provides the capabil ity to defi ne stora ge classes and to add and delete virtual volumes to and from the def ined stora ge classes. A storage clas s is identi fied by a storage class ID and its as sociated attribut es. For detailed descripti ons of each attribut e as sociated with a storage class, see Section 6.
utilit y programs copy data fro m one tape VV to another, so the number of available tape drives of the appropria te t y pe m us t be at least twice the tape Stripe Width, for thes e programs to functi on.
strea m ing to maxim i ze performance. For recommended values for various m edia types, see Section 3.10.1.12: Some Recommended Paramet er Values for Supporte d Storage Media on page 106. 3.1 0. 1. 6. Mi nim um St or age Se gme nt S ize S ele ct ion (di sk on ly ) The Core Server maps disk fil es onto a series of disk storage segm ents.
3.1 0. 1. 8. Ma xim um VV s to Wr it e (ta pe on ly) This parameter res tricts the number of tape VVs, per Storage Class, that can be c oncurrentl y written by the Core Server. Its purpose is to minimize the number of tape mounts and to limit the number of tape VVs being wri tten, to prevent files from being scatter ed over a num ber of tapes.
3.1 0. 1. 12 .1. Dis k Me dia Pa ram ete rs Table 7 contains attribut es settings for the supported disk storage m edi a types. Tab le 6 . S ug ges te d Blo ck S ize s for D isk Disk Ty pe Media Block.
Tab le 7 . Sug ge ste d Bl ock S iz es fo r Tap e Tape Ty pe Medi a Block Size Blocks Between Tape Marks Estimated Physica l Volume Size Am pe x DST-312 1 MB 1024 50, 150, 330 GB Am pe x DST-314 1 MB .
StorageTek T10000A 256 KB 2560 500 GB StorageTek T10000B 256 KB 2560 1000 GB In the above table: • Media Block Size is t he block size to use in the St orage Class definition. This is the size of the data blocks written to tape. Note that f or tape device s, the Mover configuration does not contain the Media Block Size.
3.1 0. 3. Cl as s of Se rv ice Each HPSS fi le belongs to a single Clas s of Service (COS) which is selected when the fil e is creat ed. It is select ed via Class of Service Hints infor m at ion pa ssed to the Core Server when the bitfil e is created.
guaranteed that the file is completely and successfull y staged before it is read. If the stage operat ion fails, the open wi ll return with an error. Guideline 3: Select the Stage on Open Asy nc option if y ou wish to stage the enti re fil e to the top level i n the hierar chy and do not want the Clie nt API open to block.
Latency fi eld from the Storage Class at the t op level in the hierarc hy . 3.1 0. 3. 6. Se lec ti ng T ra nsf er Ra te This field can be used via t he COS Hints mechanism t o affect COS selection.
· Maximum users and applicatio ns connect ed to DB2 · Nature of usage: read or update • Database logging · Hardware or software m i rroring · Disk speed and reliabil ity: sel ect the fastest, mo.
directl y to tape, the buffer size used by the FTP server and the virtual volum e block size def ined for the Storage Class bei ng written to will have a significant im pa ct. If the buffer siz e used by the FTP server is not a multiple of the virtual volume block size, each buffer written will resul t in a distinct storage se gm ent on the t ape.
3.1 1. 5. Cl ien t AP I The Client API provides the capabilit y to perfor m data transfer of any size (the size being param e ters supplied by the client to the read and writ e inter faces). The size of the data transfers can have a significa nt impact on the performance of HPSS.
stage reque sts. The site policy could li mit the maximum num be r of non-Authorized Caller requests allowed at once by either dela y ing or denying partic ular reque sts. To delay the request, the site policy may return a spe cial re try status along with the num ber of seconds to wait before the Client API retries the reques t.
3.1 2. HP SS M eta dat a Bac ku p Con sid er at ion s This section contains guidelines for proper maintena nce of t he HPSS metadata stored in DB2. The polic ies descri bed should be fully understood and implemented to protect the HPSS metadata. Failure t o follow the se polici es can le ad to unrecov erable data loss.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 118.
Cha pte r 4. Sy ste m Pr epar at ion This section covers the st eps that m ust be taken to appropriat ely prepare y ou r system for installat ion and configurat ion of HPSS and its inf rastructur e. • General setup (Sect ion 4.1) • Setup f ilesystems (Secti on 4.
• Configure the Perl pre requisite software on HPSS nodes. • Configure the SSH prerequisi te software on the core HPSS server node (at a minimum ) and configure SSH to accept connections from IBM Houston. Include the Houston subnet IP addresse s 192.
/db2/mirror-backups/subsys1 4.2 .2 . HPS S Fi lesy s tem Configure /var /hpss as a separate file sy s tem on each HPSS server node. Thi s fil esy s tem will store HPSS configurat ion fil es, log file s, MPS reports, and other HPSS related files. It is recommended that this fil esy stem be at least 1GB in size.
(SMC) l ibrary device on the node tha t will run the HPSS LTO PVR, and verif y that it i s operation al. To configur e the l ibrary: root% cfgmgr root% lsdev -Cc tape | grep smc smc0 Available 40-58-0.
To star t the lmcp daemon: root% /etc/methods/startatl To test whether lmcp daemon is configured and working correctly: % mtlib -l<lmcpDevice> -qL where l mcpDevice is usually /dev/ lmcp0 .
For AML ta pe librarie s: • If using an AML PVR, configure the Insert/Eject ports using the configur ation fi les /var /hpss/ etc/AML_Ejec tPort .conf and /var/hpss /etc/A ML_InsertPo rt.conf . Refer t o Section 5.2.8.3: AML PVR Specific Configurati on of the HPSS Management Guide for m ore information.
To measure read perfor mance on drive r mt1 using the previously-written unco m pre ssed and compressed files: % iocheck -r -t 20 -b 1mb /dev/rmt1.1 % iocheck -r -t 20 -b 1mb /dev/rmt1.1 To unload a tape: % tctl -f <device> rewoffl Repeat the above steps for each tape drive.
4.4 .3 . IRI X On each Tape Mover node, verify that ea ch tape drive has the vari able-length block size opt ion enabled. To deter mine if t he variable block size option is enabled, the foll owing sh.
4.5 .1 . AI X • Verif y that the correct num ber and t y pe of disk devices are availabl e on each DB2 and Disk Mover node. The disk devices sect ion of t he lsnode report displa y s all available disk devices.
Use the iocheck.ksh sc ript fr om the deploym en t tool s package to show t he performance of one or more i ndividual disk devi ces and the peak aggreg ate perfor mance of concur rent I/O across m ult iple disks (e.g., to show the peak perfor m anc e of adapters).
4.6 . Se tup N etw ork P ara me ter s • Install and configure all network interf aces and correspondi ng network connection s. Refer t o IBM' s internal network technol ogies home page for resources on configuring and tuning networks and TCP/IP.
will be used. For Linux, a similar change should be made t o /etc/nssw itch.con f : hosts: nis dns files • For each AIX ethernet net work interface, verify that the en0 a nd et0 interf aces a re not both configured at the sa m e time (we reco m mend only using en0 unless the other nodes in the network are all using t he 802.
... ccs0 64k 64k On -- -- ccs0 64k 32k On -- -- ... You are l ooking for the best values possi ble for each network connecti on. Thes e values will be used by H PSS to optimize i ts data transfers. This e xam pl e is , by no m eans, a complete picture of what c ontrols net work performance.
udp_recvspace Controls the default size of the receive buff er for UPD/IP sockets. A value that is too small can cause server RPC sockets to be overrun. tcp_recvspace, tcp_sendspac e Controls the default size for the recei ve and send buffers for TCP/IP sockets.
4.6 .2 . SP /x Sw it ch D evi ce Bu ff er Dr iv er Bu ff er Po ols IBM SP/x systems provide the capabili ty to tune the buffer pool allocat ion i n the switch device driver. Two variables can be changed: rpoolsize, which is the size of the buffer pool for incoming data, and spoolsize which is the buffer pool size for out going data.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 134.
Cha pte r 5. HPSS Ins ta lla ti on and In fr ast ru ct ur e Con fig ur at ion This chapter provides instr uctions and supporting information f or installi ng the HPSS prerequisite software, the HPSS and DB2 software from the HPSS distri bution m edia , and perf orming the HPSS infrastr ucture configurati on.
Tab le 9 . In st all at ion Pa cka ge S ize s an d Dis k Req uir eme nt s Platfor m HPSS Package Nam e Package Size /opt/hps s Space Requirement s Package Descripti on AIX HPSSServer-6.2.0.0.lpp < 65MB 450 MB All HPSS Com pon ents HPSSClientMover-6.
• The disk, where the installa tion tar get director y resides, has enough space to hold all the HPSS packages to be installed on this node. • WARNING: Do not use NFS mounted directories for i nstalling nor allocati ng space for HPSS related components.
If UNIX authori zation will be used, this product is not required. LDAP authoriza tion is supported on AIX only. If LDAP will be use d for HPSS authori zation, download the IBM Tivoli Direct ory Server from http:/ /www.ibm.com. Search for "IBM Tivoli Direct ory Server" on the site to find the download page.
XFS uses the Linux udev daem o n to dynamicall y configure the DMAPI de vice node. Use the chkconfig comm a nd to make sure t hat boot.udev i s "on". Note that i f a change is required, then the machine needs to be reboot ed in or der for i t to take eff ect.
5. From the "Root Subsystem Machine " submenu, cli ck on the 'Pre-Ins t all Config' icon i n the left panel. mkhpss will display the following screen: 6. Veri fy that the default values are correct for the given inst allati on and modify if necessary.
scripts to verify/cre ate the 'hpss' account and group, se tup the /var/ hpss (defaul t locat ion) director y with the required subdirectori es and initiali ze the HPSS environ m e nt file , env.
DB2 software will be installed in the /usr/opt/db 2_08_01 ( AIX) or /opt/IBM/db2/v8.1 (Linux) directory. 2. For 6.2. 0, the HPSS software and docu m ent ation should alrea dy be install ed accordi ng to the install ation step in section 5.3.1.1. Installing from CD will be an opti on starting in 6.
% su - % cd /usr/opt/db2_08_01/adm % ./db2licm -a <path name to the DB2 generic license file> The generic DB2 lice nse fil e (*/db2/li cense/db2e se.lic) can be found on the DB2 Installation CD or image. It can also be obtained b y contacting your HPSS Support Representa tive.
3. Using the scrollbar, move the right-panel displ ay until the "Authorizat ion Servic e" information is seen. It should look like the following: HPSS Installation Guide July 2008 Release 6.
4. Select the "Confi gure Authoriza tion Servi ce" checkbox. Set the "Author ization Service" to "Unix and config files".
configurati on step. Other HPSS util ities are availabl e to a dm ini ster these HPSS configurati on files. See sect ion 2.2.2: Security Mechanisms in the HPSS Management Guide for more inf orm a tion. To use t he HPSS configuration files, select the "Enabl e local Unix Passwd Fil es" checkbox.
• KDC Director y. The pathname of t he KDC director y . This director y should be set to /var/ hpss/krb5kdc. • Master Passw ord. The Kerberos administra tion password. Be sure to remember t his password to be able to administer the Ker beros environment later.
5. Select the "Confi gure Authoriza tion Servi ce" checkbox. Set the "Author ization Service" to "Unix and config files". 6. Review and m odif y (if nec essary ) the following authorization fields: • Local Si te Name. The value is usually set to the full host name of the local host.
8. Select the "Confi gure Server accounts" checkbox to create UNIX accounts for HPSS servers. 9. Click on the "Configure Securit y Services" button at the bottom of the screen to perform the specifie d securi ty configurat ion. 10.
4. Select the "Confi gure Authoriza tion Servi ce" checkbox. Set the "Author ization Service" to "LDAP". 5. Review and m odif y (if nec essary ) the following authenticat ion f ields: • Kerberos Install Path. Th e pathname where Kerberos is ins talled.
• Authenticati on Type. There are two supported options: Keytab Fi le or Password. The Key t ab Fil e option allows HPSS s ervers or uti lities to read a key ta b fil e to authenti cate. The Password option r equires a password to be supplied each time an HPSS server or utility i s invoked.
Unix Passwd Files" checkbox as shown in the example above. The default names for t he files should be used as displ ay e d. 8. Select the "Confi gure Server accounts" checkbox to create accounts for HPSS serve rs.
3. Review and m odif y (if nec essary ) the following fields: • Instance Owner . The nam e of the DB2 instance owner, normally 'hpssdb'. • Schema Nam e . The name of the DB2 schema containing the HPSS metadata table, normally 'hpss'.
• Create Subsy s Database . Sel ect thi s checkbox to cre ate the "subsys1" data base. • Subsyste m Database Ali as . The "real" database is configured as 'hsubsy s1' , while the databa se al ias is the name used by HPSS servers and utiliti es t o reference the database.
B. On the “Tables pace Config” window, set t he Tablespa ce T y pe from the drop down menu. For the USERSPACE1 tablespac e, select “SMS” System Managed Space. For the remaining tablespace entries , selec t Tables pace Type to "DMS" Database Managed Space.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 156.
F. Select the "Add" button to add "raw devices" to Contai ner Path list. The "raw devices" m ust alread y exist. For AIX, the logical volumes must have al ready been cr eated and t he "raw" for m be specified (i.
a variable named DB2_USE_LOCAL_RESYNC set to the value of 'true' when sta rting DB2 in orde r for the aforementioned fileset operati ons to complete successf ully: csh & tcsh: setenv DB2_USE_LOCAL_RESYNC true sh & bash: export DB2_USE_LOCAL_RESYNC=true 5.
4. After exiting mkhpss , verify permissions on the generated fil es. In particular , note the permissions on the keytab fil es. The hpss.key t ab is used by HPSS servers to establi sh credenti als. The mm .ke y ta b is used by hpss utili ty programs.
5.3 .2 . In st all and Co nfi gu re H PSS – S eco nda ry Subs ys te m Mac hin e For the secondary subs y ste m m a chine, the following configuration steps must be performed: • Pre-installa tion C.
3. Veri fy that the default values are as desired. Modify them, if necessary. Cl ick the 'Configure' button to perf orm the pre-instal lation setup.
This panel allows y ou to ins tall the DB2 software, HPSS software (option starting i n 6.2.1), and HPSS documentatio n. Perform the following ste ps to ins tall t he software: 1.
% su - % cd /usr/opt/db2_08_01/adm % ./db2licm -a <path name to the DB2 generic license file> The generic DB2 lice nse fil e (*/db2/li cense/db2e se.lic) can be found on the DB2 Installation CD or image. It can also be obtained b y contacting your HPSS Support Representa tive.
5.3 .2 .5 . Con fig ur e HPS S Sec ur ity Ser vic es This section describes the procedur e to confi gure a Kerbe ros or UNIX Se curity Client on the secondary subs y st em machine. The securit y client m us t match the security mechanism on the root machine.
• Configure server accounts . Thi s checkbox is flagged when the server accounts should be created on the local machine. This is usual ly not require d when the Kerbero s server has already been configured with the HPSS server accounts.
2. Using the scrollbar, move the right-hand panel until you see the foll owing screen: 3. Review and m odif y (if nec essary ) the following fields: • Instance Owner . The nam e of the instance owner HPSS will use. Should use the default value of 'hpssdb' in most cases.
• Authenticati on Type . Curre ntly there is only one authenticat ion t y pe allowed. • User Name . The UNIX userid to be used f or DB2 authenti cation. This userid must have a valid UN I X account bef ore running thi s configurat ion option. • Passw ord and Verify Passw ord .
"Configurati on" icon and then the "Other Services" ic on. The following window wil l be shown: 2. Click on the "Configure Other Servic es" button to complete the configura tion of t he Secondary Subsystem Machi ne.
Source Tr ee t o obtain t he source code from the root machine and i nstall on the Mover/Cl ient machine. 5.3 .3 .2 . In st all Con figu ra tio n Bu nd le The configuration bundle is created on the root subsy s tem and cont ains confi guration files use d by the root, Mover/Client and subs y st em machines.
/opt/hps s/config/ <HPSS configurati on scripts > /opt/hps s/stk/<STK fi les> /opt/hps s/src/< HPSS source files> Included only if t he hpss-src package is installe d.
bundle t he HTML f iles for delivery to t he hpssgui host m achi ne. The recommended instal lation location for t he HTML fi les on each hpssgui host i s /var/hpss/d oc for AIX and Linux platforms and c:hpssdoc for Windows platforms. 5.5 .2 . Ma nua l Page Se tu p Perform the following steps to set up HPSS manual pages: 1.
wishing to learn more about DB2 tuning are ref erred to the HPSS DB2 Tuning Guide , avail able fr om y ou r support represe ntative, the DB2 Administ rative Guide: Perf ormance , availabl e on-line f rom the IBM DB2 website, t he IBM DB2 Tuning Redbook , and the many IBM and after-market books available on this subject.
Makefile.macros: BUILD_PLATFORM = AIX BUILD_TOP_ROOT = /opt/hpss KRB5_AUTH_SUPPORT=on UNIX_AUTH_SUPPORT=on LDAP_AUTH_SUPPORT=off GSI_AUTH_SUPPORT=off CONVERSION_FROM_45 = off CONVERSION_FROM_51 = off .
1. Log on as hpss. 2. Change dir ectory to /opt /hpss/bi n. 3. Run the following command: % hpss_db2_bindall.ksh 5.8 .2 . Con st ru ct a nd Bui ld t he HPS S Mo ver/ Cl ien t S our ce Tr ee This section describes the procedur es to ext ract t he Mover/Client code from the HPSS base sour ce tree and to build the Mover/Cli ent binaries.
5.8 .3 . Con st ru ct a nd Bui ld t he HPS S HDM Sou rc e Tre e XFS is not supported in HPSS 6.2. XFS refe rences have been l eft in the HPSS documentati on to support the option of re- enabling XFS in future releases.
Unix authe nticati on with LDAP aut horization is not suppor ted at this ti m e, so it only m ake s sense t o do this if y o u ar e using Unix aut horization.
serverinterfaces where server_id = (select server_id from server where desc_name = 'SSM System Manager') and descriptive_name = 'Administrative Client Interface' AUTHN_MECH_SET_NUM_MECHS AUTHN_MECH_SET_MECHS1 ------------------------ --------------------- 1 0 1 record(s) selected.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 178.
Cha pte r 6. Upg rad ing t o HPS S Rel eas e 6.2 This chapter is only intended for site s upgrading HPSS fro m either version 4.5 or 5.1 to versi on 6.2. Sites wishing to upgrade from prior HPSS rel eases must fi rst upgrade to HPSS 4.5 or HPSS 5.1. Sites that are going to install and confi gure HPSS 6.
6.2 . Pla nn ing for t he HP SS 6. 2 Upgr ade This section provides information necessa ry to plan t he upgrade of an HPSS 4.5 or HPSS 5.1 s y ste m to HPSS 6.2. It is im por tant that al l planning i nformation be revi ewed careful ly before perf orming the upgrade.
• Modific ation of NFS metadata. In support of new authenti cation m echanis ms, elimination of credenti al obje ct Id. Change privile ged caller principal length fr om 15 to 255 character s. NFS is no longer supported. The NFS tabl e contai ns converted m et adata, but will be renamed to PRE62_NFS to prevent use.
information. New index defi nition for table. The m eta data conversion is pe rformed by the hpss_51_62_se rver conversion program. • New SERVERINTERFACES table. This table i s populated by the hpss_51_62_serve r conversion with default server i nterface information.
hpss_ldap_i mport to c onvert DCE authorizat ion infor mation into LDAP. • Kerbero s authenti cation and Unix aut horization. In this case, t he site determines on its own how to convert DCE authenticat ion i nformation into Kerberos. The site will then use hpss_unix_i mport to convert DCE authorizat ion information into Unix.
• The hpss_dce_export and hpss_uni x_import uti lities are provided to convert DCE authorizat ion infor m a tion. LDAP: • Configuring LDAP is m ore complex than Unix. • Managing LDAP is f airly simple and does not re quire regular m ai ntenanc e.
three m i nutes, and the subsystem conversi on took approxi m a tely 40 minutes. 6.2 .6 .1 . Run nin g Tim e f or t he Lon g Run nin g Met ada ta Co nve rs ion Ut ilit ie s (fo r 4 .
running the m et adata conversion. Th is direc tory will be used to s tore one text-based restar t fil e, various te xt-based db2 output files, and other text fil es. Prior to performing the m eta data conversion, beco m e familiar with the conver sion program output for the HPSS 4.
% DB2 UPDATE DB CFG FOR <Database Name> USING <Setting> <Value> To reset to defa ult set tings, execut e: % DB2 RESET DB CFG FOR <Database Name> Review and update the fol lowin.
attribut es per tinent to authorizati on are retained in HPSS 6.2. The program also opti onally supports Unix authenti cation in HPSS 6.2 b y obtaining each HPSS users’ password from DCE and preserv.
load i nto the new ta ble. • db_convert_nso bject - This program converts the name server ob ject m et adata from the HPSS 4.5 nsobj ects SFS file to the HPSS 6.2 DB2 NSOBJECT and NSACL tabl es by reading records from SFS and performing DB2 loads into the new table s.
hpss_md_convert_51. This progr am will rename the HPSS 5.1 tables by prepending the original table name with PRE62_ so that the original m eta data in HPSS 5.1 is pres erved. The hpss_md_convert_51 utilit y calls the following programs to perform the conversion: • hpss_51_62_dmg – Reads the 5.
• Acquire Kerberos or LDAP software, as needed. See Section 6.2.3: New Aut henticati on and Authorizat ion Mechan isms on page 182 for a l ist of vali d authenticat ion a nd authorizati on combinations. See Section 5.2: Inst all Prerequi site Software on page 137 for more information on obtaining MIT or IBM Kerberos and LDAP.
instance (e.g. . /home/hpssl dap/sqlli b/db2prof ile) 7. Setup DB2 instance for LDAP: % /opt/IBM/ldap/V6.0/sbin/idsicrt –n -e <random string> -I <ldap instance name> -t <user name> -l <dir for ldap instance> e.g. % /opt/IBM/ldap/V6.
% /opt/IBM/ldap/V6.0/bin/idsldapmodify –c –i /opt/hpss/config/ HPSS_ldap_schema.ldif –D “cn=hpssldap” –w <password> -v Note: wher e passwd is the password for the DN. In the example above, i t would be the hpssldap user’s password since hpssldap is the DN used above and configur ed with LDAP on this system.
6.3 .5 . Upg rad e AIX This step cannot be performed whil e the HPSS 4.5 or 5.1 system is running. This section applies to site that are upgrading to HPSS 6.2 from both HPSS 4.5 and HPSS 5.1. See Section 3. 3.2: Prerequi site Summary By HPSS Node Type on page 59 for t he the appropria te version of AIX required for HPSS 6.
6.3 .8 .1 . In st all HPSS 6.2 Di st rib ut ion Im age This ste p can be performe d while the HPSS 4.5 or 5.1 system i s running. Prior to install ing the HPSS 6.
code. Check $HPSS_ROOT/bin/ convert62 to ensure the conversion program s compiled properly. The conversion utiliti es must include several Encina SFS fi les to com pi le and link using /usr/l pp/enci na as the defaul t pathna m e.
Next, use m khpss and select the Configur ation opt ion and the n Other Servi ces option to configure the IEEE address for HPSS. This will create the /var/ hpss/etc/i eee_802_ad dr fil e. This is only used b y HPSS and will not affect other services on t his system.
Environment variabl es are no longer kept in t he $HPSS_ROOT/confi g subdirect ory . Many are now kept in /var/ hpss/etc/ env.conf. The m khps s utili ty will a ssist i n creating t he env.conf file and HPSS specific environment varia bles can be added to it.
• MKHPSS_ROOT – set to the path of HPSS 6.2 code (e.g. "/opt /hpss") • HPSS_DB_INSTANCE_OWNER – the Unix User ID of the DB2 HPSS instanc e (e.g. "hpssdb") • HPSS_LDAP_BIND _ TYPE – should correspond with the ty p e of bindi ngs allowed for LDAP (e.
HPSS_PRIMARY_AUTHN_MECH=krb5 HPSS_PRIMARY_AUTHENTICATOR=/krb5/hpss.keytabs Valid settings for unix a uthenticat ion are: HPSS_PRIMARY_AUTHN_MECH=unix HPSS_PRIMARY_AUTHENTICATOR=/etc/passwd The new authorizati on is perf ormed based on the contents of /var/hpss/ etc/s ite.
Using the sc rollbar, m ove the right-panel scr ollbar until the "Authorizat ion Service " information is seen. It should look like the f ollowing: HPSS Installation Guide July 2008 Release 6.
6.3 .1 1. Pr e- Con ver sio n S yst em C hec k • I t is strongl y recommended that a test conver sion be performed pri or to running the conversion on a productio n system.
6.3 .1 2. T ake a fu ll ba ck up of SF S or DB2 This st ep should not be performed while t he HPSS 4.5 or 5.1 system is running. The SFS or DB2 backup should be performed on the root and each non-root subsytem.
The first program used in the 4.5 conve rsion is the information collecti on uti lity, db_convert_col lect_i nfo. This utilit y will gather configuration related information based on input provided about the 4.5 HPSS sy st em. The program will save the information to several text files located in the /va r/hpss/convert/ 6.
subsystem Id of the sub y ste m being converted as the command line argum ent s. For exa m p le, % su – root % db_subsys_convert /.:/encina/sfs/hpss/globalconfig 1 This program provides an option to change al l partial ly written HPSS 4.5 tapes to be read-only.
-db /var/hpss/convert/6.2/Convert.DB.Names -ss /var/hpss/convert/6.2/Convert.SS.Server.Ids -sub 1 % db_convert_bitfile –g /.:/encina/sfs/hpss/globalconfig -db /var/hpss/convert/6.2/Convert.DB.Names -sub 1 % db_convert_nsobject –g /.:/encina/sfs/hpss/globalconfig -db /var/hpss/convert/6.
root 1456 2034 0 16:04:08 pts/13 0:00 db_convert_bitfile ... root 1567 1456 0 16:04:08 pts/13 0:00 ksh db2 load ... Next, is sue a 'kill -15 1381', sending a SIGTERM (kill -l, will list all .
-db /var/hpss/convert/6.2/Convert.DB.Names -sub 1 -restart When given the ‘-restart’ fl ag, the program will first a ttempt to det ermine that no other conver sions or DB2 loads are currentl y running on the specific table.
error occurs while reading metadata. A restart from a user t ermination (C TRL-C) works well 90% of the time. Som eti mes a user termination can cause DB2 to output m an y sy st em log errors (usuall y means the db2as , administrat ive server di ed). If the program is una ble to perform a restart (i.
environment variables to HPSS 4. 5 values. Example s foll ow: • HPSS_PRINCIPAL_SSM=hps s_ssm • HPSS_PRINCIPAL_FTPD=hpss_ ftp • HPSS_PRINCIPAL_MPS=hpss _mps • HPSS_PRINCIPAL_NDCG=hpss_ndcg • HPSS_PRINCIPAL_NFSD=hpss_ nfs • HPSS_PRINCIPAL_DMG=hpss_ dmg This al lows the db_convert_dce_c ds program to add proper DCE principals from HPSS 4.
machine to enable t he HPSS 6.2 system to work properl y. On sever al test machines, we had to open world access to the devi ces used by the HPSS Core Server and PVL in order for them to init ialize properly.
ensure that the site has SFS and DB2 configured as expected. This program is not able to check the Nam e Server Obj ects (NSOBJECT) or ACLs (NSACL) tabl e. The object count between two systems does not m at ch because object s associa ted wit h deleted bitfile s are not converted.
check every bitfi le descri ptor in the 6.2 s y ste m . The - f and -l options check only the fir st and l ast number of bit file de scriptors provided wit h these opt ions.
Option 1 – Rename old tables [ renaming LSPOLICY table to PRE62_LSPOLICY ] [ renaming SERVER table to PRE62_SERVER ] [ renaming DMG table to PRE62_DMG ] [ renaming GATEKEEPER table to PRE62_GATEKEEP.
6.3 .1 6. En ab le DB2 Bac ku p Set up the DB2 backup process for HPSS metadata. Ensure that an ini tial ba ckup of all HPSS database s are avail able at this point. Perform this step on each root and non-root subsy ste m . 6.3 .1 7. Pe rf orm t he DC E E xpo rt : h pss _d ce_ ex po rt This step applie s to upgrades for both HPSS 4.
5.1, set the non-default server principa l values using the appropr iate environm en t variabl e names: • HPSS_PRE62_PRINCI PAL_CORE • HPSS_PRE62_PRINCI PAL_DMG • HPSS_PRE62_PRINCI PAL_FTPD • .
The conversion program that imports DCE authori zation i nformation i nto LDAP is calle d hpss_ldap_i mport. Usage: hpss_ldap_import <input dir> -realmname <realm> % hpss_ldap_import /var/hpss/convert/6.2 -realmname "cn=hpss.acme.com" Where the real m name option should use the nam e of the realm desired in LDAP.
6.3 .1 9. 1. T une DB2 f or nor ma l ope rat ion s Refer t o Section 5.7: Tune DB2 on page 171 . Perform this step on each root and non-root subsy s tem.
that each caller of the interface is given. Run the hpss_init_se rver_acls program as follows: % /opt/hpss/bin/convert62/hpss_init_server_acls Error in stat of Keytab File, /var/hpss/etc/mm.keytab, 2 Note: The error is expected and does not indicat e that the hpss_ini t_server_ac ls program did not complete succ essfull y .
hpssgui.pl hpssgui.vbs hpss.jar login.conf The - ssmclien tpkg option c reates a ta r file and places it in t he specifie d directo ry (e.g. /tmp/ssmclient pkg.tar) which will contain the f ollowing file s: • hpss.j ar – Java executables for runni ng the SSM GUI • hpssgui.
6.3 .2 0. 1. In vo ke t he SSM S ys tem Man ager , St ar tup D aem on and pr ere quis it e s of twa re Perform this step on t he root subs y st em only. Use the rc.hpss s cript to invoke the Startup Daem o n, SSM System Manager a nd the prerequ isite software.
The default nam e of the SSM configuration file is ssm.conf. Its default locati on is the current director y or, if not there, i n $HPSS_PATH_SSM ( /var/hpss/ssm by defa ult). The name and locat ion may be overridden by the - m option to the hpssgui.pl scri pt or by setti ng the value i n the user's environment.
MPS 10 10 5 20 PVL 50 10 1 2 PVR 30 20 5 30 Mover 20 20 1 5 Startup Daem on 10 10 0 2 SSM Sy s tem Mana ger 100 100 5 20 4. Review and update the Core Server(s ) other configuration parameters, if necessar y 5. For 4.5 upgrades only: Review all migration policies to ensure that the y were converted correctl y In pre-5.
fields will displ ay the current value. Change the accounti ng bits suc h that if the ini tial value is 1 the n the new value will be 2 and conversely if the initi al value is 2 then t he new value will be 1. At this point, t he HPSS sy s tem has no accounting metadata for exi sting fil es.
• Using the GUI, m ar k the MPS confi guration executable and start it • Verify that Migrat ion and Purge are working correctl y • Repack and recl aim tape volumes 6.
in tape mount errors for read operat ions Once it is determined that it ’s safe to revert back t o Release 6.2, perform the steps as fol lows. Note that this procedure assumes that the upgrade stopped after the 6.2 servers are up but before changes were made t hat may aff ect the 4.
the "PRE62_". Next, beginning with step 4, follow the procedures in Section 6.3.24.1: Rev ert the HPSS 6.2 System to Version 4.5 on page 225. The site will a lso have to revert the operati ng sy s tem software and any other upgraded software back to the HPSS 4.
6.4 .1 .2 . db_ co nf ig_ co nv ert , db_s ub sy s_ co nve rt , and db _lr _c on ve rt Err or s and W arn ing s 1SQL3304N The table does not exist . => The program is att empting to inse rt data into a tabl e that has not been created under t he database nam e and sche m a it i s running under.
Resolution: Check that the table exists in the sche m a and that the db_convert _collect _info ut ilit y has been run recently. The empty table scripts pull their information about which schema to use from the text file /var/hpss /convert /6.2/Convert.
Resolution: Either the wrong filena me or the wrong subs y st em Id for that f ilename was ente red. Rerun the conversion program with the corre ct subsystem Id and filena m e .
Error: w rite_bi tfil e_to_ASC fa iled to write to pipe, fd is - 1, errno = 9 => This e rror resul ts when running a l ong running conversion program that cannot write t o /var/hpss/conve rt/6.2 and create a file called asc_fifo_ bitfile (the nam e d pipe f or the C program to c om municat e with the DB2 load).
trying to i nsert the converted metadata. If this resul ted from previousl y running the m eta data conversion, and the metadata should be re-converted, then identify the table nam e (e.
through severa l sy s logd error messages output to the monitor or a failed atte m pt at res tarting the failed conversion progra m . Should DB2 be placed in an inconsistent state , the t ablespace will likel y have to be dropped and rec reated al ong with the t able bei ng converted.
The output displa y s “Re-running” which indicate s that the utilit y is perfor m i ng a restart . When performing a rest art and there are already rows in the DB2 ta ble, rows committed should stil l equal rows submitted to the load.
$ db_config_convert /.:/encina/sfs/hpss/globalconfig Logged into DCE as hpss_ssm. Emptying all configuration tables in global database... All config tables emptied in global database, under schema hpss. Running db_convert_global utility... Converting SFS file /.
Running db_convert_gatekeeper utility... Converting SFS file /.:/encina/sfs/hpss/gkconfig Converted 1 records successfully from /.:/encina/sfs/hpss/gkconfig db_convert_gatekeeper complete, inserted 1 records into DB2 gatekeeper table Running db_convert_logclient utility.
/.:/encina/sfs/hpss/cartridge_stk Converting SFS file /.:/encina/sfs/hpss/cartridge_stk_rait Converted 4 records successfully from /.:/encina/sfs/hpss/cartridge_stk_rait db_convert_cartridge complete, inserted 32 records into DB2 cartridge table Running db_convert_cos utility.
Running db_convert_purgepol utility... Converting SFS file /.:/encina/sfs/hpss/purgepolicy Converted 1 records successfully from /.:/encina/sfs/hpss/purgepolicy db_convert_purgepol complete, inserted 1 records into DB2 purgepol table Running db_convert_pvldrive utility.
$ db_subsys_convert /.:/encina/sfs/hpss/globalconfig 1 Logged into DCE as hpss_ssm. Emptying all subsystem tables in subsys1 database... All subsystem tables emptied in subsys1 database, under schema hpss. Running db_convert_acctlog utility... Converting SFS file /.
Converted 600 records successfully from /.:/encina/sfs/hpss/bfmigrrec.1 db_convert_bfmigrec complete, inserted 600 records into DB2 bfmigrec table for subsystem 1 Running db_convert_bfpurgerec utility... Converting SFS file /.:/encina/sfs/hpss/bfpurgerec.
table for subsystem 1 Running db_convert_storagemapdisk utility... Converting SFS file /.:/encina/sfs/hpss/storagemapdisk.1 Converted 3 records successfully from /.
Converting SFS file /.:/encina/sfs/hpss/bftapesegment.1 Converted 1159 records successfully from /.:/encina/sfs/hpss/bftapesegment.1 lr_db_convert_bftapeseg complete, submitted 1159 records to DB2 bftapeseg load for subsystem 1, 1596 operations per sec, 0.
Converting SFS file /.:/encina/sfs/hpss/nstext.1 Converted 408 records successfully from /.:/encina/sfs/hpss/nstext.1 lr_db_convert_nstext complete, submitted 408 records to DB2 nstext load for subsystem 1, 1233 operations per sec, 1.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 244.
App en dix A. Glos sa ry of Ter ms an d A cr onym s ACI Auto matic Media Library Client I nterface ACL Acce ss Control Lis t ACSLS Auto mated Cartridge Syste m Library Soft ware (Science Technology Co.
Bitfile Service Portion of the HPSS Core Server that provides a logical abstraction of bitfiles to its clients. BMUX Block Multiplexer Channe l bytes between tape marks The number of data bytes that are wr itten to a tape virtual volu me before a tape mark is r equired on the physica l media.
device A phy sical piece of hardware, usua l ly associated with a drive, that is c apa ble of reading or writi ng data. directory An HPSS object that can contain f iles, sy mbolic links, hard links , and other directories.
Gatekeeping Ser vice A registered interf ace in the Gateke eper that provides a site the mecha nism to create local policy on how to t hrottle or deny c reate, open and stage requests and whi ch of these request ty pes to moni t or. Gatekeeping Site Inter f ace The A P Is of the ga tekeeping site policy code.
I/O I nput /Outpu t IOD/IOR Input/Ou tput Desc riptor / Input/Output Reply . Structures us ed to send control inform ation about data movement requests in HPSS and about the success or failure of th e requests. IP Internet Protocol IRIX SGI ’s impl ementation of UNI X junction A mo unt point for an HPSS fileset.
LS Location Server LTO Linear Tape-Open. A ha lf-inch open tape technology developed by I BM , HP and Seagate. MAC Mandatory Ac cess Control managed o b ject A pr ogrammi ng data structure that represents an H PSS sy s tem resource. The resource can be monitored and controlled by operations on the ma naged object.
notification A notice fro m one server to another about a noteworthy occurrence. HPSS notifications i nclude notices sent from ot her servers to SSM of cha nges in manag ed object attributes, change s in tape mount inf ormation, and log messa ges that are alarm, event, and sta t us log r ec ord message ty pes.
RAM Random A ccess Memory reclaim T he act of ma king empty tape virtual volume s available for reuse. Reclaimed tape virtual volu mes are assigned a new Virtual Volume I D , but retain the rest of their previous c haracterist ics.
SS HPSS Storage Service SSA Serial Storage Arch it ecture SSM Storage Sy stem Manage ment SSM session The environmen t in which an SSM user interacts with the SSM Sy stem Manage r to monitor and control HPSS.
stripe length The number of by tes that must be writte n to span all t he phy sical storag e media (phy sical volumes) t hat are grouped together to form the logical storage media (virt ual volume). The stripe length equals th e virtua l volume block size multi plied by the nu mber of phy si cal volu mes in the stripe group (i.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 255.
App end ix B. Refe ren ces 4. 3580 Ultri um Tape Drive Setup, Operator and Service Guide GA32-0415 - 00 5. 3584 UltraSc alable Tape Library Planning and Operator Guide GA32-0408-01 6. 3584 UltraSc alable Tape Library SCSI Reference WB1108-00 7. AIX Perform ance Tuning Guide 8.
Storage System (HPSS), ” f rom the 1995 IEEE MSS Sy mposi um, courtes y of the IEEE Com p uter Society Press. 33. T.W. Ty l er and D.S. Fisher, “ Using Distri buted OLTP Technol ogy in a High-Per formance Storage System, ” from the 1995 IEE E MSS Sy mposi um, courtesy of the IEEE Com put er Society Pres s.
App end ix C. Deve lop er A ckn owl edg men ts HPSS is a product of a governm ent-industr y collabora tion. The proje ct appr oach is ba sed on the premise tha t no single c om pa ny , government labo.
App end ix D. HPSS. co nf Conf ig ura tio n F ile The HPSS.conf configurati on file contains tuning options to be used by HPSS clients and servers. For additi onal i nformation, plea se see the HPSS.
Stanza (CMPD) PFT P Client = { E.g. PFTP Client = { Optional Reserved Sta nza specifier . Must be terminated wi th a matching “}” SubStanza SYSLOG Fac ility = <value > Values: DAEMON , LOCAL0 .
SubStanza Aut o Parallel Size = <value> Value: Size - May be specified as a deci mal num ber or “ x MB” st y le notation. E.g. Auto Parallel Size = 4MB Optional SubStanza specif y ing the minimum file size to start using the “auto-parallel ” feat ures of the PFTP Cli ent.
SubStanza No SAN3P E.g. No SAN3P Optional SubStanza specif y ing not to use SAN3P even if it is availabl e. Default is to use SAN3P if available . SubStanza No Transfer Agent Support E.g. No Transfer Agent Support Optional Substanza specif y i ng to NOT use the Tra nsfer Agent.
The pftp_client automatical ly performs conversi on of get and put comm a nds to their pa rallel equivalents , pget and pput . Some sites have reported degraded performance as a result of thi s substitu tion occurring with sm al l fil e transf ers.
; Transfer Buffer Size = 1MB ; Socket Buffer Size = 16MB # PFTP sets an Artificial (Compiled in) Maximum of 250GB MAX Ptran Size = 10GB # Disable SAN3P ; No SAN3P # Disable Transfer Agent ; No Transfer Agent Supported # Disable 64-bit Protocol - Default is on ; No 64-bit Support # Special Features ; Special Features Enabled } D.
SubSection <Nam e> or <Dotted IP Address> Nam e : Valid Interfac e Name Dotted IP Address: 132.175.1.1 E.g. eth0 132.175.1. 1 Optional param eter containi ng the name or Dot Notation IP Ad.
PFTP Client Interfaces Stanza Exam ple: ; PFTP Client Interfaces = { # PFTP Client Host Name(s) ; water.clearlake.ibm.com water = { # Next Specification is the PFTP Daemon Host # water has 3 specific .
Configuration Ty p e Description Stanza (CMPD) Multinode Table = { E.g. Multinode Table = { Optional Reserved Sta nza specifier . Must be terminated wi th a matching “}” SubStanza Sleep for Debugger = values Value: Time in sec onds.
superdaemon ( /etc/ine td.conf and /etc/ services ) to ini tiate the multinoded. The sections m a y be either a simple secti on or a valued section. A simple substanza is a singl e name/Dot Notati on IP Address to be used for both “Control” connection and “Data” connectio n.
Destinat ion IP address “m as ked” by the NetMask value. The calling appli cation (PFTP Cli ent, Client API, or Mover) will apply the val ue of the NetM ask specifica tion in the configur ation fi le entry to the specifi ed destinat ion a ddress.
Section (CMPD) <Destinati on IP Address> = { E.g. 100.101.102.0 = { Optional SubStanza speci fy i ng a dot ted decimal addre ss of the destinat ion int erface. Only one address is al lowed; however, net works and sub-networks may be chosen by appropriate specific ation of the NetMas k.
SubSection TcpNoDelay = <value> Values: 0, 1 E.g. TcpNoDelay = 1 Optional parameter Indicate s whether the TCP Dela y option should be disabled (0) or enabled (any othe r value) SendSpace & RecvSpace Controls the size of the receive and se nd buffers for TCP/IP sockets.
• Multipl e Sect ions may be included in any SubStanza. A “Default” Destinati on Interface Nam e Section m ay be speci fied. NOTE: Do not inc lude the quotes when specifying Default. • The NetMask must be speci fied in Decimal Dot IP Address Notat ion • All SubSect ions must be specified in every Section.
Default = { NetMask = 255.255.255.0 RFC1323 = 1 SendSpace = 256KB RecvSpace = 128KB WriteSize = 512KB TCPNoDelay = 0 } } } D.5 . PFTP D aem on Sta nz a A large number of opt ions are available for configur ing the PFTP da em on and tuni ng its performance.
SubStanza SYSLOG Faci lity = <value> Value: DAEMON, LOCAL0 ... LOCAL7 E.g. SYSLOG Faci lity = LOCAL0 Replaces -s<string> option. Optional SubStanza s pecif y ing the s y slog facilit y for the HPSS PFTPD. The defaul t s y slog facilit y is LOG_DAEMON (reference: / usr /include/s ys/sysl og.
SubStanza FTP Access Fil e = <value> Value: filen ame E.g. FTP Access File = m y ft pacce ss Replaces -F<string> option. Optional SubStanza setti ng the { FTP_F tpAccess File }. Default: ftpacces s . Located in the directory {FTP BaseDi r}/etc .
SubStanza FTP Principal Keytab File = <value> Value: Pathname/F ilen ame E.g. FTP Pr incipal Keytab File = /var/hpss/et c/hpss.key tabs Optional SubStanza specif y ing the keytab cont aining the FTP princi pal. SubStanza All ow Passive Connectio ns E.
SubStanza PFTP IO Buffer Size = <value> E.g. PFTP IO Buf fer Size = 4MB Replaces -b<string> opt ion. Optional SubStanza setti ng the preferr ed IO Buffer Size f or the PFTP Server SubStanza Debug Val ue = <value> E.g. Debug Value = 3 Replaces -d option(s).
SubStanza Cli ent API Verbose Value = <value> E.g. Client API Verbose Value = 1 Replaces -v option(s). Optional SubStanza specif y ing the level of HPSS Client API Lo gging to use (1-3).
SubStanza Ma xim u m Time Out = <val ue> Value: Time in sec onds E.g. Maximum Ti me Out = 86400 Replaces -T option and hpss_option MTO time in ftpac cess . Optional SubStanza specif y ing the maximum timeout in s econds. SubStanza Use UDP ONLY E.
SubStanza Port Range = <value> E.g. PortRange = ncadg_ip_udp[10100- 12100]:ncacn _ip_tcp[10 100-12100] Optional SubStanza specif y ing the port range to be used for the non-HP SS parallel FTP daemon whic h is neces sary for paral lel transfers. NOTE: This is ignored for passive list ings, etc.
SubSection COS = <value> E.g. COS = 2 Optional SubSection speci fying the Cl ass of Service to be used based on file size. 0 m ean s all ow the Core Server to dete rm i ne the optimal COS. (Has no meaning for the Non-HPSS PFTD daemon.) SubStanza <nodena me> Service Name = < canonicalname> E.
SubStanza PFTP Group File = <value> Value: Pathname /Filename E.g. PFTP Group File = /var/hpss/ etc/pf tp_groups Optional Substanza used to specify the file cont aining the group information for PFTP clients.
SubSection Mapfi le Speci fier = <value> Values: Pathname/f ile name E.g. Mapfile Specif ier = /var/hpss/e tc/Mapf ileName Optional Substanza used to specify a fi le contain ing username mappings. A different file can exist for each Authenticat ion Type.
sizes i n the range [1MB, 2MB). PFTP Daem on Stanza Exam ple: PFTP Daemon = { # Allow the Daemon to take Core Dumps ; Allow Core Files # Directory to put core files in (Default = .) ; Core File Directory = /var/hpss/adm/core # Specify the SYSLOG facility to use for all syslog messages # except Authentication Messages.
; Default Time Out = 1500 # Specify (in octal) the Default umask ; Default Umask = 077 # Specification of the Level of HPSS Client API logging to use ( 0 - 3 ) ; Client API Verbose Value = 0 # Do NOT .
; 100MB = { ; BlockSize = 4MB ; StripeWidth= 0 ; COS = 0 ; } ; 1GB = { ; BlockSize = 8MB ; StripeWidth= 0 ; COS = 0 ; } ; } # Use the System Password file routines (TRUE or FALSE) # The Default for PF.
; GSI = { ; Mapfile Specifier = LDAP:/var/hpss/etc/KRB2UnixMapfile ; Use Site Auth Method = CryptoCard ; Default Authorization Mechanism = LDAP ; } ; IDENT = { ; Mapfile Specifier = FILE:/var/hpss/etc.
SubStanza N ode set Fil e = <value> Value: Pathname/ file name E.g. Nodeset File = /var/hpss/et c/PMTA_Node Sets Optional Substanzaused to specify the location of the Transfer Agent file containi ng Nodesets. SubStanza N ode Affinit y File = <val ue> Value: Pathname/ file name E.
SubStanza D e bug Logfile = <value> Value: Pathname/ file name E.g. Debug Logf ile = /var /hpss/log/ PMTA_Debugf ile Optional Substanzaused to specify the location of the Transfer Agent Debugging File. Substanza SYSLOG Facilit y = <value> Values: DAEMON , LOCAL0 .
# Parallel Multinode Transfer Agent (PMTA) Section Transfer Agent = { # The (optional) NodeSet File contains named sets of # Nodes that can be referred to via the "SET:setname" # notation.
D.7 . Stan za s Re ser ve d for F utu re Use The following stanza nam e s (specif iers) are reserve d for future implementation in HPSS and shoul d not be used by applicati on developers. • Transfe r Agent (Part ially Implemented) • Pipe Fi le • Local Fi le Path • PSI HPSS Installation Guide July 2008 Release 6.
HPSS Installation Guide July 2008 Release 6.2 (Revision 2.0) 292.
App end ix E. hpss _e nv_ de fs .h The HPSS environment variables are define d in /opt /hpss/inc lude/hpss _env_defs.h. These environment variabl es can be overridden in /var/hpss/etc /env.
{ "HPSS_GRP_NAME_CLIENT", "hpss_client", NULL}, /* ************************************************************************** * * HPSS Server Principal names * * HPSS_PRINCIPAL - P.
* HPSS_PRINCIPAL_MPS_UID - Principal UID for Migration/Purge Server * HPSS_PRINCIPAL_MVR_UID - Principal UID for Mover * HPSS_PRINCIPAL_NFSD_UID - Principal UID for NFS Daemon * HPSS_PRINCIPAL_NS_UID .
* HPSS_EXEC_PVR_SCSI - executable name for PVR SCSI * HPSS_EXEC_SSMSM - executable name for SSM Storage Manager * ************************************************************************** * */ { &quo.
* HPSS_EXEC_DELOG - Pathname for the delog utility * HPSS_EXEC_RECLAIM - Pathname for the reclaim utility * HPSS_EXEC_REPACK - Pathname for the repack utility * ***************************************.
* HPSS_UNIX_NFS_CHECKPOINT - checkpoint * HPSS_NFS_DISABLE_JUNCTIONS - disable traversal of junctions * HPSS_MNT_DISABLE_JUNCTIONS - disable mounting junctions ****************************************.
{ "HPSS_SUBSYS_DB_NAME", "subsys", NULL}, { "HPSS_MM_SCHEMA_NAME", "HPSS", NULL}, { "HPSS_MM_LOW_WATER_MARK", "1", NULL}, { "HPSS_MM_HI.
*/ { "HPSS_HOST_TMP", "%H", NULL}, { "HPSS_DESC_CORE", "Core Server", NULL}, { "HPSS_DESC_DMG", "DMAP Gateway", NULL}, { "HPSS_DESC_FTP.
updates * HPSSSSM_UI_MO_RATE - Time the GUI will wait between MO update tries * HPSSSSM_UI_LIST_RATE - Time the GUI will wait between List update tries * HPSSSSM_UI_ALARM_RATE - Time the GUI will wait.
* to maintain at once. If this number of connections is * exceeded, then old connections will be close to * maintain this number of connections * ******************************************************.
* HPSS_API_MAX_CONN - Defines the number of connections that * are supported by the Client API within * a single client process * HPSS_API_DEBUG - Used to enable debug messages * HPSS_API_RETRIES - Us.
{ "HPSS_API_TOTAL_DELAY", "0", NULL}, { "HPSS_API_LIMITED_RETRIES", "1", NULL}, { "HPSS_API_DMAP_WRITE_UPDATES","20", NULL}, { "HPSS_AP.
* [ stdout | syslog ] * HPSS_CONFIG_CAT_NAME - HPSS config message catalog full pathname * HPSS_INFRA_LOG_TYPES - Default types of infrastructure messages * to be logged * HPSS_INFRA_LOG_CONF - The in.
* HPSS_AUTHZ_TYPES - Supported authorization types * HPSS_SITE_LOCATION - Site Location * KRB5_INSTALL_PATH - Kerberos installation path * no default - platform dependent * KRB5_KDC_DIR - Kerberos dir.
NULL}, { "HPSS_PRIMARY_AUTHENTICATOR", "${HPSS_KRB5_KEYTAB_FILE}", NULL}, { "HPSS_CLIENT_AUTHN_MECH", "${HPSS_PRIMARY_AUTHN_MECH}", NULL}, { "IEEE_802_FILE", "${HPSS_PATH_ETC}/ieee_802_addr", NULL}, { "HPSS_AUTH_SERVICE_CONF", "${HPSS_PATH_ETC}/auth.
* HPSS_PATH_CORE - Path where subsystem core files are placed * HPSS_PATH_TMP - Path where temporary files are placed * HPSS_PATH_ETC - Path where runtime config files are placed * HPSS_ENV_CONF - The.
App en dix F . /var/hpss files The /var/hpss dir ectory tree is the default location of a number of HPSS confi guration files, l og files, and other files needed by the server s. The directories and confi guration files can be created with the mkhpss util ity or hand created.
authorizat ion mechanism and aut horization URL to utiliz e. • rc.db2 . Create d by mkhpss. Script for starting DB2. • rc.krb . Creat ed by mkhpss. Script for starting the Kerbe ros servers . • passwd. Created by mkhpss. A local HPSS-only password file for use wi th Unix authentica tion and authorizati on.
of the HPSS servers it brought up in the node. HPSS may also write diagnostic log files and disk allocati on maps in t his directo ry , when configured to do so. The lock files are very small, but t he log files and maps can be very large. HPSS Installation Guide July 2008 Release 6.
Ein wichtiger Punkt beim Kauf des Geräts IBM HPSS (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie IBM HPSS noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für IBM HPSS - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von IBM HPSS reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über IBM HPSS erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon IBM HPSS besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von IBM HPSS verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit IBM HPSS. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei IBM HPSS gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.
