B. Create storage resources (Section 8.1.2: Creating Storage Resources on page 234)
4. Create additional HPSS Users (Section 13.1.1: Adding HPSS Users on page 325)
5. Create Filesets and Junctions (Section 10.1: Filesets & Junctions List on page 308 and Section
10.5: Creating a Junction on page 315)
6. Create HPSS /log Directory
If log archiving is enabled, using an HPSS namespace tool such as scrub or ftp, create the /log
directory in HPSS. This directory must be owned by hpsslog and have permissions rwxr-xr-x.
The /log directory can be created by the root user using ftp as follows:
% ftp <node> <HPSS Port> # login as root user
ftp> mkdir /log
ftp> quote site chown hpsslog /log
ftp> quote site chmod 755 /log
1.5. Additional Configuration Roadmap (All Sites)
This section provides a high level roadmap for additional HPSS configuration.
1. Configure HPSS User Interfaces (Chapter 14: User Interfaces on page 339)
2. Set up Backup for DB2 and Other Infrastructure (Chapter 15: Backup and Recovery on page 356)
3. Set up High Availability, if desired (HPSS Installation Guide, Chapter 3: HPSS Planning)
4. Optionally configure support for both authentication mechanisms (HPSS Installation Guide,
Section 5.9: Supporting Both Unix and Kerberos Authentication for SSM)
1.6. Verification Checklists (All Sites)
This section provides a number of checklists regarding configuration, operational and performance
issues.
1.6.1. Configuration Checklists
After HPSS is running, the administrator should use the following checklists to verify that HPSS was
configured or converted correctly:
Global Configuration
• Verify that a Default Class of Service has been selected.
• Verify that a Root Core Server has been selected.
Storage Subsystem Configuration
• Verify that a Default Class of Service has been selected if desired.
• Verify that a Gatekeeper has been selected if gatekeeping or account validation is required.
• Verify that the COS Name list has been filled in correctly.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 17